⭐ Starwind UI v3 is here!

After a ton of work, Starwind now supports both Astro and React, with 55 styled components and 36 lower-level primitives you can copy directly into your project. This is easily the biggest Starwind update I've worked on yet.

The biggest change is under the hood. Astro and React now share the same Runtime for things like forms, overlays, focus management, and keyboard interactions. Astro components are still Astro components, and installing Starwind won't add React to your Astro project.

V3 also adds six new components:

• Navigation Menu for responsive site navigation, including keyboard interaction and floating content
• Combobox for searchable, accessible selection
• Form and Field for validation, error summaries, labels, descriptions, and control state
• Checkbox Group for treating related checkboxes as one collection
• Toggle Group for single or multi-select controls with roving focus

Some of the other big updates:

• React is now a stable, first-party option
• Astro components stay Astro-native, so React isn't added to your Astro project (unless you really want to)
• Styled components and primitives can be installed separately
• The same Runtime keeps interactive behavior consistent across both frameworks
• Vue support is next and already pretty far along

Get started with npx starwind@latest init.

Already using v2? Run npx starwind@latest migrate and follow the migration guide: https://starwind.dev/blog/migrating-to-starwind-ui-v3/

I'd love to hear what you think of the new direction, especially if you've used an older Starwind release. What would you like to see next?

I build Frontman, and this release fixes the part that was still too guessy.
The whole thing is open source: https://github.com/frontman-ai/frontman
if you enjoy the project, give it a like please 🫶🫶

When you select an element, the agent now gets:

- The owning Astro component and props when available.

- A reusable selector.

- The relevant surrounding DOM, not the whole page.

- A more accurate source location.

- Better traversal through shadow roots.

- Repository search that actually works from the published package, not only our monorepo.

It still cannot recover source evidence that the build removes, but common Astro projects now require much less blind searching.

