Tag
12 articles tagged #Astro.
P.01Astro 7.0 shipped a full Rust rewrite of its compiler, a jump to Vite 8, and a default markdown parser switch, plus a short list of breaking changes. Here's what changed, what got removed, and a practical checklist for upgrading a real project.
P.02Astro 6 beta ships CSP nonce support, declarative web components, improved server islands, and Vite 7. We break down the architecture decisions and tradeoffs.
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.05EditorPickWe have built production apps with all three. Here is an honest comparison of Next.js 15, Astro 5, and Remix covering performance, DX, and when to use each.
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.07Cloudflare has acquired The Astro Technology Company, bringing the popular open-source web framework under its umbrella. We analyze the acquisition, its impact on Astro developers, and Cloudflare's broader web platform strategy.
P.08Astro 6 Beta brings a redesigned dev server, first-class Cloudflare Workers support, live content collections, and major performance improvements. Here's what developers need to know about migrating from Astro 5.
P.09How we split our agency website into two repos — one for code, one for content — and why this architecture scales better than a monolith. With our exact Git submodule setup, GitHub Actions validation, and content workflow.
P.10Astro vs Next.js vs Remix. PostgreSQL vs MongoDB. Vercel vs AWS. Every technology choice in your web application has tradeoffs. Here's a practical guide to making the right decisions for your project.
P.11We build client projects in Next.js daily. But for our own agency website, we chose Astro 5. Here's the performance data, developer experience comparison, and architectural reasoning behind that decision.
P.12Astro for the website, Vercel for deployment, Airtable as CRM, Satori for OG images, a separate content repo with GitHub Actions CI — here's every tool in our stack and the reasoning behind each choice.