Studio core workflows
Three recipes: write a page, generate an asset, and hand content off downstream.
Overview
Studio's three tools — CMS editing, HF Pipeline, and the (building) Asset Manager and Social & publish — combine into a few recurring jobs. This page walks through the ones you'll hit most often.
How it works
Every Studio workflow assumes Forge has already scaffolded the site and locked Brand DNA — Studio authors against that manifest, it doesn't define it.
Steps
- •
Workflow 1 — write and ship a page
Open the page's content slots in CMS editing, write with the SEO sidecar open, preview against the real template, and save.
- •
Workflow 2 — generate an on-brand image or clip
Open HF Pipeline, submit a job scoped to a brand and page slot, and review it in staging — nothing publishes automatically.
- •
Workflow 3 — approve and route an asset
Once a staged HF Pipeline job looks right, approve it into the asset library or straight into the page slot it was generated for.
Capabilities
- Structured, template-bound authoring — not freeform page building.
- Staging-first generation — every image or video job lands for review before it's usable live.
- A shared manifest — content and generated assets both plug into the same site definition Forge locked.
Limits & honest scope
- Asset Manager and Social & publish are still building — routing generated content into a library or a social queue today is more manual than the target workflow. Check each page's tier badge.
- Studio doesn't replace an editorial team's judgment about what to actually say on a page.