Publishing Workflow

Move content from draft through review, approval, scheduling, and publication with owners and blockers visible at every stage. This example brings Board and Calendar together so content and product teams can find the next task without losing context.

It includes representative records such as Q4 product update and Enterprise case study. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Publishing Workflow
Use this template in Figr

Template facts

Screen

Board

Primary action

New content

Pattern

Board

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to new content while keeping drafts, in review and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Board gives users an obvious place to start.
  • Supporting view: Calendar keeps the related context close.
  • Primary action: New content stays visible when people need it.
  • First signal: Drafts shows a useful value (18).
  • Second signal: In review gives additional context (7).
  • Sample record: Q4 product update.
  • Next record: Enterprise case study.

States worth designing

  • No cards in this stage: say what changed, protect progress, and offer a clear next step.
  • Movement in progress: say what changed, protect progress, and offer a clear next step.
  • Move blocked by rules: say what changed, protect progress, and offer a clear next step.
  • Ownership updated: say what changed, protect progress, and offer a clear next step.
  • Archived item restored: say what changed, protect progress, and offer a clear next step.
  • Permission to edit missing: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Board → Calendar → New content → Review outcome

Patterns used

Board, Board, Calendar, contextual actions, error recovery

Why these choices work

Use real domain stages with a clear owner. Confirm high-impact moves and explain when permissions or missing work block an item.

Pay attention to board and calendar. People need to distinguish Q4 product update from Enterprise case study. Keep drafts visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “New content”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Version History, Editorial Review, Media Upload.

Start from this in Figr

Design a publishing workflow screen inside our existing product. Use our current components, tokens and content language. Include Board and Calendar views, credible records like Q4 product update, and a clear “New content” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr