What the calendar stores
A calendar entry can store date, title, publish time, target platforms, hook, angle, CTA, tags, shot list, and status. Status currently supports idea, draft, scheduled, and published.
Manual and artifact-synced entries
You can add entries manually, or approve a content-calendar Artifact generated by a Skill. Editing a synced entry turns it into a manual override so later imports do not silently overwrite your changes.
Fanout from one calendar item
When an entry has one or more target platforms, Lumo can start a new planning run for scripts, metadata, covers, or all deliverables. The generated prompt includes the entry title, date, platforms, hook, angle, CTA, tags, and an inferred cover aspect ratio.
Vertical-first platforms such as Douyin, Xiaohongshu, and TikTok lean toward 9:16; horizontal platforms default toward 16:9.
Content-calendar Artifact format
The app recognizes a content-calendar JSON payload and renders it as a calendar preview before you approve it into the calendar panel.
{
"type": "content-calendar",
"weekStart": "2026-05-04",
"timezone": "America/Los_Angeles",
"items": [
{
"id": "post-01",
"date": "2026-05-06",
"platform": "youtube",
"title": "Reviewing an AI tool workflow",
"hook": "Why does the same tool simplify work for some people and create more chaos for others?",
"status": "idea"
}
]
}Plan by publishing decision, not by empty slots
Use the calendar to capture the decisions that affect production: why this topic matters now, which platform gets the main version, what hook should open the piece, what CTA belongs at the end, and which assets are still missing. A calendar with fewer but clearer entries is more useful than a crowded calendar full of vague titles.
Use status as a production signal
Idea means the topic is still being shaped. Draft means there is a script or working outline. Scheduled means publishing time and platform are set. Published means the item has left Lumo and can be used later as learning material. Keeping status honest helps the next Skill choose the right task.
Turn one idea into platform-specific work
A single topic can produce different work by platform. YouTube may need a longer outline and thumbnail direction, Xiaohongshu may need a sharper title and visual note, Douyin or TikTok may need a fast hook and vertical cut list, and Bilibili may need context and chapter structure. Keep those differences in the entry instead of hiding them in separate chats.
Review generated calendars before importing
When a Skill generates a content-calendar Artifact, scan the dates, platform mix, repeated topics, asset requirements, and publishing load before approving it. If it is too dense, ask Lumo to reduce the schedule or focus only on the next week.
Do not approve a generated calendar just because it looks complete. Check whether you can actually produce it.