Astro 6 Beta — CSP Nonces, Declarative Web Components, and Architecture Tradeoffs
Astro 6 beta ships CSP nonce support, declarative web components, improved server islands, and Vite 7. We break down the architecture decisions and tradeoffs.
Tag
#Astro
11 posts tagged with "Astro"
Astro 5 in Production — SSR, Supabase, and the Architecture Behind Our Website
A 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.
Build a Real-Time Dashboard with Supabase Realtime, Astro, and D3 — A Complete Tutorial
Step-by-step tutorial to build a live-updating analytics dashboard using Supabase Realtime subscriptions, Astro SSR, and D3.js charts. Full code included.
Next.js 15 vs Astro 5 vs Remix — Choosing the Right Framework in 2026
We 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.
Server Components Are Everywhere Now — React, Vue, Astro, and What It Means for Data Fetching
Server 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.
Cloudflare Acquires Astro: What It Means for Developers and the Web Framework Ecosystem
Cloudflare 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.
Astro 6 Beta: First-Class Edge Computing with Cloudflare Workers Changes Everything
Astro 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.
Building a Modern Web Application in 2026: The Technology Stack Decision Guide
Astro 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.
Managing 130+ Blog Posts with a Separate Content Repository
How 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.
Astro 5 for Agency Websites: Why We Moved Away from Next.js for Our Own Site
We 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.
Our Tech Stack in 2026: What We Use and Why We Chose It
Astro 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.