Why Astro Is My Go-To Framework in 2026
After building with Next.js, SvelteKit, and Remix, here's why Astro won me over for content-driven sites.
The framework fatigue is real
I’ve shipped production apps with Next.js, SvelteKit, Remix, and even good old Gatsby. Each has strengths, but for content sites, they all share a problem: they ship way too much JavaScript.
Enter Astro
Astro’s proposition is simple: ship HTML by default, add JavaScript only where you need it. The islands architecture means you can sprinkle in React, Svelte, or Vue components exactly where interactivity is needed — and nowhere else.
What convinced me
- Zero JS by default — my blog posts are pure HTML/CSS
- Content collections — type-safe markdown with Zod schemas
- View Transitions — SPA-like navigation without the SPA
- Cloudflare Pages — Astro’s first-class CF support makes deployment trivial
The numbers
My personal site ships under 50KB of JavaScript (gzipped). That’s with cursor trails, 3D tilt effects, confetti easter eggs, and smooth page transitions. Try getting that with Next.js.
When NOT to use Astro
Astro isn’t the right choice for:
- Highly interactive apps (dashboards, editors)
- Real-time collaboration tools
- Apps where most pages need heavy client-side state
For everything else? Astro is the answer.