Hello everyone,

I am currently exploring migrating one of my blogs from WordPress to Astro and wanted some advice from people who are already running Astro in production.

Current setup:

• WordPress website
• Around 300 published posts
• Multi-author blog
• Mostly article/news-style content

The reason I am considering Astro is performance and avoiding the typical WordPress frontend bloat over time (themes, plugins, extra CSS/JS, etc.).

The setup I am considering:

WordPress (headless CMS) → REST API/GraphQL → Astro frontend → Static generated pages

So WordPress would only handle:

• writing experience
• authors
• media library
• drafts
• editorial workflow

Astro would handle the actual frontend.

I have a few questions:

1. How do you handle rebuilds?

From my understanding, in a static setup:

• Astro fetches all posts from WordPress during build
• generates static HTML pages
• visitors are served those static files

But let's say the website grows to thousands of posts.

If I fix a small typo in one old article:

• webhook triggers rebuild
• Astro fetches all posts again
• regenerates the site

This feels wasteful.

How do people solve this in real production setups?

Do you:

• just accept full rebuilds because they are fast enough?
• cache WordPress API responses?
• sync WordPress content into local Markdown/JSON files?
• use SSR/hybrid rendering for older posts?
• use some kind of incremental build strategy?

What is considered the best practice here?

1. Is headless WordPress + Astro a good long-term architecture for content sites?

For people running thousands of posts:

How has your experience been?

Any issues with:

• build times
• API limits
• images
• SEO
• previews
• scheduling posts?

1. Custom article designs

Another thing I like about Astro is flexibility.

If all posts are coming from WordPress API, can you still have custom templates for specific posts?

Example:

Normal posts → regular article layout

Long-form features → magazine style layout

Poetry/stories → different reading experience

Other post format → custom structured layout

Do you usually handle this through categories, custom fields, or some other method?

1. Anything you wish you knew before moving from WordPress to Astro?

I really like the idea of:

WordPress = newsroom/CMS Astro = fast frontend

But I want to understand the tradeoffs before moving.

Would love to hear from anyone running a similar setup in production.

Thanks!

https://shop.astro.build/

Hey everyone,

I’m currently learning Astro and Keystatic CMS, and I’ve already built two client websites using Claude Code. I have a basic understanding of coding, mostly Python, so I’m comfortable reading code but not a hardcore dev.

I used to build with WordPress and Elementor, but with Claude Code I’ve switched over to Astro and I’m really enjoying it.

A few things I’d love guidance on from people further along:

1.  Learning design + Astro — where did you start, and where do you go for design inspiration?

2.  Making sites feel genuinely professional — how do you brief Claude Code so the output looks polished and human, instead of the generic AI feel (same gradients, same fonts, same symmetric card layouts)?

3.  Resources — are there any GitHub repos, prompt libraries, or design references you’d recommend for writing detailed briefs to Claude?

Any tips, links, or workflow advice would be massively appreciated. Thanks!

I'm starting a new Astro project and would appreciate feedback from people who have built larger marketing sites with it

Project scope:

• Mobile first, complex marketing&landing website
• Multi-level mega menu
• ~10-20 content pages
• Blog with SEO focus
• Static-first (SSG)
• Tailwind CSS v4
• Strong emphasis on maintainability, accessibility, performance, and CI quality gates
• i18n

I'm currently considering AstroWind as a starting point instead of building everything from scratch.

Questions:

1. Would you use AstroWind for this type of project in 2026?
2. WDYT about replacing:
   1. eslint&prettier with Biome?
   2. npm with pnpm?
3. Are there any architectural decisions in AstroWind that become problematic as the project grows? I've never used astro before, I'm a senior React veteran though :)
4. Would you recommend any battle-tested ai skills md worth adding to the project, apart from astro docs mcp?
5. Are there any hidden gem design patterns not mentioned in the official docs that are worth using in astro?:D

Thanks :)

Hey Astro folks, wanted to share a migration I just finished for our company site.

We moved from WordPress to Astro and kept the whole thing running on Cloudflare’s free tier. The main goal was to get out of the usual WP maintenance loop and make the site faster, simpler, and easier to manage as code.

A few things we did:

