astro

When to use astro

Reach for Astro when building content-heavy sites — blogs, documentation, marketing pages, portfolios, e-commerce fronts — where fast load times and SEO matter and most of the page is static. It shines when you want to reuse existing React/Vue/Svelte components without committing to a single framework, and when you want optional SSR or static output per route.

When not to

Less ideal for highly interactive, app-like SPAs (dashboards, real-time tools) where most of the UI is dynamic — a framework like Next.js, Remix, or SvelteKit centered on a single component model gives a smoother experience. The .astro component syntax and multi-framework flexibility also add a learning curve you don't need if you're already all-in on one framework.

Strengths

• Islands architecture ships zero JS by default, yielding excellent Core Web Vitals
• UI-agnostic: mix React, Vue, Svelte, Solid, Preact in one project
• Flexible output: static site generation, SSR, or hybrid per-route
• Rich official integration ecosystem (adapters for Vercel, Netlify, Cloudflare, Node) plus content collections, MDX, and @astrojs/db
• Strong tooling: TypeScript-first, language server, VS Code extension, astro check

Trade-offs

• The .astro file format is another syntax to learn alongside your framework of choice
• Cross-framework component interop has edge cases and shared-state limitations between islands
• Not the natural fit for stateful, app-heavy SPAs
• Rapid major-version evolution has historically required migration work