Content Calendar

Plan content across channels with campaign, owner, status, asset readiness, and publishing date visible in one weekly schedule. The screen connects Calendar and Drafts so growth teams can find the “Schedule post” action while checking scheduled and drafts.

Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as LinkedIn · Product teardown and Newsletter · Weekly digest, rather than an empty visual shell.

Content Calendar
Use this template in Figr

Template facts

Screen

Calendar

Primary action

Schedule post

Pattern

Calendar

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps users do

Growth teams need a clear “Schedule post” action without losing sight of scheduled, drafts and the affected records. Keep the decision and its outcome clear before moving to the next task.

Key elements

  • Primary action: Schedule post is clearly available where the task happens.
  • Main view: Calendar keeps the starting point obvious.
  • Connected view: Drafts supplies nearby context.
  • Metric: Scheduled is visible with a meaningful value.
  • Another signal: Drafts helps people judge what to do next.
  • Representative record: LinkedIn · Product teardown makes the example specific.
  • Second record: Newsletter · Weekly digest shows the pattern works beyond one item.

States worth designing

  • No availability in selected range; show what people can do instead of leaving a blank panel.
  • Loading calendar without changing the layout unexpectedly.
  • Slot conflict or reschedule; explain the problem and preserve work.
  • Permission denied for drafts; clarify who can continue.
  • Success after choosing Schedule post; confirm the result and the next step.
  • Network or data refresh failure; offer a retry without losing context.

Where this screen sits in the flow

Calendar → Drafts → Schedule post → Review outcome

Patterns used

Calendar, Calendar, Drafts, Campaigns, accessible states, contextual actions

Why these choices work

Show timezone, time range and conflicts before a user commits. Offer a clear path back to available slots.

In this design, people should be able to compare LinkedIn · Product teardown with Newsletter · Weekly digest. Make scheduled clear, then use drafts to explain whether the next step needs attention.

Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Schedule post” action. The happy path alone is not enough.

Related UI examples: Creator Dashboard, Campaign Builder, Audience Segmentation.

Start from this in Figr

Design a content calendar screen for our existing software product. Use our real design-system tokens, components and product language. Show Calendar and Drafts, include believable records such as LinkedIn · Product teardown, and make schedule post easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.

Open Figr