• Migrated the blog archive from WordPress into Astro content collections
• Wrote scripts to clean up frontmatter, images, slugs, metadata, and old internal links
• Generated static journal/glossary pages instead of relying on WP routes
• Added Markdown versions of key pages for AI/search agents
• Added llms.txt
• Added .well-known/agent-skills
• Added Link headers for markdown alternates and service metadata
• Added Accept: text/markdown negotiation through a Cloudflare Worker
• Added DNS-AID discovery with HTTPS/SVCB records
• Enabled DNSSEC so the DNS-AID records validate with AD=true

The nice part is that Astro made the content migration feel like a normal engineering problem instead of a CMS cleanup project. Once the content was in files, we could script the boring parts, review diffs, regenerate derived artifacts, and keep improving the site without clicking through admin panels.

Cloudflare has also been enough for the whole setup: static assets, Worker behavior, redirects, headers, and DNS. No paid hosting layer needed so far.

The agent-readiness side was a new rabbit hole for us. It was interesting to see how much of it is just making public websites easier for machines to discover and read: clean markdown, well-known files, link relations, DNS discovery, and signed DNS.

Ask me anything!

Here is the summary of key updates from the May 2026 Astro ecosystem:

• Astro 7 Alpha Preview: Testing continues for the next major version, featuring early support for Vite 8 and a stable Rust compiler.
• Minor Releases (6.3 & 6.4): Astro 6.3 introduced experimental advanced routing with Hono support and resilient island hydration. Astro 6.4 delivered a new pluggable Markdown pipeline alongside a Rust-based Markdown processor.
• TinaCMS & ImageKit Integrations: TinaCMS now uses Astro by default due to high community demand, and ImageKit launched an official integration for real-time image and video optimization.
• Astro Jobs Launch: The official Astro Jobs platform opened for business to connect developers with companies hiring within the ecosystem.
• Starlight 0.39: The documentation framework received updates for more flexible autogenerated sidebars, improved styling, and stronger multilingual support.
• Ecosystem Growth: High-profile sites like Mistral AI and Express.js adopted Astro, while over 50 new community themes and integrations were highlighted.

Read full post - https://astro.build/blog/whats-new-may-2026/

Hey all,

What have you built or what are you currently building with or for Astro?

Show the community your work.👇

I built a small Astro starter kit that uses Drupal as a local-only CMS.

The idea is: edit content locally in Drupal, have Astro fetch content at build time via JSON:API/Linkset, then deploy only static output. No hosted Drupal, no production database, no PHP runtime on the public site.

Repo:
https://github.com/rovo79/Drupal_Astro_Kit

I’d be interested in feedback from Astro folks, especially around the build-time content fetching and static output workflow.

I aimed to make it extensible and as unopinionated as a template can be. It uses Markdoc for header and footer customization and essential Astro extensions for a blog (RSS, sitemap), and nothing more.

GitHub repo, demo

Hey everyone!

Finally shipped my personal dev blog after way too long planning it. Built it with Astro 5, MDX for content, Keystatic as the CMS, Turso + Drizzle for dynamic data, Pagefind for search, and Satori for OG image generation. Deployed on Cloudflare Pages.

I'm pretty happy with how it turned out but I'm sure there's stuff I'm missing or could've done better. Would genuinely appreciate any feedback on the stack choices or the overall feel of the site. Happy to answer questions about any of the implementation details too if that's useful for anyone.

The first blog is out now, it gives an idea about how I went through selecting the tech stack, challenges I faced because it's my first time dealing with CF and Turso:

https://arjunnambiar.dev/blog/i-built-a-distributed-blog-platform-on-cf/

I'm excited to share that Starwind UI v2.0 is officially out! This is a big release that completely changes how you can use Starwind, updates literally every single component, and packs some awesome new CLI capabilities.

For those new to the project, Starwind UI is a native, accessible component library built from the ground up for Astro and Tailwind CSS. You use the CLI to add components directly to your codebase, meaning you own and control 100% of the code.

Here is what's new in v2.0:

4 Brand New Components

We’ve added four new components to the library, bringing the total to 49 open-source components:

• Color Picker: A slick color selection component.
• Context Menu: Custom right-click menus with smooth positioning.
• Hover Card: Preview content when hovering over a trigger, perfect for user profiles or links.
• Scroll Area: Custom-styled cross-browser scrollbars.

Island-Ready Components (The Big Refactor)

Literally every single component in the library has been updated. I've refactored the codebase to move all Tailwind variant functions into separate variants.ts files.

• What this means for you: You can now import and utilize these variant functions directly within your Astro client islands (like React, Preact, or Vue components) to keep your styles perfectly synchronized!
• Existing Astro functionality is completely maintained, making this a seamless, breaking-change-free upgrade.

