r/astrojs

⭐ 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?

Frontman is for a specific problem: AI coding agents often edit frontend files without seeing the running app, built for technical people.

Why try it:

- select/click UI before asking for edits

- agent gets DOM, screenshot, logs, routes, source mappings

- works with Astro, Next.js, Vite, WordPress

- open source

Latest release added Astro content collections support.
And it's fully OSS, self hostable etc

Repo: https://github.com/frontman-ai/frontman

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: github.com/DuvInc/duvlify - Docs (built with itself): duvlify.dev

Behind the scenes, how my site architecture looks like.

Lightning-fast, smart, and local AI in the build process: https://ammar-najjar.com/blog/website-architecture/

#WebDev #AstroJS #Performance #Cloudflare

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?

I've been building PlopKit, an open source comment system that can be embedded into any website. It's made for people who want comments on their website without visitors having to sign up to leave a comment.

It has moderation tools such as:

• Accepting or rejecting incoming comments
• Automatically accept comments
• Banning certain words
• And many more in the future

I've been building this in private for around two months now, and I figured I might as well share what I have so far and get some feedback.

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

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

website: https://plopkit.com/

🚀 Shipped ScrollStack — headless infinite scrolling for Web

📦 1.92 KB gzipped, zero runtime deps

⚛️ React, Vue & Svelte adapters

🔁 Cursor, offset, Virtual list & page pagination → one function

🧠 Stale responses can't resurrect dead state

You bring the markup 👇

https://scrollstack.js.org

A while back I went looking for an Astro template actually built for publications: news sites, blogs, content-heavy stuff. Not another landing page kit with a blog tacked on. I couldn't find much I liked, so I built one for myself.

That one became a few. The few became over 20, somehow, without me really planning it that way.

I put them on Astro site with zero expectations. No audience, nothing. Two months ago I got my first sale, and now people are reaching out asking if I can set up their blog after buying one of my themes. That's the part that really threw me.

I'm not sharing this because the numbers are impressive, they're not. I'm sharing it because a year ago "build and sell my own theme catalog" was just a vague idea I kept putting off, and now it's turning into actual client work I didn't ask for.

If you've got something like that sitting on your own back burner, consider this a nudge. :-)

The catalog is here if you want to poke around: https://xocothemes.com. A handful of themes are free to try. Honest feedback on the design and UX is genuinely welcome, good or bad.

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

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.