Editorial workflows should make it clear what can happen next and who is responsible. A collection of loosely related buttons is not a workflow; it is a set of actions without enforceable rules.
Define a state machine
List valid states and transitions. For example, a draft may move to review, review may return it to draft or approve it, and approved content may be scheduled or published. Reject transitions that do not make sense for the current state.
Implement transition rules in a domain or service layer rather than relying only on hidden buttons in the admin interface. A crafted HTTP request must not bypass approval requirements.
Separate capabilities from roles
Roles are useful bundles, but authorization should be expressed as capabilities: create content, edit own drafts, review submissions, publish, schedule, archive, and manage users. This is easier to reason about than scattered checks such as if role == admin.
Record who performed each transition, when it happened, and any review note. Keep an audit trail separate from the current status.
Handle scheduled publication safely
A scheduler should claim due items in a concurrency-safe way, verify that they are still approved, publish them once, and record the outcome. Make the operation idempotent so retries do not create duplicate events or notifications.
Implementation checklist
- Enumerate states and permitted transitions.
- Enforce transitions on the server.
- Use capability-based authorization.
- Record actor, timestamp, and reason.
- Make scheduled jobs retry-safe.