Deployment Readiness
This page keeps the public deployment contract simple and visible.
The site is English-first, wiki-led, and selectively published. It should stay small, readable, and safe to ship. For the public routing and information architecture, see Public Site Structure.
Current deployment path
- write or revise public-safe docs and notes
- run a production build
- verify the generated output in
build/ - deploy the static build through Wrangler
In practice, the site currently uses:
npm run build
npm run deploy
npm run deploy rebuilds first and then runs wrangler deploy.
Release checklist
Before a push or deploy:
- confirm the content is public-safe
- keep navigation clear and English-first
- prefer wiki structure over docs-for-docs-sake
- run a build after site code or docs change
- treat build success as the minimum release gate
Current constraints
- the public site is a selective surface, not a vault mirror
- thin drafts should stay private until they become useful
- deployment should remain boring and reversible
- Cloudflare Pages can be evaluated later if it becomes the cleaner fit
What this page is for
This is not a roadmap. It is a working note so the publish pipeline stays legible while the site evolves.