Intrepid/prometeu-studio
Intrepid/prometeu-studio
3
0
Fork 0
Code Pull Requests 1 Activity
prometeu-studio/docs/studio/agendas/01.0. Studio Shell, Workspace Navigation, and Layout Agenda.md
bQUARKz cb786c2663
added agendas studio
2026-03-24 13:42:38 +00:00

2.1 KiB
Raw Blame History

Studio Shell, Workspace Navigation, and Layout Agenda

Status

Open

Purpose

Define the baseline Studio shell:

  • main window layout,
  • workspace navigation model,
  • shell regions and panel hierarchy,
  • default landing behavior,
  • how future workspaces should fit into the frame.

Domain Owner

docs/studio

Current Code Context

Current prometeu-studio already provides:

  • MainView as the root shell;
  • WorkspaceBar as left-side workspace navigation;
  • EditorWorkspace as the most concrete workspace;
  • placeholder workspaces for Assets and Device;
  • a BuilderWorkspace implementation artifact with logs and toolbar.

The shell exists, but it is still closer to a scaffold than a documented Studio UX contract.

Core Questions

  1. What is the long-lived shell structure of the Studio?
  2. Is left-side workspace switching the correct baseline navigation model?
  3. Which shell regions are global and which belong to each workspace?
  4. How should the Assets workspace coexist with Editor, Device, and future shipping flows?
  5. What should the default landing workspace be?

Options

Option A

Keep the current shell mostly intact and grow workspaces within it.

Option B

Evolve toward a multi-panel shell with global activity and contextual side panels.

Option C

Adopt a dock-heavy IDE-style shell from the start.

Tradeoffs

  • Option A is fast and consistent with current code, but may constrain richer workflows later.
  • Option B preserves the current shell while creating room for Studio-grade interaction design.
  • Option C is powerful, but likely too heavy for the current code and service maturity.

Recommendation

Prefer Option B.

Recommended direction:

  • keep workspace switching in the shell,
  • formalize a stable frame with navigation, workspace body, and activity/progress region,
  • let each workspace own its internal panels,
  • avoid a fully dockable IDE model for the first Studio UI wave.

Expected Follow-up

  • a shell decision,
  • a Studio shell spec,
  • a PR/plan for MainView, WorkspaceBar, and workspace composition.