Design a backend workflow where editors create content, reviewers approve it, and published users see only approved versions.

Design content approval and publishing

Designs draft, review, publish, rollback, and audit behavior for content managed by editors and admins.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I would separate draft content from published content, either with explicit versions or status fields that make the read boundary clear. Editors can create and update drafts, reviewers can approve or reject, and publishing creates the version visible to users. Each transition records actor, timestamp, reason, and previous state. Public APIs read only published versions.

Full answer below

Practice focus

Versioning, draft state, review state, publish boundaries, permissions, rollback, audit events, and cache invalidation.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Approval workflows appear in content, commerce, and admin tools. The design has to keep draft changes away from public reads while preserving a clean path to review, publish, and rollback.
I would separate draft content from published content, either with explicit versions or status fields that make the read boundary clear. Editors can create and update drafts, reviewers can approve or reject, and publishing creates the version visible to users. Each transition records actor, timestamp, reason, and previous state. Public APIs read only published versions.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would define the state machine: draft, in review, changes requested, approved, published, archived, and possibly rolled back. Transitions need capability checks and optimistic concurrency so reviewers do not approve stale edits. Publishing may invalidate caches, rebuild search indexes, or enqueue notifications. Rollback is easiest when previous published versions are retained and can be republished deliberately.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Editing the live row directly before approval.
No clear difference between draft and published reads.
Skipping stale-version checks during approval.
No rollback or history model.

Design a backend workflow where editors create content, reviewers approve it, and published users see only approved versions.

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

Technologies

Tech stacks

Skill areas

Suggest an improvement