# Design an editorial workspace

Begin with the thing being published and the production rhythm. A publication
calendar, campaign launch, and asset library are different editorial products.

## Optional visual references

[Brand Guide by Matt Bio](https://www.notion.com/templates/brand-guide-bio) offers
inspiration for a compact index, strong typography, and coordinated brand panels.
[Brand Assets by Notion](https://www.notion.com/templates/brand-assets) is a reference
for recognizable asset previews, short labels, and category tabs. The
[content calendar reference](content-calendar-reference.md) supports the production model.
Inspect current previews when adapting their visual details; previews alone do
not establish underlying automation or interactions.

## Compose a connected editorial system

The marketing home is an index into work, not a container for every work surface.
Use a compact identity and a few meaningful destinations. A campaign database
record is the campaign home; content records relate to it and carry the drafts.
A shared Content destination provides production and calendar views without
crowding the marketing home. Use existing brand resources or a useful separate
brand page when the brief supplies guidance. Do not require identical page
structures or a fixed number of databases for every request.

Use the reference patterns at the level where they help: the Brand Guide's
compact index and coordinated sections for brand guidance; the content calendar's
publishing model for the shared production destination; asset previews in a real
asset library. Naming a reference is not evidence that a layout reflects it.
If closer visual fidelity is needed, inspect the linked previews and record the
specific hierarchy, spacing, navigation, or preview treatment being adapted.
Keep this design rationale in the delivery or test report, not the user's work surface.

## Give each destination its own job

- **Marketing home:** a short identity, recognizable navigation, active campaigns,
  and the few items needing attention. No repeated hero slogans or welcome essay.
- **Campaign page:** visible lifecycle properties; a concise brief and linked
  content filtered to this campaign. Use a readable table/list for a handful of
  deliverables. A campaign is part of the larger collection, not a free-floating
  document that duplicates its metadata in paragraphs.
- **Content workspace:** room for a production board or publishing calendar.
  Provide an undated view. Choose the default from the actual work, hide redundant
  card properties (especially status when already grouped by status), and avoid
  an overflowing wall of one-card columns.
- **Deliverable pages:** expose operational properties near the title. Give an
  article a draft and editorial questions; a video a sequence and script; an email
  a subject, preview text, and body. Their bodies should not be identical generic
  brief headings. Keep supporting sources and review detail one level deeper.
- **Brand resources:** concise voice/message guidance and real reusable assets.
  Use recognizable previews only when assets exist. Never fabricate screenshots
  or fill an empty gallery with decorative stock images.

Use typography, spacing, and restrained color consistently across the workspace,
while varying composition by purpose. Select actual page width, font, and database
page layouts where available; neither nesting nor an emoji supplies those settings.
Show fewer properties in overview views than on the record page. Avoid duplicate
headings and links above a linked database. A long title must remain readable.

## Judge the result in Notion

Start in the sidebar and enter the marketing home. Open a campaign, then one
article and a different-format deliverable. Return to the shared Content view and
brand resources. Check that every route works, relations connect the right records,
and campaign filters would exclude another campaign. Inspect the visible property
panel and useful body content, not just the database schema.

At the available width, can an editor find the next publication, the approval
needed, and the working draft without parsing a dense wall of metadata? Check
undated and blocked work remains discoverable. Review the actual rendered output
when available; otherwise disclose that appearance or layouts remain unverified.

In skill tests, retain the raw result and report failures. Improve the skill and
rerun when needed; manual polish after the run does not establish skill quality.
