Direct answer
Build locally, validate, then upload a full asset set to Workers static assets so visitors never see a mixed old/new tree.
Practical shape
npm run gate— typecheck/build/validate (includes AEO markdown mirrors)wrangler deploy— atomic-ish publish of the new asset manifest- Soft-reload 404s: Worker strips
If-None-Matchbefore ASSETS rewrite; purge only if an old 404 was edge-cached
No nginx in this stack. Origin is Workers + Cloudflare DNS.
Links
- Writing: /blog/atomic-static-releases
- Expertise: /expertise/infrastructure