Sample release
See the public-safe release walkthrough.
Trust
Safe releases
WPFlow is staging-first by default, with evidence packs, rollback awareness, and client-approved publish before anything goes live.
The rule
The headline version, in plain language.
- WPFlow does not treat production as the testing surface.
- Release review happens against staging with an evidence pack.
- Publish remains a distinct approval step.
Why the rule exists
Governance only helps if the reason is visible.
- Risk falls when the preview surface is staging rather than live.
- Evidence keeps the release conversation concrete.
- Approval before publish reduces accidental live changes.
What it means in practice
The rule changes the working method, not just the copy.
- Every approved change is implemented on staging first.
- The release pack records what changed, what did not change, and the publish path.
- Rollback awareness is recorded before publish is offered.
What the client sees
The client-facing experience should make the rule obvious.
- A staging preview to review before live action is even discussed.
- Evidence pack details rather than vague status updates.
- A clear publish step that still requires client approval.
What WPFlow does not do
Clear omissions are part of trust.
- Casual live edits as the normal working method.
- Hidden publish actions with no evidence trail.
- Pretending speed and safety are opposites.
Related proof and next reading
Useful links if you want to inspect the release model more closely.
Next step
If these rules make sense for your team
Sign up with your site details and the sort of changes you need month to month.