Tag
11 articles tagged #Astro.
P.01Astro 7.0 rewrote its compiler in Rust, jumped to Vite 8, and switched markdown parsers by default. What changed, what was removed, and how to upgrade.
P.02Astro's stable CSP hashes its scripts and styles into a per-page meta tag, with no nonces. How to set up security.csp in Astro 6 and 7, and where it stops.
P.03EditorPickA deep dive into how we built codercops.com with Astro 5 SSR, Supabase as a CMS, Git-based content, and Edge Functions. Architecture decisions and lessons learned.
P.04Step-by-step tutorial to build a live-updating analytics dashboard using Supabase Realtime subscriptions, Astro SSR, and D3.js charts. Full code included.
P.05EditorPickPick Astro for content sites, Next.js 16 for large React apps, React Router 8 for loader-and-form apps on any host. Current versions and tradeoffs compared.
P.06Server components have gone from React experiment to cross-framework standard. Here is how they work in React, Vue, Astro, and Svelte — and what changes for your apps.
P.07Run npx astro add cloudflare, build, then wrangler deploy. Static pages serve from Workers static assets; on-demand routes run in the Worker. Astro 7 setup.
P.08Splitting a growing blog into its own repo, linked by a Git submodule, fixes merge conflicts and CI noise. Here is our exact setup for 130+ posts.
P.09Choosing a modern web app stack means weighing Next.js vs Astro vs Remix, SQL vs NoSQL, and Vercel vs AWS against your project's actual priorities, not trends.
P.10Pick Astro for sites people read and Next.js for apps people operate. A decision guide for agency and marketing sites, checked against Astro 7 and Next.js 16.
P.11Astro powers our site, Vercel deploys it, Airtable runs our CRM, and Satori generates OG images. Here is every tool in our stack and why we picked each one.