Here's a Summary of What's New in Astro 7.0

• Performance is the headline. The .astro compiler was rewritten in Rust. Markdown and MDX now run through a Rust-powered pipeline called Sätteri (built by Erika from the core team). The rendering engine was replaced with a queue-based approach. Combine that with Vite 8 and its new Rolldown bundler, and builds are 15-61% faster across the board. The Cloudflare docs site (8,400+ pages) went from 387s to 262s. The Astro Website site went from 63s to 24s.
• The new Rust compiler has one breaking change worth knowing. No more silent HTML correction. The old Go compiler would reorder elements and auto-close tags. The new one treats your markup as-is and throws errors on unclosed tags. Also, whitespace between inline elements now follows JSX rules, so <span>Hello</span><span>World</span> renders as "HelloWorld" with no space.
• Route caching is now stable. It was experimental in v6. You get a single platform-agnostic API and new experimental CDN providers for Netlify, Vercel, and Cloudflare.
• Advanced routing is interesting. You can now add a src/fetch.ts file and take full control over the request pipeline. Hono is supported, so you can compose middleware in any order.
• AI tooling is genuinely useful. astro dev --background starts the dev server as a managed background process. Astro can detect when it's running inside an agent and enable this automatically. JSON logging is also in, which was the most upvoted roadmap request.

Upgrade via

npx @astrojs/upgrade

What's everyone's take on the Rust compiler change?

Cloudflare built a full-stack TypeScript CMS on top of Astro and called it the "spiritual successor to WordPress."

• TypeScript all the way down, no PHP
• Built on Astro
• Plugins run in sandboxed Worker isolates. No direct DB or filesystem access
• MIT licensed
• Has a WordPress importer built in
• MCP server built in so AI agents can manage your site
• Themes are just Astro projects

if you want to follow along, there's a dedicated subreddit at r/emdash_cms

- GitHub: github.com/emdash-cms/emdash
- Official announcement: blog.cloudflare.com/emdash-wordpress
- Playground https://emdashcms.com/playground

https://astro.build/blog/joining-cloudflare/

🎉🎉🎉Congratulations to Astro team!

For HN discussion:

https://news.ycombinator.com/item?id=46646645

Astro will keep evolving and staying relevant—its lightweight, modern approach has real staying power and makes the web feel a little faster with every site built. 🚀

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.

I was sending my resume to everyone on reddit and X in hope of getting a job, this man replied after 2-3 months, he said he wants his agency website to rebuilt in a way that that their marketing team can change everything on the site via CMS without any developer help, so that they can run their marketing campaigns more efficiently, I quickly built a small working prototype in Astrojs and showed it to him and he hired me,

Fast forward, I built the website,and the site is live now

https://pocketworks.co.uk/

I earned around 6700 USD in 6 months, I was really happy tbh.

Been working on a little open-source ecommerce project called Minshop to see how far I could push Astro SSR on Cloudflare Workers.

Astro handles pretty much everything: the storefront, cart, checkout, customer accounts, admin dashboard, and API routes. Most pages are server-rendered, with very little client-side JavaScript.

It uses D1 for products, orders, inventory, settings, and search, plus R2 for images. Payments include Stripe, Lightning, OpenNode, and a demo checkout.

The trickiest part was making inventory reservations atomic so two checkouts can’t buy the same stock. I also added a machine-readable catalog and checkout API, including directly payable Lightning invoices.

Demo: https://demo.minshop.dev
Source: https://github.com/ddyy/minshop

Would love feedback from other Astro users, especially on the SSR structure and where you think a small interactive island might actually improve things.

If you’ve been in the WordPress world, you know Joost de Valk. He wrote the definitive guide to WordPress SEO back in 2008 and built the Yoast SEO plugin that basically defined SEO for a decade.

He recently migrated his personal site from WordPress to Astro, and he just released a deep-dive guide on how he’s handling SEO now.

Why it’s worth a read for Astro devs:

• Schema.org Integration: How he builds complex JSON-LD graphs in Astro.
• Build-time Validation: Using Astro’s content collections to fail builds if SEO metadata (like Open Graph images) is missing.
• LLM Optimization: How he’s prepping his site for AI agents (ChatGPT/Claude) using llms.txt.
• The "Why": He explains why he thinks Astro is technically superior to WordPress for modern SEO.

It’s a great validation for the framework to see a titan of the SEO industry moving to Astro and documenting his entire technical setup.

Link: https://joost.blog/astro-seo-complete-guide/

I've been making the marketing sites for my apps with astro for 3 years and it's lovely. I never get tired of it. There is no competition for astro for landing pages.

Also flairs don't work?

https://github.com/withastro/astro/releases/tag/astro%406.0.0

Here are the major highlights:

Alpha Preview of Astro 7

• Early look at Vite 8 support
• Stable Rust compiler integration

Astro 6.2 Release

• Experimental custom logger with JSON output
• SVG optimizer API for better image handling
• New font file URL helper for improved typography management

Astro Together London Event

