1. Pick a content type
From the workspace, choose blog post. Studio applies the publisher-native schema (title, slug, lede, body, hero image, byline, tags, publish_at, seo_meta).
2. Configure a publishing destination
Pick edge-native (Studio renders directly to its own subdomain) or a deep CMS integration (WordPress, Ghost). Connect via OAuth or API token; the destination becomes the system of delivery while Studio remains the system of record.
3. Write the first piece
Open a new draft. Write the title and lede. Drop in markdown for the body. Studio saves on every keystroke; the content.draft.saved event fires and any draft-time workflows you have enabled (fact-check, copy edit) start in the background.
4. Request review
Click "request review." This fires content.review.requested. The reviewer (configured per type or per workspace) sees the piece in their queue. Specialists who annotated the draft (fact-checker, copy editor) attach their notes to the same view.
5. Schedule and watch it render
Reviewer clicks approve. Set a publish_at time. Studio waits, then renders to R2, fans out RSS, posts to syndication channels per your configuration, and serves the piece from 300+ PoPs.