Launch Site Flow Standardization: Add WP Admin masterbar variations by zaguiini · Pull Request #47705 · Automattic/jetpack

zaguiini · 2026-03-20T00:01:13Z

Fixes DATSCI-1168

Proposed changes

This PR standardizes the "Launch site" flow for the WP Admin masterbar entry point, under a calypso_standardized_site_launch_gating ExPlat experiment.

Control (experiment not assigned): The existing behaviour — clicking "Launch site" in the masterbar redirects to wordpress.com/start/launch-site.

Treatment (ungated_site_launch variation): The launch is performed directly from WP Admin without a redirect:

For Simple sites: calls POST /sites/{blog_id}/launch directly via wpcom-proxy-request
For Atomic sites: calls a new local proxy endpoint POST /wpcom/v2/launch-site, which tunnels the request to WPCOM via the Jetpack connection
On success, shows the CelebrateLaunchModal in place

Shared infrastructure added for future use:

useLaunchSiteMutation hook extracted to common/hooks/ so the Reading Settings "Launch site" CTA can reuse it in a follow-up PR
CelebrateLaunchModal moved from wpcom-dashboard-widgets/celebrate-launch/ to common/ since it is now used in multiple entry points
JetpackScriptData.site.wpcom.blog_id populated on admin pages via a new jetpack_admin_js_script_data filter, so Simple sites have the blog ID available client-side

Other information

Generate changelog entries for this PR (using AI).

Related product discussion/links

DATSCI-1168

Does this pull request change what data or activity we track or use?

No.

Testing instructions

Prerequisites: An unlaunched Simple or Atomic site, assigned to the ungated_site_launch variation of the calypso_standardized_site_launch_gating ExPlat experiment.

Simple site (treatment):

Go to WP Admin on an unlaunched Simple site
Confirm the "Launch site" button is visible in the masterbar
Click "Launch site"
Verify no redirect occurs — the site launches in place and the celebration modal appears
Confirm the modal shows the correct domain, plan upsell, and "View site" link

Atomic site (treatment):

Repeat the above steps on an unlaunched Atomic (WoA) site
Verify the launch is proxied correctly through /wpcom/v2/launch-site and the celebration modal appears

Control (no experiment assignment):

On an unlaunched site without the experiment variation
Click "Launch site" — confirm it redirects to wordpress.com/start/launch-site as before

github-actions · 2026-03-20T00:02:08Z

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the datsci-1168-standardize-site-launch-wp-admin-masterbar-entry-point branch.
To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack datsci-1168-standardize-site-launch-wp-admin-masterbar-entry-point

bin/jetpack-downloader test jetpack-mu-wpcom-plugin datsci-1168-standardize-site-launch-wp-admin-masterbar-entry-point

Interested in more tips and information?

In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
Read more about our development workflow here: PCYsg-eg0-p2
Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

github-actions · 2026-03-20T00:02:29Z

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

✅ Include a description of your PR changes.
✅ Add a "[Status]" label (In Progress, Needs Review, ...).
✅ Add testing instructions.
✅ Specify whether this PR includes any changes to data or privacy.
✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

Follow this PR Review Process:

Ensure all required checks appearing at the bottom of this PR are passing.
Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
You can use GitHub's Reviewers functionality to request a review.
When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

jp-launch-control · 2026-03-20T00:21:10Z

Code Coverage Summary

Coverage changed in 3 files.

File	Coverage	Δ%	Δ Uncovered
projects/packages/jetpack-mu-wpcom/src/features/launch-button/index.php	0/70 (0.00%)	0.00%	17 💔
projects/packages/explat/src/class-rest-controller.php	0/62 (0.00%)	0.00%	5 💔
projects/packages/jetpack-mu-wpcom/src/class-jetpack-mu-wpcom.php	0/356 (0.00%)	0.00%	5 💔

1 file is newly checked for coverage.

File	Coverage
projects/packages/jetpack-mu-wpcom/src/features/wpcom-endpoints/class-wpcom-rest-api-v2-endpoint-jetpack-launch-site.php	0/35 (0.00%) 💔

Full summary · PHP report · JS report

_{If appropriate, add one of these labels to override the failing coverage check:

Covered by non-unit tests
Use to ignore the Code coverage requirement check when E2Es or other non-unit tests cover the code

Coverage tests to be added later
Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR

I don't care about code coverage for this PR
Use this label to ignore the check for insufficient code coveage.}

zaguiini · 2026-03-21T02:34:09Z

