Cloudflare Workers
Cloudflare Workers development
Applications deployed to the edge, with static artefacts generated at build rather than served from a worker.
Part of devops and release engineeringThis site runs on Cloudflare Workers through Wrangler. The sitemap and robots file are written at build time into static assets so a crawl costs no worker invocation, and the canonical origin is a single value in one content file, which makes moving to a custom domain a one-line change instead of a search across the codebase.
The same deployment shape carries the VM Academy web application, which is a considerably larger surface: marketing, an authenticated student experience and an admin panel behind one build.
What that covers
- Wrangler deploys with environments kept separate
- Static assets generated at build, not served dynamically
- Environment variables understood as build-time versus runtime
- Server functions at the edge for forms and webhooks
- A single canonical origin driving canonicals, sitemap and metadata
Where this has shipped
Next: Expo
Tell me what you are building.
A sentence about the product and where it is stuck is enough to start. I answer every mail myself, including the ones where the answer is that I am not the right person.