71 lines
2.6 KiB
Markdown
71 lines
2.6 KiB
Markdown
# PR-03 - Project Launcher and Project Entry Shell
|
|
|
|
## Briefing
|
|
|
|
The Studio shell spec requires a project launcher or home surface before the main workspace shell.
|
|
|
|
This PR introduces that first real user entry flow so the Studio can:
|
|
|
|
- show existing or recent projects,
|
|
- open a project,
|
|
- create a new project,
|
|
- then enter the main shell intentionally.
|
|
|
|
## Objective
|
|
|
|
Implement the first project entry experience for the Studio and connect it to the shell and event model.
|
|
|
|
## Dependencies
|
|
|
|
- [`../specs/1. Studio Shell and Workspace Layout Specification.md`](../specs/1.%20Studio%20Shell%20and%20Workspace%20Layout%20Specification.md)
|
|
- [`../specs/2. Studio UI Foundations Specification.md`](../specs/2.%20Studio%20UI%20Foundations%20Specification.md)
|
|
- [`../specs/3. Studio Components Module Specification.md`](../specs/3.%20Studio%20Components%20Module%20Specification.md)
|
|
- `PR-01 - StudioEventBus Foundation`
|
|
- `PR-02 - Studio Shell Components Wave 1`
|
|
|
|
## Scope
|
|
|
|
- add a launcher or home surface before the shell
|
|
- show existing or recent projects
|
|
- expose `Open Project` and `Create Project`
|
|
- enter the main shell only after project selection or creation
|
|
- publish the relevant Studio events for project entry
|
|
|
|
## Non-Goals
|
|
|
|
- implementing the full asset-management workspace
|
|
- implementing all future project metadata and history policy
|
|
- finalizing shipper workflows
|
|
- introducing remote project management behavior
|
|
|
|
## Execution Method
|
|
|
|
1. Introduce a project launcher or home view in the Studio entry flow.
|
|
2. Add a minimal project list surface for existing or recent projects.
|
|
3. Add actions for `Open Project` and `Create Project`.
|
|
4. Route project entry through the Studio event model where appropriate.
|
|
5. Enter the main shell only after a concrete project action completes.
|
|
6. Keep the shell and launcher aligned with i18n, themes, and Studio controls.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- the Studio no longer lands directly in a workspace by default
|
|
- the user can see existing or recent projects from the launcher
|
|
- the user can trigger `Open Project`
|
|
- the user can trigger `Create Project`
|
|
- entering the main shell requires a concrete selected or created project
|
|
- project entry behavior is aligned with the shell spec
|
|
|
|
## Validation
|
|
|
|
- compile validation of `prometeu-studio` and `prometeu-studio-components`
|
|
- smoke validation that the launcher appears before the shell
|
|
- smoke validation of open/create project entry paths
|
|
|
|
## Affected Artifacts
|
|
|
|
- `prometeu-studio` application entry flow
|
|
- shell composition
|
|
- `prometeu-studio-components` shell and launcher controls
|
|
- Studio event publication for project entry
|