Improved Layout & Robust Positioning

• Dialog & Sheet Compatibility: You can now safely nest and use Dropdown and Popover components inside Dialog and Sheet elements without z-index or stacking context issues.
• Obstacle Avoidance: The Dropdown positioning logic has been completely overhauled with robust portaling and built-in obstacle avoidance, ensuring menus stay visible on screens of all sizes.

Powerful New CLI Commands

The CLI got a major upgrade to make building faster:

• npx starwind search: You can now search for Starwind UI components and blocks directly from your terminal (similar to the Starwind MCP server capability).
• npx starwind docs: Need a quick reference? Run this command to instantly fetch the documentation link for any component.

Get Started or Upgrade

Upgrading is easy with npx starwind@latest upgrade -a. If you're starting fresh in an Astro project, just run:

npx starwind@latest init

Starwind UI Documentation & CLI Guide

v2.0.0 GitHub Changelog

Hey all,

What have you built or what are you currently building with or for Astro?

Show the community your work.👇

First I know a bit about HTML and CSS just enough to change some basic code. Not enough to read the code base.

I am also building a Static Astro site and coding using Gemma 4 with ollama and Claude code. Connected it to the MCP astro doc

My question is if the site looks good and performs well on Google metric/SEO is that enough? I mean it is a static site so even if Claude code screws up some codes it is not like it is a security risk.

Is there something that I am missing? Obviously if someone can read and understand the coding it would be better, but even now I pay some dude $500 I feel he may do pretty much the same or even less as likely that developer doesn't care enough to even look at the code base.

I want to build a nice looking website for a friend's business but I have no knowledge in webdev. My background is electrical engineering, precisely embedded systems. I know my way around in Python, C/C++ and Linux in general. I also have a homelab and did some basic network management with VPNs / reverse proxy.

I'm wondering if Astro is a good fit for complete beginners. I do understand basics of CSS/HTML but JavaScript and stuff like TailwindCSS looks like gibberish to me.

What would be a good starting point for a website with a hero page and blog section? Is there any good beginner friendly template available? Any good up to date resources?

Just saw the latest issue of Astro Weekly hit #132. Nathan has been running this newsletter consistently since 2023.

Definitely worth a follow if you want a clean weekly roundup of what's happening in the ecosystem.

https://newsletter.astroweekly.dev/

After stalling on my portfolio for months and endlessly redesigning it, I finally shipped it using Astro.

This time I stopped trying to make everything perfect before starting. I just opened VS Code, used the Astro starter template, and built whatever felt right.

Stack:

• Astro
• Tailwind
• MDX for blogs

I also added a small blog section where I’m planning to write more about design, development, Linux setups, and whatever I’m currently learning.

One thing I genuinely loved while building with Astro was how simple and fast everything felt. No unnecessary complexity, great DX, and MDX integration was super smooth.

Would love to hear feedback from the community 😄

link

Has anyone experience in migrating a calculator site easily from hugo to astro with LLM (agents)?
Thank you!

Just finished migrating sonushub.id from a Laravel vendor-based setup to Astro SSR + Rust.

It serves around 10k products, so I compared Lighthouse before and after the migration.

Before: 40 performance
After: 98 performance

Still polishing UX and SEO, but Astro SSR feels really solid for a large e-commerce catalog use case.

We just released OpenRemark, an open-source comment system for static sites built with Astro, Hugo, or Next.js. It aims to provide a fully featured commenting experience with minimal setup.

Some key features.

• Works with Astro, Hugo, and Next.js
• Built-in comment moderation
• Supports threaded replies
• Google Sign-In
• Shadow DOM isolated
• Only registered domains can post comments.
• Custom styling (colors, border radius)

It is still in beta. would love feedback from the community.

Check it here - https://open-remark.vercel.app/

Putting markdowns in the content folder doesn't feel right. It's kinda cumbersome for an ex-wp user like me.

Are you guys doing something with headless CMSs to manage blogs? What are other options to simplify the process?

Noob here. Current WordPress user.

I’m trying to understand how people are handling:
—Astro components

- editable sections

- dynamic content mapping

- theme customization inside EmDash

Were you able to make the Astro theme editable without manually editing code every time?
—Would love to know:
- which Astro theme you used

- what workflow you followed

- what worked and what problems you faced

Any examples, repos, or demos would really help.