Skip to content

Add Blueprint details step to blueprint selection flow#2571

Merged
ivan-ottinger merged 6 commits intotrunkfrom
stu-1196-studio-update-blueprint-selection-to-reuse-deeplink-confirmation
Feb 17, 2026
Merged

Add Blueprint details step to blueprint selection flow#2571
ivan-ottinger merged 6 commits intotrunkfrom
stu-1196-studio-update-blueprint-selection-to-reuse-deeplink-confirmation

Conversation

@ivan-ottinger
Copy link
Copy Markdown
Contributor

@ivan-ottinger ivan-ottinger commented Feb 11, 2026

Related issues

Proposed Changes

  • Add a "Blueprint details" intermediate step to the manual blueprint selection flow, making it a 3-step process: Choose Blueprint → Blueprint details → Site name & details
  • Reuse the existing deeplink confirmation screen (BlueprintDetails) for both deeplink and manual flows, with a dynamic source indicator (deeplink, file, or featured)
  • Navigate directly from file upload on the grid to the Blueprint details step
  • Consolidate blueprintDeeplinkWarnings and file blueprint warnings into a single shared blueprintWarnings state
  • Rename BlueprintDeeplink component to BlueprintDetails to reflect its broader usage
CleanShot.2026-02-13.at.13.41.18.mp4

Testing Instructions

  1. Open Studio and go to "Add Site"
  2. Select "Start from a Blueprint" to see the blueprint grid
  3. Click a featured blueprint and click "Continue" — verify the new Blueprint details step shows with "Featured Blueprint" in the footer
  4. Click "Back" to return to the grid, then click "Continue" again — verify the details step still works
  5. Upload a blueprint JSON file with warnings (you can use example blueprints from here: 3a658-pb) — verify it navigates to the Blueprint details step with "Blueprint loaded from file" in the footer and warnings displayed
  6. Click "Back" to return to the grid, then click "Continue" — verify the file warnings are still shown
  7. Select a different featured blueprint — verify any file warnings are cleared
  8. Test the deeplink flow by opening a blueprint URL (you can use example blueprint deeplinks from here: https://jsbin.com/kulaqijega/1/edit?html,css,output) — verify the 2-step deeplink flow still works with "Blueprint loaded from URL" in the footer
  9. Verify the stepper shows 3 steps for manual flow and 2 steps for deeplink flow
  10. Creating a site with any blueprint selected should work well

Pre-merge Checklist

  • Have you checked for TypeScript, React or other console errors?

@ivan-ottinger ivan-ottinger self-assigned this Feb 11, 2026
@ivan-ottinger ivan-ottinger force-pushed the stu-1196-studio-update-blueprint-selection-to-reuse-deeplink-confirmation branch 2 times, most recently from 7149173 to c52b647 Compare February 13, 2026 10:53
@ivan-ottinger ivan-ottinger marked this pull request as ready for review February 13, 2026 12:42
@ivan-ottinger ivan-ottinger force-pushed the stu-1196-studio-update-blueprint-selection-to-reuse-deeplink-confirmation branch from c52b647 to da80bf4 Compare February 13, 2026 12:42
@ivan-ottinger ivan-ottinger requested a review from a team February 13, 2026 12:45
Copy link
Copy Markdown
Contributor

@bcotrim bcotrim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
@ivan-ottinger ivan-ottinger force-pushed the stu-1196-studio-update-blueprint-selection-to-reuse-deeplink-confirmation branch from 7a687ae to 6ab1ae4 Compare February 17, 2026 09:52
@ivan-ottinger
Copy link
Copy Markdown
Contributor Author

LGTM and works as described!

Could we clean up the blueprintWarnings from blueprints.tsx since we no longer use it?

Thanks for the review, Bernardo! Good catch! I've removed the unused
blueprintWarnings state and the BlueprintWarningNotice rendering from
blueprints.tsx in commit 6ab1ae4.

@wpmobilebot
Copy link
Copy Markdown
Collaborator

📊 Performance Test Results

Comparing 6ab1ae4 vs trunk

site-editor

Metric trunk 6ab1ae4 Diff Change
load 2712.00 ms 2712.00 ms 0.00 ms ⚪ 0.0%

site-startup

Metric trunk 6ab1ae4 Diff Change
siteCreation 7079.00 ms 6077.00 ms -1002.00 ms 🟢 -14.2%
siteStartup 3928.00 ms 3931.00 ms +3.00 ms ⚪ 0.0%

Results are median values from multiple test runs.

Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff)

Copy link
Copy Markdown
Contributor

@bcotrim bcotrim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@ivan-ottinger ivan-ottinger merged commit 51b47d5 into trunk Feb 17, 2026
9 checks passed
@ivan-ottinger ivan-ottinger deleted the stu-1196-studio-update-blueprint-selection-to-reuse-deeplink-confirmation branch February 17, 2026 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants