Visual editing
Publishing workflows people follow
The BetterCMS team Product
Share this post
Summarize with
AI
TL;DR, key takeaways
- Workflows that survive have few stages and one clear owner at each.
- Three stages is usually enough: draft, review and published.
- Reviewers need a diff of what changed, not just a preview.
- Put permissions where the risk is, not on every field.
A workflow is a promise that nothing reaches the public without the right person seeing it. Teams break that promise not out of carelessness but because the workflow costs more than the risk it prevents, and somebody with the permission to skip it does.
So the design question is not how to enforce more. It is how to make the compliant path the fast one.
What is a publishing workflow?
A publishing workflow is the sequence of states a piece of content moves through before it goes live, together with the rule about who can move it between them. Draft, in review, approved, published is the common shape.
The states are not the point. The point is the gate: what cannot happen until a state is reached. A workflow whose stages are labels with no gate behind them is a status field, and everyone treats it as one.
Three stages is usually enough
Draft, review, published covers most content. Legal and regulated content needs a fourth. Almost nothing needs six, and a six stage workflow is how a typo fix takes nine days.
- Every stage needs a named owner, not a group of eleven people.
- Every stage needs an exit condition somebody can check in a minute.
- If a stage has never rejected anything, it is not a stage.
- A route for the urgent case, with an audit entry rather than a shrug.
Review needs a diff, not a preview
Asking a reviewer to read the whole page is asking them to find a changed sentence by re-reading two thousand words. They will approve it without doing that, and they should not be blamed for it.
Show what changed. Field by field, before and after, with the unchanged parts collapsed. Review becomes a two minute job and starts catching things.
Put permissions where the risk is
Blanket roles cause the bypass. If publishing the pricing page and publishing a blog post require the same approval, one of the two is wrong, and the team will route around whichever one is over-controlled.
Scope the gate to the content. High risk types get review. Everything else gets a lighter path and a good audit trail. The audit trail is what makes the lighter path defensible.
A workflow nobody bypasses is one nobody wants to bypass.
How do you know it is working?
Two numbers. How long content sits in review, and how often something is published without passing through it. The first tells you whether the workflow is affordable. The second tells you whether it is real.
Your next website starts here
See BetterCMS running on your pages, not on a sample site.