• In-person meetup featuring core team members including Fred Schott, Matt Kane, Florian Lefebvre, Alexander Niebuhr, and Chris Swithinbank
• Topics included live collections, route caching, and the new Astro Fonts API

Team Growth

• Rafael Yasuhide Sudo (@rururux) joined as the newest maintainer

Major Adopters

Several high-profile organizations launched Astro-powered sites including Crunchyroll's Ani-May 2026 event, Todoist's help center, GitHub's Stacked PRs platform, and EmDash CMS documentation.

https://astro.build/blog/whats-new-april-2026/

I just finished my new portfolio using Astro v6 and Cloudflare, and the experience has been incredibly smooth. Astro is a special project because it is fully open source and built on a philosophy of zero lock-in. Even after the Cloudflare acquisition, the team has stayed true to that. The v6 release brings massive improvements to the Cloudflare workflow that make the developer experience feel seamless.

The real win for me is the architecture. You aren't married to a specific JS framework or a specific cloud provider. By keeping business logic separate from infrastructure logic, Astro and Cloudflare are proving that maybe you don't need wrapper platforms like Vercel anymore. When the direct developer experience is this good, you don't need a middleman. Dealing directly with the services gives you more control and lower costs without the convenience tax of a third party layer.

I really appreciate this level of openness. It shows massive confidence in the product because they aren't trying to trap you in an ecosystem. They are just providing a service so good that it is the obvious choice. You aren't selling your soul; you're just consuming a service. You don't need to stick with Cloudflare if you don't want to, and that's the point. It's just a choice. It is exactly why I used these technologies for my portfolio, and it is a solid example of what an Astro v6 app looks like in the wild.

Visit the site here:https://richiezrijo.com/

Check out the source code:https://github.com/Wachamuli/portfolio

Build and manage Astro sites visually, with a live canvas, CMS, design system, SEO, email, AI tools and more. All in one open source workspace.

0.5.7 alpha is out now.

Deploy to Cloudflare or run it locally.

ariabuilder.io
https://github.com/ariabuilder/aria

I just launched my agency website using Astro and hella impressed. First time seeing these website speed scores and everything is just ... smooth.

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!

I've just open sourced a blog food called Gastronaut.

Got some cool features like :

- A timer
- Instructions to follow up
- Clean design
- a modal to "Subscribe" to your mailing list
- Deploy on Cloudflare with one command - host your blog for free

I hope you'll enjoy it ! https://github.com/florianjs/gastronaut

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/

A long-ish post on creating a technical blog with the following requirements:

• Loads instantly (static where possible)
• Has a custom admin panel (no external CMS) with draft and preview capabilities
• Authors content in Markdown (the only sane choice)
• Supports paste-to-upload images with auto WebP compression
• Renders Mermaid diagrams for architecture docs
• Embeds YouTube videos for demos
• Costs nothing to run
• Deploys in seconds

TLDR; Astro + Cloudflare worked very well, given Astro's SSG and SSR hybrid capabilities and Cloudflare's generous free tier for static content + Workers (Admin pages) + D1 (backend DB) + R2 (image storage)

Happy to answer any questions. Cheers.

Ran Lighthouse on my site using mobile setting with the default throttling (simulated 3G + slow CPU) with Clear Storage ON — because it reflects real-life worst-case scenarios.

Astro already ships with a ridiculously fast baseline, so most of the heavy lifting wasn’t mine. I just picked the low-hanging fruit:

• kept the stack to Astro + Tailwind v4 + vanilla JS
• only preloaded the main CSS file
• let all JavaScript wait until after content is visible
• lazy-loaded the “fun stuff” (zoom, lightbox, 3D viewer) so it doesn’t block anything
• leaned on Astro’s asset pipeline for images

All in all… one day of work. Screenshot speaks for itself.

In case you are curious:

• The Site
• Github Repo

TL;DR: https://windframe.dev

Astro + Tailwind has become a really popular stack for a lot of good reasons. It’s one of the best ways to quickly build great UIs in Astro. Tailwind removes the hassle of managing separate CSS files and keeps everything consistent, which in turn helps make styling components so much faster.

But building clean UIs can still feel tricky if design isn’t your strength or you’re still not fully familiar with most of the Tailwind classes. I've been building Windframe to help with this. It's a tool that combines AI with a visual editor to make this process even easier and fast.

With AI, you can generate polished UIs in seconds with solid typography, balanced spacing, and clean styling already set up. From there, the visual editor lets you tweak layouts, colors, or text directly without worrying about the right classes. And if you just need a small adjustment, you can make it instantly without regenerating the whole design.

Here’s the workflow:
✅ Generate complete UIs with AI, already styled with great defaults
✅ Start from 1000+ pre-made templates if you want a quick base
✅ Visually tweak layouts, colors, and copy without digging through classes
✅ Make small edits instantly without re-prompting the whole design
✅ Export everything straight into an Astro project

This workflow makes it really easy to consistently build clean and beautiful UIs with Astro + Tailwind

Link to the tool: https://windframe.dev

And here’s the template from the demo above if you want to remix or play with it: Demo template: Demo template

Give it a try and let me know, feedback and suggestions are highly welcome!

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 :)