Add Blueprint details step to blueprint selection flow#2571
Merged
ivan-ottinger merged 6 commits intotrunkfrom Feb 17, 2026
Merged
Conversation
7149173 to
c52b647
Compare
c52b647 to
da80bf4
Compare
bcotrim
requested changes
Feb 13, 2026
Contributor
bcotrim
left a comment
There was a problem hiding this comment.
LGTM and works as described!
Could we clean up the blueprintWarnings from blueprints.tsx since we no longer use it?
Reuse the deeplink confirmation screen (BlueprintDeeplink) as a new intermediate step when selecting blueprints. The manual blueprint flow now has three steps: Choose Blueprint → Blueprint details → Site name & details. File uploads navigate directly to the Blueprint details step. The BlueprintDeeplink component now supports a source prop to show contextual footer text for deeplink, file, and featured blueprints.
Rename blueprintDeeplinkWarnings to blueprintWarnings and use it for both the deeplink and file upload flows, removing the separate fileBlueprintWarnings local state. Also remove the local warning state update in blueprints.tsx to prevent a brief flash of the warning notice on the grid screen before navigating to the details step.
The component is now used for both deeplink and manual blueprint selection flows, so the name better reflects its broader purpose.
Moving the warnings cleanup from back navigation to the blueprint change handler preserves warnings when returning to the grid and re-entering the details step with the same file blueprint.
The local blueprintWarnings state was never set to a non-undefined value after consolidating warnings into the shared parent state.
7a687ae to
6ab1ae4
Compare
Contributor
Author
Thanks for the review, Bernardo! Good catch! I've removed the unused |
Collaborator
📊 Performance Test ResultsComparing 6ab1ae4 vs trunk site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff) |
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issues
Proposed Changes
BlueprintDetails) for both deeplink and manual flows, with a dynamic source indicator (deeplink, file, or featured)blueprintDeeplinkWarningsand file blueprint warnings into a single sharedblueprintWarningsstateBlueprintDeeplinkcomponent toBlueprintDetailsto reflect its broader usageCleanShot.2026-02-13.at.13.41.18.mp4
Testing Instructions
Pre-merge Checklist