Data, not tangled markup.
Edit src/data.js to add stages, playbooks, environments and release checks.
YOUR PATH TO PRODUCTION
THE RELEASE PLAYBOOK V1.0
Great ideas.
Careful steps.
Live with confidence.
A clear route from your next feature to a tested release. One repository, three branches, and two environments working together.
RELEASE ROUTE↗
feature / your-ideaBUILD
↓ pull request + checks
developmentINTEGRATE
↓ release review
productionVALIDATE
↓ tested release
mainGO LIVE ↗
Every promotion has a checkpoint.
03Long-lived branches
02Permanent sites
01Shared release process
0Direct feature pushes to main
01 / THE BIG PICTURE
Every branch has a purpose.
Select a stage to see where work belongs
and what happens next.
A name worth remembering. The
production branch is the release candidate. The main branch serves the live production site.02 / PUT IT INTO PRACTICE
Your next move, explained.
03 / TWO SITES. ONE SOURCE.
A place to test.
A place to go live.
Cloudflare Pages builds the static site.
cPanel continues to serve existing PHP apps.
Preview before promotion. Enable the
production preview branch in the prod Pages project. Test its commit-specific deployment, record the SHA in the PR, then promote that code to main.04 / THE LAST MILE
Ready is a checklist.
Not a feeling.
Record your checks before promoting a release. Progress stays in this browser; it is a personal aid, not a GitHub approval or a live deployment status.
05 / BUILT TO EVOLVE
Change the content.
Keep the structure.
Small, replaceable pieces.
Each ES6 class owns one interface. Components receive data and services from the application.
Dependencies at the edge.
Storage and clipboard adapters can be replaced without rewriting the workflow or its views.
Setup record, operations & official references +
Setup status · Daily operations and recovery · Cloudflare setup
GitHub branch protections · Cloudflare branch controls · Preview deployments