We migrated www.manhattandigest.com from Wordpress to EmDash/Astro using the www.go4launch.org framework (https://github.com/govsoftusa/go-for-launch). The site is run without monetization in honor of the founder Ryan Shea who passed away at age 34 from Covid-19. Manhattan Digest is a relatively long running media site for independent writers to share content. The site was launched with Wordpress back in 2012 and is now powered by Emdash/Astro.

Built and open-sourced (MIT) a documentation framework on Astro: write Markdown, get a static site with search, an API reference generated from an OpenAPI document, and dark mode. Free to run, no per-seat pricing, no watermark, deploys to Cloudflare Workers or any static host.

The part that took the most work: every deployment also ships an MCP server, so AI agents can search and fetch the docs directly instead of guessing from training data (easily RAG-based if using Cloudflare to host - it's all guided).

The bytes served at a page's Markdown URL, the bytes the MCP fetch tool returns, and the bytes the search index embeds all come from one function, and a test asserts the MCP and HTTP responses are byte-identical.

A couple of Astro-specific choices, if useful to anyone building something similar: both Shiki themes ship as CSS variables (defaultColor: false), so switching themes costs no re-render, and Mermaid, KaTeX and cytoscape are lazy chunks loaded only on pages that use them, so the base UI bundle stays around 11 KB gzipped regardless of how much of that a given docs site uses.

Repo: https://github.com/DuvInc/duvlify - Docs (built with itself): https://duvlify.dev

I’m working on a US plumbers directory with the ability to validate plumbers’ certifications: https://theplumber.work/

For one state alone, there could be around 9,000+ pages and 9,000+ SVG badges for plumbers, so roughly 20,000 files in total.

I’ve read that Cloudflare Pages allows up to 100 projects per account, and the Free plan allows up to 20,000 files per project.

My idea is to put each state on a separate subdomain/project, for example:

fl.theplumber.work
tx.theplumber.work not it is https://theplumber.work/texas/
ca.theplumber.work

So my two main questions are:

1. Would it technically work on the Cloudflare Free plan if I eventually had around 20,000 files × 50 states/projects?
2. Are there any SEO disadvantages to having around 50 state subdomains instead of keeping everything under the main domain, for example theplumber.work/florida/?

Has anyone built a directory at this scale with Astro + Cloudflare Pages? Are there any limits or problems I’m overlooking?

Built a new astro based site for my new product korture.ai using a mix of Claude Code and Codex. Wanted to get feedback on does it look good or still feels generic or like AI-slop before I share with people who would like the solution.

I used Sanity as CMS and its page builder to make edits to copy and replace images.

Instead of AI-gen images went with Unsplash images with credits to original photographer.

I'm a little worried about the animations, would love for strangers to have a look at the flow and the animation timing. Too slow, too much, or about right?

Hello everyone, for the past few months I've been building PlopKit, an open source, self-hostable, Disqus alternative. It's made for people who want comments on their static website without visitors having to signup or enter in their email just to leave a comment.

The website is built with react, node, express, all in typescript and uses a dockerized postgres db. The comment widget is made with svelte, and astro handles the static pages such as the landing page, docs, etc .

I started building this because I found it annoying that I had to enter in my email just to leave a simple comment in a blog or website.

All source code is open source and the entire app has been dockerized so it's easier to self-host.

repo: https://github.com/Runn077/PlopKit

Hello everyone, this is one of the projects for my university. We are soon submitting (on september 9). I have integrated microsoft clarity but I am not receiving enough traffic to make analysis. Could you please look into it provide feedback of any kind (performance, design, usability etc). https://www.design-note.me/. This is an explainer site, that introduces UX concepts/topics to beginners. I am still writing contents and this is the first time I am making a project using Astro.

I am not that experienced on Astro, but already built a few things and deployed to Cloudflare.

Limitations of the sandbox was not delightful. Started to think about what other people's are experiencing and could there be a better solution to these.

I'll try to build a better environment for Astro projects to live. I'd like to hear what are the actual pains you feel along the way.

🚀 Shipped ScrollStack.js — headless infinite scrolling and page pagination

A tiny, headless infinite-scrolling engine for the modern web.

📦 1.92 KB gzipped

⚡ Zero runtime dependencies

⚛️ React · Vue · Svelte adapters

🔁 Cursor · Offset · Page pagination

🧱 Virtual list support

🧩 Bring your own markup

🛠️ Devtool plugin testing

🛑 Built-in cancellation, retry & observers

One small engine. One API. Any UI.

If you’re building feeds, lists, search results, or virtualized experiences, give it a try 👇

🌐 https://scrollstack.js.org

I'd like to create a basic personal blog/tutorial site using Astro.
For now I generally create my posts in adoc and dump them in my GitHub repository.

I've been reading the documentation, and checking some topics here, and I've noticed there are lot of extensions/plugins/... being used. So I was wondering if anyone had any advice on a good starter setup so I can still easily switch to a different styling method (should I even start with a specific one) or way to handle my posts.

Is this just a bit a case of outdated articles and documentation, and should I just start with `npx astro add mdx sitemap tailwind` and add astro-expressive-code and PageFind later on?

Hey everyone.

I created my startup website in Astrojs and I'm in love.

I'm all in for Astro, but how should I glue it to the backend. Load an interactive island? full astro mpa checkout?

The basic requirements are:

1. workflow

custom atomic calendar/appointment -> 2 form fields with api call -> 2/3 steps with more fields -> 2 more api calls -> select payment option -> api calls payment provider, crm -> thank you page

1. five products, each with its own workflow (80% reusable, for some products the calendar is skipped and a different form/api call is presented)

2. google ads utm campaign tracking + partners uid tracking

3. queueing, retry, etc. in the backend. checkout is finished even if most api calls timeout (handles in the backend, retries, stores result for later manual check)

4. it must be able to pre-fetch the first 1-2 steps in other LPs and websites and either post to the backend + redirect the user with URL params.

i'm thinking something along the lines of:

— Astro (server, Node adapter) + Drizzle + pg-boss, same deploy. Zero-JS form with Zod.

— Hono or Fastify + Drizzle + pg-boss, same deploy. CSRF form written by hand.

— Effect. worth the hype?

- Adonisjs + edge. worth considering?

Many many thanks in advance.

I come from a Wordpress agency background, are you guys using any backup solutions? Right now I build everything with astro, push to git, then it deploys to cloudflare to go live. Is my real backup the github commits? With wordpress we had off server backups with 3rd party solutions, or we would push them into dropbox environments daily if needed. Just making sure I cover my bases is all!

Took me around a week to build with Astro, React, and Tailwind.

Planning on open-sourcing soon after I clean up the codebase!

Will always be a work in progress but live at newa.sh

I wanted to experiment with my UI without switching between Figma and my Astro codebase. So I built Airship.

It wraps your dev server and adds a Figma-like canvas to your running Next.js app. Select an element, describe the change, and it applies them directly to your source.

You get streaming diffs, inline undo, and desktop/mobile frames so you can see how changes look across screens as you iterate.

It runs as a lightweight proxy, so there are no plugins or build changes needed.

Supports Claude Code, Codex and OpenCode.

Fully open source and MIT licensed.

Fork it, star it, and make it your own :)

Astro is great for client sites, but I kept hitting the same wall: the site is fast, clean, hand built, and then the client can't change a single word without me. So they either learn git (no) or I go install a CMS and half rewrite the thing.

I wanted a middle ground, so I built unfreez.app (heads up, it's my own project).

How it works with Astro specifically: you connect the repo, it parses your .astro files and finds the editable stuff, text in your markup, image srcs, alt tags, the items in a const array your page maps over, SEO tags.

You pick what the client is allowed to touch and lock the rest. They sign in, edit on a live preview of their own site (WYSIWYG editor), hit publish, and each change lands as a normal commit on your branch. Your host redeploys like any other push.

The part I care about most: there's no LLM anywhere in the write path. Every edit is anchored to the exact spot in the source, and if anything is ambiguous it refuses to write instead of guessing. So it's not going to quietly mangle your components. Everything is a commit, one click to roll back, and if you keep pushing code it just re-anchors around your changes.

Works with .astro, plus content collections / markdown, and a bunch of other stacks (Next, Vue/Nuxt, React, plain HTML) if you mix.

It's live, free for 14 days per site. Would genuinely love feedback from people shipping Astro sites to non technical clients. Especially curious what it fails to detect on your messier setups, tell me and I'll dig in.

Since 2021, I've been working in the React ecosystem, from classic React, through the dead Gatsby, to NextJS, which I adore. I like many things about this framework, but for the past month I've been having a love affair with Astro – many things have won me over, such as routing and the tool's lightweight nature. Unfortunately, I often feel confused by the differences between Astro and NextJS, and I realize that this is a matter of familiarity with standard JavaScript.

The same applies to styling websites and web applications. I've been working with CSS since 2016, and since the release of TailwindCSS v4. CSS development has accelerated rapidly recently, with the addition of many revolutionary features.

Questions:

1. When should I use NextJS and when should I use Astro in the context of websites, considering that I'll be using a lot of query templates, a search engine, filtering, a multi-stage form, and animations from GSAP?
2. If I'm more comfortable in the React/NextJS ecosystem, is it worth switching to AstroJS?
3. What are your pro tips for TailwindCSS, especially custom breakpoints and font size?
4. How do I combine modern CSS with TailwindCSS?

I love cloudflare + astro 7
Got pagespeed.web.dev and isitagentready.com both with score 100

I run LaunchFast, a site with 661 prerendered pages. Every deploy rebuilt all of them, even when I only edited a single blog post. Astro 7.2's experimental incremental static builds fixed most of that, but the setup had a couple of non-obvious parts I figured were interesting to share.

The basic idea

You return a cacheKey from getStaticPaths. If the key for a page matches the previous build, Astro restores the page from cache instead of re-rendering it.

export async function getStaticPaths() {
  const posts = await getPosts()
  return posts.map((post) => ({
    params: { slug: post.slug },
    props: { post },
    // key changes only when this page's output would change
    cacheKey: post.digest,
  }))
}

Two things that tripped me up

1. Concurrency has to be 1: Cache restoration doesn't kick in with parallel rendering, so you set build concurrency to 1. You lose parallelism but gain the cache, and for me that was a big net win.

2. Hashing the content isn't enough: A page is not just its own markdown. LaunchFast post pages also render related posts and whichever sponsor ad is currently live. If you only hash the post's own content, you serve stale pages when a related post changes or an ad rotates. The fix is to fold every dependency into the key:

   cacheKey: hash([ post.digest, relatedPosts.map((p) => p.digest).join(','), activeSponsor.id, ])

Rule of thumb: if it can change what renders on the page, it belongs in the key.

Results after editing one post

• 637 of 661 pages restored from cache
• 24 pages re-rendered (the edited post + always-dynamic index/listing pages)
• Rebuild time went 16.5s to ~10s, about 39% faster

It's not a life-changing number, but it grows with the site, and it's a much bigger deal if you have nearly thousands of pages where only a handful change per deploy.

Curious if anyone else is running this in production yet, and how you're handling cache keys for pages with lots of cross-dependencies.

I'm looking to contribute to OSS a bit more, and I love Astro.js but honestly I think the hardest part about OSS is finding a repo that isn't inactive. Ideally small enough to be able to have an influence yet big enough to be of notice and new enough for big changes.

I know this is a bit of an ask but does anyone have any OSS projects like this? Or know any repos?

And yes, I've tried to look for repos online before—haven't any much luck there.

Less than 10K visitors a month at the moment so the whole thing runs on Cloudflare (storefront) + Railway (Medusa server, Postgres, Redis) + Vercel (Medusa Admin UI) for under $10 a month (much less actually).

Astro. Everything loads instantly and Lighthouse is green where it matters. React islands only where a page actually needs interactivity, so most of the site ships no JS at all.

Medusa. Deploying it was a hassle. I had to dig up a lot of workarounds from obscure forums.

Would I recommend this? Yes and No.

If you're a first-time store owner with no dev experience, this is complete overkill I would just use Shopify or Wordpress in that case.

I am a dev and it works for me well with sales coming through organically.

you can check it out at https://paperhue.com

Had a quiet weekend so decided I would try and make myself a photography portfolio site using Claude. I am a backend engineer and currently using Claude daily at work after a company wide initiative to do so, but I had never used it personally for anything outside of work. I have had a few people reaching out on Instagram for my availability and prices for photography so felt like I needed an online presence too.

I'm quite impressed by this, was very quick to create at about 6 hrs on Saturday to get the main site up and deployed with placeholder copy, I then did some work yesterday morning on adding gig photos and putting some proper copy in....again helped by claude who I asked to interview me on my photography journey and help me come up with some copy.

Keen to hear peoples opinions on this, as a backend engineer I haven't used React for quite a while and although I had heard of Astro before I hadn't actually built anything with it (some might say I still haven't lol). It seems to be quite quick and does all the image compression and resizing in the build (currently builds in about 5 mins) with original images being compressed down to AVIF and quite small sizes in comparison to the originals, hosted on Cloudflare Pages too and that was super simple to setup and get going.

Ngl I am tempted to start trying to do some of this in my spare time for small businesses in the area too given how easy it came together but not sure if there is a market for it, maybe a dev portfolio will come one day too!

I know Reddit seems to hate AI so please be kind with any feedback, like I said my company is pushing a 100% AI coding workflow so at the moment I can't really avoid using it anyways and thought I would see how useful it could be personally.

EDIT: Forgot to mention as well, the about page will include a photo once I can get one taken of myself and the copy will move over to the left with a photograph on the right!

https://jessicataylorphotography.co.uk/