Astro + Markdown + CDN
Content sites that stay fast because there is almost no JavaScript to ship.
Circumstances — when to use it
- Blogs, docs, changelogs, marketing sites — content changes, layout rarely does
- Authors are comfortable writing Markdown in a repo
- Lighthouse scores and Core Web Vitals are a business requirement
Synergy — how the pieces fit
Astro renders components to HTML at build time and strips their JavaScript unless you explicitly opt in with an island. Markdown files become typed content collections, so a missing frontmatter field fails the build instead of the page. The output is static files, which a CDN serves from the edge with no origin server, no cold starts, and no database to keep alive.
The tech and its role
Architectural examples
Each example links to a public source — no claims about private internals.
Astro's own docs
Built with Astro and content collections; the repo is public and is the canonical example of the pattern.
sourceCloudflare developer docs
Moved developers.cloudflare.com from Hugo to Astro with the Starlight docs theme and open-sourced the content.
source · 2025Firebase blog
Rebuilt the Firebase blog on Astro, reporting a 71% performance improvement and publishing time cut from hours to minutes.
sourceSkip if
Skip if the page content depends on who is logged in — personalization fights a fully static build.