Cloudflare Worldedge community field guide

FIELD NOTE / 03

Pages: make the deploy loop boring

Connect a static or full-stack project to a repeatable build, preview, and production path — on Workers for new projects, on Pages for the ones you already run.

ROUTE03 / 06
SOURCEWorker Previews

READ THE BOUNDARY

Pages: make the deploy loop boring

A good deployment path gives every change a place to be inspected. Cloudflare now tells new projects to start with Workers, where Worker Previews give each branch its own production-like environment; Pages remains the path for projects already running on it. Treat build output, environment variables, preview URLs, and rollback behavior as part of the product.

  • Start new projects on Workers and keep `wrangler pages deploy` for existing Pages projects.
  • Make the build command deterministic and documented.
  • Declare each Preview explicitly — it does not inherit production settings, and KV, D1, and R2 are isolated only when bound to separate resources.
npx wrangler preview

SOURCE CHECK

Keep the official page authoritative

This note is an orientation layer, not a claim of affiliation. Product behavior changes; follow the source link, check the current docs, and bring concrete results back to the Community forum.