Skip to content

Social: roll out the modernized dashboard to 100%#50092

Draft
dhasilva wants to merge 1 commit into
trunkfrom
release/social-dashboard
Draft

Social: roll out the modernized dashboard to 100%#50092
dhasilva wants to merge 1 commit into
trunkfrom
release/social-dashboard

Conversation

@dhasilva

@dhasilva dhasilva commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Fixes #

Brings the modernized Jetpack Social wp-admin dashboard to 100% on the Jetpack side, mirroring the Newsletter rollout (#50091).

Do not merge until the Simple-site cohort reaches 100% on the WordPress.com backend. Like Newsletter, the Simple rollout is staged from a wpcom server-side flag; this PR flips the Jetpack-side default, which takes effect on Atomic (WoA) and self-hosted Jetpack sites immediately on merge. Holding it open until Simple is at 100% keeps the two paths consistent.

Proposed changes

  • Flip the rsm_jetpack_ui_modernization_social gate (Social_Admin_Page::is_modernized()) default from false to true, so the wp-build Social dashboard (Overview + Settings tabs) loads by default instead of the legacy single-page React app.
  • The function_exists( 'jetpack_social_..._render_page' ) guard in is_wp_build_dashboard_active() is unchanged, so a site still falls back to the legacy bundle if the wp-build chassis isn't available.
  • Opt-out is unchanged: hosts (and a11ns who want the legacy view back) can still force the legacy experience with add_filter( 'rsm_jetpack_ui_modernization_social', '__return_false' ) — exercised by the existing kill-switch test.
  • Unlike Newsletter, the Social gate had no Jetpack-side cohort scaffolding to remove (no rollout-percentage constant, a12s carve-out, or blog-ID bucket — its staged rollout lives entirely wpcom-side), so this is a single default flip plus the matching test.

Related product discussion/links

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

No.

Testing instructions

  • On a connected Atomic (WoA) or self-hosted Jetpack site, go to Jetpack → Social (admin.php?page=jetpack-social) and confirm the modernized wp-build dashboard (Overview + Settings tabs) loads by default, instead of the legacy single-page screen.
  • Confirm the host opt-out still wins: add_filter( 'rsm_jetpack_ui_modernization_social', '__return_false' ); restores the legacy Social admin screen.
  • PHP unit tests: composer phpunit in projects/packages/publicize (113 tests pass; --filter Social_Admin_Page_Test covers the new default-on behavior, the explicit-on case, and the kill switch).

🤖 Generated with Claude Code

Flip the `rsm_jetpack_ui_modernization_social` gate default from false to
true so the modernized wp-build Social dashboard loads by default on
Atomic and self-hosted Jetpack sites. Simple is driven separately from
the WordPress.com backend, so this PR stays open until that cohort
reaches 100%. Hosts (and a11ns who want the legacy view back) can still
opt out with add_filter( 'rsm_jetpack_ui_modernization_social', '__return_false' ).

Unlike Newsletter, the Social gate carried no Jetpack-side cohort
scaffolding to remove — its staged rollout lives entirely on the wpcom
side — so this is a single default flip plus the matching test.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

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), and enable the release/social-dashboard branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack release/social-dashboard

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

Copy link
Copy Markdown
Contributor

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:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. 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!

@dhasilva dhasilva marked this pull request as draft June 30, 2026 22:25
@jp-launch-control

Copy link
Copy Markdown

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment