LOG 07 · INFRASTRUCTURE
Cloudflare Pages Deployment
Static builds pushed straight to Cloudflare's edge network via Wrangler — fast first-byte times worldwide, and nothing running that needs a server bill or a patch schedule.
Deploy is a build artifact, not an operation
Because the site compiles to static files, deployment is `wrangler` pushing that output directory to Cloudflare's edge network — no server to provision, no runtime to keep patched, no scaling configuration to get wrong under a traffic spike. The entire site is replicated to edge locations worldwide, so a visitor gets served from whichever location is physically closest to them.
For client work, this matters beyond raw speed: a static, edge-hosted site has a dramatically smaller attack surface and no ongoing server cost that scales unpredictably with traffic — one less thing for a client to budget for or worry about after launch.