Architecture Decision
Astro as a static-first operating constraint
The site’s publishing architecture stays intentionally simple: Astro source becomes static output served by Cloudflare Workers Static Assets.
The site follows a deliberately narrow delivery path:
Astro source → static build → dist → Cloudflare Workers Static Assets
That constraint keeps important content in generated HTML, makes navigation independent of client-side JavaScript, and limits the number of moving parts between authored content and the public site.
Practical boundary
Static-first does not mean that the site can never become interactive. It means an interactive feature has to justify the additional client runtime, operational surface, and accessibility work it introduces.
Implementation note
The current architecture does not use a server output mode, an Astro Cloudflare adapter, or a Worker application entry point. Cloudflare serves the generated dist directory as static assets.
Warning
Adding on-demand rendering, a database, or a hydrated framework would be an architectural decision—not a routine dependency change. It should happen only when a real feature requires it and after the effect on performance, deployment, and maintenance is understood.