projects/packages/jetpack-mu-wpcom/src/features/launch-button/index.php

 */
 function wpcom_enqueue_launch_button_styles() {
-	if ( ! current_user_can( 'manage_options' ) ) {
+	// phpcs:ignore WordPress.Security.NonceVerification.Recommended -- This is a context check, not a form submission.


We were rendering the masterbar while loading the preview and that was assigning the user unintentionally. This snippet prevents loading the scripts twice.

projects/packages/jetpack-mu-wpcom/src/features/launch-button/launch-button.js

…P Admin masterbar Adds the actual API call to the Launch site button for both Simple sites (via wpcom-proxy-request) and Atomic sites (via a new /wpcom/v2/launch-site proxy endpoint that tunnels through the Jetpack connection). Also populates JetpackScriptData.site.wpcom.blog_id for Atomic so the Simple site path has the correct blog ID available. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…_Site class declaration Guard the class with class_exists() to prevent a fatal redeclaration conflict when the same class is already loaded from WPCOM core's rest-api-plugins on Simple sites.

…aunch_Site Rename WPCOM_REST_API_V2_Endpoint_Launch_Site to WPCOM_REST_API_V2_Endpoint_Jetpack_Launch_Site to avoid a fatal conflict with the identically named class in WPCOM core's rest-api-plugins.

…ton/index.php Enqueue site data (siteUrl, siteDomain, sitePlan, hasCustomDomain) as an inline script in the launch button enqueue hook, so CelebrateLaunchModal has the data it needs regardless of whether the user is on the dashboard page.

…com/v2 - Switch from as_blog to as_user to allow user-level launch action

Moves the mutation logic out of LaunchButton into a reusable useLaunchSiteMutation hook in common/hooks, so it can be shared with the upcoming Reading Settings launch flow.

The modal is now used by both the masterbar launch button and the dashboard widgets, so it belongs in common/ rather than scoped to wpcom-dashboard-widgets.

github-actions bot added [mu wpcom Feature] Launch Button [Package] Explat [Package] Jetpack mu wpcom WordPress.com Features [Status] In Progress labels Mar 20, 2026

github-actions bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label Mar 20, 2026

zaguiini force-pushed the datsci-1168-standardize-site-launch-wp-admin-masterbar-entry-point branch from 6842dac to 7ca320c Compare March 20, 2026 21:54

zaguiini changed the title ~~Launch Site Flow Standardization: Add WP Admin variations~~ Launch Site Flow Standardization: Add WP Admin masterbar variations Mar 21, 2026

zaguiini commented Mar 21, 2026

View reviewed changes

github-actions bot added the [mu wpcom Feature] Wpcom Endpoints label Mar 27, 2026

bogiii self-assigned this Mar 27, 2026

zaguiini commented Mar 27, 2026

View reviewed changes

projects/packages/jetpack-mu-wpcom/src/features/launch-button/launch-button.js Outdated Show resolved Hide resolved

github-actions bot added the [mu wpcom Feature] Wpcom Dashboard Widgets label Mar 27, 2026

zaguiini and others added 12 commits March 28, 2026 01:09

Launch Site Flow Standardization: Add WP Admin masterbar variations

b1b49b4

Change user agent to assign the experiment in production

c280d19

Address feedback

3a7d5e0

Fix fatal error caused by duplicate WPCOM_REST_API_V2_Endpoint_Launch…

0bda094

…_Site class declaration Guard the class with class_exists() to prevent a fatal redeclaration conflict when the same class is already loaded from WPCOM core's rest-api-plugins on Simple sites.

Fix fatal class redeclaration by renaming endpoint class to Jetpack_L…

3f5c392

…aunch_Site Rename WPCOM_REST_API_V2_Endpoint_Launch_Site to WPCOM_REST_API_V2_Endpoint_Jetpack_Launch_Site to avoid a fatal conflict with the identically named class in WPCOM core's rest-api-plugins.

Fix launch site on Atomic: use wpcom_json_api_request_as_user with wp…

448d384

…com/v2 - Switch from as_blog to as_user to allow user-level launch action

Extract launch site API call into shared useLaunchSiteMutation hook

7c871c7

Moves the mutation logic out of LaunchButton into a reusable useLaunchSiteMutation hook in common/hooks, so it can be shared with the upcoming Reading Settings launch flow.

Move CelebrateLaunchModal to common/ for shared use

f86de5b

The modal is now used by both the masterbar launch button and the dashboard widgets, so it belongs in common/ rather than scoped to wpcom-dashboard-widgets.

Changelog

45bc4e0

Launch site: stay on page after modal close

ae53c8e

bogiii force-pushed the datsci-1168-standardize-site-launch-wp-admin-masterbar-entry-point branch from a199c66 to ae53c8e Compare March 28, 2026 00:11

bogiii requested a review from a team March 28, 2026 00:12

bogiii marked this pull request as ready for review March 28, 2026 00:27

bogiii mentioned this pull request Mar 30, 2026

Launch Site Flow Standardization: Add WP Admin Launchpad variations #47832

Draft

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Launch Site Flow Standardization: Add WP Admin masterbar variations#47705

Launch Site Flow Standardization: Add WP Admin masterbar variations#47705
zaguiini wants to merge 12 commits intotrunkfrom
datsci-1168-standardize-site-launch-wp-admin-masterbar-entry-point

zaguiini commented Mar 20, 2026 •

edited by bogiii

Loading

Uh oh!

github-actions bot commented Mar 20, 2026 •

edited

Loading

Uh oh!

github-actions bot commented Mar 20, 2026 •

edited

Loading

Uh oh!

jp-launch-control bot commented Mar 20, 2026 •

edited

Loading

Uh oh!

zaguiini Mar 21, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

zaguiini commented Mar 20, 2026 • edited by bogiii Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposed changes

Other information

Related product discussion/links

Does this pull request change what data or activity we track or use?

Testing instructions

Uh oh!

github-actions bot commented Mar 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Mar 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jp-launch-control bot commented Mar 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Coverage Summary

Uh oh!

zaguiini Mar 21, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

zaguiini commented Mar 20, 2026 •

edited by bogiii

Loading

github-actions bot commented Mar 20, 2026 •

edited

Loading

github-actions bot commented Mar 20, 2026 •

edited

Loading

jp-launch-control bot commented Mar 20, 2026 •

edited

Loading