Why this site runs on the edge
Notes on rebuilding eliascorp.org as a static Astro site on Cloudflare Workers.
SEED POST — placeholder content. Replace or delete once real posts exist.
The v2 of this site is static Astro served as Cloudflare Workers static assets. Zero client JS by default, build-time image optimization, and the framework is now first-party to the deploy target. Fast where it counts, cheap to run, and boring in the way infrastructure should be.
Why static, why the edge
The site is content, not an application. Once that’s true, a server in the request path is mostly a liability: another thing to keep warm, patch, and pay for. Pre-rendering every route to HTML and pushing it to Cloudflare’s edge means the first byte comes from a machine near the reader, not from a region on the other side of the planet.
- No cold starts. Static assets don’t boot.
- Predictable Core Web Vitals. No JS to parse before content paints.
- Cheap to run. Bandwidth, not compute.
The dynamic bits that remain — OG image generation, the RSS feed — are build-time or edge functions, not a long-running server.
See DECISIONS.md in the repo for the full rationale.