Architecture · Diagram Design

Content site in production

The static-first stack: Cloudflare's edge absorbs most reads, Astro renders MDX on misses, content is checked into the repo.

Content site in production Architecture diagram showing reader requests moving through Cloudflare to an Astro origin, MDX bundle, and content CMS. CONTENT HTTPS RESP SSR READ MDX QUERY EXT Reader Browser EDGE 01 Cloudflare Pages · cache ORIG 02 Astro Origin SSR + MDX BUN MDX Bundle src/content/*.mdx CMS Content CMS assets · og images LEGEND Focal / origin Backend / bundle Store Cloud External HTTP request Primary flow Return / async

THE HEADLINE

Edge absorbs the reads

Nearly every reader is served by Cloudflare's edge cache. The Astro origin only wakes on a cold slug or a revalidation.

Content lives in the repo

  • Posts are MDX files
  • Checked in, reviewed in PRs
  • No runtime database

CMS holds the big stuff

Images, OG art, and downloadable assets live in a separate bucket keyed by slug. Astro links them at render time.