Deployment — Cloudflare Pages

This registry is published as a static docs site on Cloudflare Pages, connected to this GitHub repo. Every push to main auto-deploys; feature branches get preview URLs. No secrets, no database.

How it works (no dashboard build settings needed)

  • The site is generated from the Markdown by npm run build into public/, and that output is committed to the repo.
  • wrangler.jsonc tells Pages where it is: "pages_build_output_dir": "public".
  • So Pages just uploads public/ and serves it — no build command required in the dashboard.

Because the built site is committed, the Pages project needs no build command and no output directory set in the dashboard — wrangler.jsonc supplies the output directory.

Updating the docs

  1. Edit any .md file.
  2. Run npm run build (re-renders public/).
  3. Commit both the .md and the regenerated public/, and push.

The build prunes any page in public/ it did not just write, so renaming or deleting a source file removes its published page in the same commit. Before that, a rename left the old page live at its original URL, serving superseded content to anyone holding the link.

Pages redeploys automatically on push to main.

Local preview

npm install
npm run build
npm run dev          # wrangler pages dev public

Branch discipline

  • Don't push directly to main (it auto-deploys production).
  • Feature branch → PR → merge (only when requested) → delete the branch afterwards.
  • In Cloudflare, deploy the latest commit — Retry deployment re-runs the old commit and won't pick up newer changes.