Manage the Content Library and Statuses
Find, filter, and advance every content item in **Contents**—across calendar origins—with clear editorial and CMS status handling.
Overview
Contents is the production library for your workspace: every article, post, and asset with a content record, whether it originated from strategy generation, a campaign brief, an opportunity, manual calendar entry, or scratch creation.
Use it when the calendar’s date-centric view is the wrong lens—you need full-text search, status dashboards, bulk filters, or a flat list sorted by last updated. Each row exposes brief status (when a brief exists), editorial status, and CMS status so you can triage without opening every item.
When to use
- You manage more drafts than fit comfortably in calendar briefs view.
- You filter by In review, Approved, or CMS failed for weekly ops.
- You locate a piece by title without remembering its planned date.
- You audit workspace production across Strategy, Campaign, Opportunity, and Manual origins.
Before you start
- Confirm the active workspace—Contents is workspace-scoped like the calendar.
- Understand the three status columns:
– Brief status — planning validation (only when linked to a calendar brief) – Editorial status — internal production workflow – CMS status — WordPress / Webflow sync state
- Know that editorial and CMS statuses are independent; filter each deliberately.
Steps
- Open Contents from the sidebar.
- Use search by title or keyword when you know the piece name.
- Apply filters:
– Editorial status — for example In review for approvers, Approved ready to publish – CMS status — for example CMS failed for integration fixes – Channel or content type — to batch similar work – Brief status — when separating planning backlog from production backlog
- Sort by Planned date, Updated, or Created depending on your sprint rhythm.
- Open an item to edit in the content editor, or use row actions when available (open, delete, status change).
- Advance workflow from the editor:
– Writers move items In progress → In review – Approvers set Approved – Publishers push to CMS and verify CMS published
- For items stuck without drafts, jump to Calendar via the linked brief or planned date and run Generate draft.
- Archive or remove obsolete items—removal may delete linked briefs; confirm before bulk delete.
Expected result
- You can answer “what needs review this week?” and “what failed to publish?” from one list.
- Status filters match how your team divides planning vs writing vs publishing duties.
- Items from all calendar layers appear alongside from-scratch content in one library.
- Editorial Approved items are clearly separated from CMS-synced live posts.
Tips
- Calendar vs Contents — Calendar optimizes when and whether to plan; Contents optimizes what is written and publish-ready.
- Filter In review, not Draft — Approver queues should target In review; Draft often means the writer has not submitted yet.
- CMS failed — Fix integration credentials or slug conflicts in the editor, then retry publish; editorial status may still be Approved.
- Brief approved, no body — Filter brief Approved + editorial empty or Draft with no content flag; batch generate from calendar.
- Multi-origin reporting — Use channel and date filters rather than layer (layer lives on calendar items; Contents may show origin badges when present).
Next step
Understand Brief and Editorial Statuses for the full status reference, then Publish Content as a Draft or Live Post for CMS push.
Ready to try this in CntX?
Open the product and apply this guide to your workspace.