Workflow & publishing
Every item moves through a defined workflow before it reaches your audience — draft, review, approval, processing, published. Publishing can be scheduled in advance, access is gated on two independent dimensions, and a health dashboard catches what slipped.
The workflow
Content follows a state machine. Each transition can fire background work on the way in or out — start transcoding when an item enters processing, notify reviewers when it enters approval — and every move is recorded with who did it and when.
Scheduled publishing
A workflow plan schedules a transition for a future moment. Set an article to publish at 9am, lift an embargo the instant it ends, or rotate seasonal content in and out — no one has to be at a keyboard when it happens.
Visibility
Being published isn't the same as being public. Access depends on two independent things: the workflow state, and a set of visibility flags. Both have to line up — a published item with its public flag off stays private.
Keeping it healthy
Two safety nets run over a live library: a health dashboard that flags problems, and a moderation flow that keeps community content in check.
A dashboard of aggregate stats plus a triage list — click an issue to jump straight to the item. Its checks include:
Threaded comments on any item, gated by per-item switches and a moderation flow that runs before anything appears.
The moderation logic is a pipeline you can shape — automatic checks, human review, or both.
Keep exploring
What the content engine is, and how a piece of content moves through it.
Collections, metadata, and the typed items that fill your library.
Real-time collaborative documents, guides, data forms, and templates.
Adaptive streaming, quality tiers, previews, and auto-transcription.