65 lines
2.2 KiB
Markdown
65 lines
2.2 KiB
Markdown
# PR-04b - New Project Wizard
|
|
|
|
## Briefing
|
|
|
|
The current project launcher can create a project directly from an inline text field.
|
|
|
|
This PR replaces that minimal path with a dedicated wizard so project creation becomes a guided flow rather than a single-form action.
|
|
|
|
## Objective
|
|
|
|
Introduce a new project wizard that guides project creation before opening the Studio shell.
|
|
|
|
## 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)
|
|
- `PR-03 - Project Launcher and Project Entry Shell`
|
|
- `PR-04a - Project Launcher Window Lifecycle`
|
|
|
|
## Scope
|
|
|
|
- replace inline project creation with a wizard flow
|
|
- support at least:
|
|
- project name
|
|
- project location
|
|
- final confirmation
|
|
- create the project through the existing project service layer
|
|
- open the project after successful creation
|
|
|
|
## Non-Goals
|
|
|
|
- full template marketplace or template system
|
|
- advanced preset configuration
|
|
- remote project provisioning
|
|
|
|
## Execution Method
|
|
|
|
1. Introduce a `New Project Wizard` surface from the launcher.
|
|
2. Split project creation into explicit steps.
|
|
3. Validate project name and location before final confirmation.
|
|
4. Reuse the existing project creation service instead of duplicating creation logic in the UI.
|
|
5. Open the created project after the wizard completes successfully.
|
|
6. Keep the wizard aligned with Studio theming and i18n rules.
|
|
|
|
## Acceptance Criteria
|
|
|
|
- `Create New Project` opens a wizard instead of creating inline immediately
|
|
- the wizard supports name, location, and confirmation steps
|
|
- invalid project data is blocked before creation
|
|
- successful completion creates the project and opens it
|
|
- the flow remains consistent with the launcher/project-entry model
|
|
|
|
## Validation
|
|
|
|
- compile validation of `prometeu-studio`
|
|
- smoke validation of wizard opening and step progression
|
|
- test or smoke coverage for successful project creation
|
|
|
|
## Affected Artifacts
|
|
|
|
- launcher UI
|
|
- project creation flow
|
|
- project service integration
|
|
- entry transition from launcher to shell
|