Handbook
Studio 201 — Day-to-day use
Using Forge Studio for regular work: switching between workspace lenses (for example Flow vs Artifacts), moving between Plans, Projects, and Knowledge, and keeping context while you work.
What it is
Using Forge Studio for regular work: switching between workspace lenses (for example Flow vs Artifacts), moving between Plans, Projects, and Knowledge, and keeping context while you work.
When to use it
After Studio 101, when Studio is your default surface.
Prerequisites
- Studio loads reliably at
/studio/.
Flow vs Artifacts (decision guide)
| Lens | Prefer when… | You usually leave with… |
|---|---|---|
| Flow | You are tracking delivery steps, handoffs, or “what happens next” | A clear next action on the plan or board |
| Artifacts | You need roadmaps, boards, or document-shaped views your build exposes | A stable view of scope and status artifacts |
If you are unsure, start in Flow for execution days and Artifacts for planning or review meetings.
Recurring jobs (examples)
| Job | A simple Studio path |
|---|---|
| Daily stand-in | Workspace → one project → latest plan or board note |
| Prep for refinement | Artifacts (if available) → scope slice for the increment |
| Cross-team alignment | Same project in Studio, then confirm the same project in Classic at / if a report only exists there |
Do / avoid
| Do | Avoid |
|---|---|
| Pick one project per short session and finish one loop | Switching workspace roots mid-session without reason |
| Name sessions and plans the way your team already searches | Treating chart views as canonical if Classic disagrees |
Steps
-
Pick a lens — Use the workspace lens switcher when present (names vary by build). Flow emphasizes delivery flow; Artifacts emphasizes roadmaps and boards where your build exposes them.
-
Stay oriented — Use the top navigation and project pickers the way your team agrees (same concepts exist in Classic under different chrome).
-
Typical half-hour — Open the workspace, drill into one project, open one plan or document linked from that project, then return to the workspace home. Adjust to your methodology.
-
Charts and embeds — Some builds expose chart views under Studio; treat them as secondary unless your team standardized on them.
How to verify success
- You can repeat the path without memorizing URLs or repo paths.
- You know when to switch back to Classic at
/if a flow is not in Studio yet.