Turn one good idea into a publishing rhythm.
Set up the source, give it a home in the workflow, choose its channels, then publish and learn. This guide keeps the work concrete through four linked databases, one calendar view, and one native production board over the Content Items database.
The operating loop
One source idea → one canonical content item → five channel-ready outputs.
The current Cueweave setup provisions four linked Notion databases — Cueweave Ideas, Cueweave Content Items, Cueweave Platforms, and Cueweave Performance. The six concepts below describe the operating model; Calendar and Production are views over Content Items, while Stage remains the workflow's source of truth. A Performance note is attached to a published Content Item and keeps its review window, signal, metric snapshot, observation, and next iteration together.
The setup sequence
Give every piece a next step.
Work top to bottom. The bold instruction is what you do; the note underneath keeps the current Cueweave implementation honest.
Idea database
Capture one raw premise per row. Add the audience or problem, the useful insight, source notes, and a Low, Medium, or High priority. Keep the idea reusable instead of writing five platform drafts here.
Current Cueweave contract: Cueweave provisions Cueweave Ideas with Name, Notes, Priority (Low, Medium, or High), and a reverse Content relation. New captures default to Medium.
Content database
Create one canonical content item related to the source idea. Give it a clear working title, choose one or more canonical platforms, assign a publish date when known, then use its stage as the single source of truth for progress.
Current Cueweave contract: Cueweave Content Items links back to one Idea, relates to one or more canonical Platforms without duplicating the content row, carries the publish date and stage, and accepts linked Performance notes.
Platform database
Choose the intended channel and format before production. Record channel-specific constraints with the content item so every output has a clear brief.
Current Cueweave contract: Cueweave provisions Cueweave Platforms with Name, Notes, Content, and Performance relations. Content Items links to canonical platform rows instead of copying labels.
Calendar database / view
Open the Cueweave Publishing Calendar on Content Items. Assign a Publish date to each output, then check the month by channel for collisions or missing dates before you move anything to Scheduled.
Current Cueweave contract: Cueweave creates one top-level Cueweave Publishing Calendar view on Cueweave Content Items. It uses Publish date for a month view, shows Platform and Stage on cards, and filters to Scheduled or Published; v1 does not create a separate Calendar database or claim native publishing integrations.
Production board / stages
Move the canonical item through Idea, Draft, Production, Scheduled, and Published. Only call it published after its live link is available.
Current Cueweave contract: Cueweave creates one native Cueweave Production Board view over Cueweave Content Items, grouped by Stage with empty groups visible. It is the current Idea, Draft, Production, Scheduled, and Published flow, not a separate Production database.
Performance database / notes
After publishing, attach a Performance note to the Content Item. Use Published URL when available, then record the Review date, Review window, Signal, Metric snapshot, Observation, Next iteration, and Notes.
Current Cueweave contract: Cueweave provisions Cueweave Performance with Name, Content, Platform, Published URL, Review date, Review window, Signal, Metric snapshot, Observation, Next iteration, and Notes. Attach one note to a published Content Item; all metrics are entered manually in Notion.
The repurposing pass
One published piece, five useful cuts.
Start from the same source idea. Adapt the promise and structure to the channel; do not paste the same draft everywhere.
Completion criterion
Relate all five outputs to the same source idea, choose a platform and date for each, move each through production, publish, then add the performance note.
Five outputs to draft
Check each one off locally as you finish it.
When all five are checked, move them to Published only when their live links are ready. Then record what worked and what you will change next time.