Handbook
Studio — navigation and shell
How the Forge Studio SPA structures top navigation, section sidebars, and client routes under /studio/, grounded in lenses-enterprise/src/App.tsx. For the exhaustive route checklist, bookmark the Studio route atlas.
Updated
What it is
How the Forge Studio SPA structures top navigation, section sidebars, and client routes under /studio/, grounded in lenses-enterprise/src/App.tsx. For the exhaustive route checklist, bookmark the Studio route atlas.
When to use it
- Onboarding operators who need screen labels tied to URL tokens.
- Before filing bugs about “missing sidebar” — confirm which route family you are in.
Route families (summary)
The canonical path checklist (every projects/... token, Settings, Governance, and embedded viewers) lives in the Studio route atlas. Use this page for shell behavior; use the atlas when you need the full table.
| Concern | Read |
|---|---|
| Project hub, charts, strategy | Workspace and projects |
| Per-project Docs Health UI | Docs Health in Studio UI |
| LLM, Fleet, experiments settings | Studio LLM and Fleet settings |
| Blank shell, assets, API origin | Studio troubleshooting |
Governance and productivity (quick pointer)
Governance (governance/connectors, governance/audit) and Productivity (toolset, toolset/:name) share the same shell: sidebar entries map to nested <Route> blocks in App.tsx. Deep API notes remain in Schemas and API for builders.
Verify
Open /studio/ and switch two top-level areas; the URL should change under /studio/... and the sidebar should list the same families described in the atlas table.