Skip to content

Admin Menu: Consolidate "Dashboard" and "My Home" menus #43983

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Jun 19, 2025

Conversation

mmtr
Copy link
Member

@mmtr mmtr commented Jun 17, 2025

Fixes DOTCOM-13618 and DOTCOM-13312

Proposed changes:

  • Stops replacing the "Dashboard" menu with "My Home". This way, the "Dashboard" menu is consistently visible across all sites (previously, only visible with the classic admin interface).
  • Always registers "My Home" as a top-level menu, so it's consistently in the same level across all sites (previously, it was a submenu of "Hosting" on sites with the classic admin interface).
Interface Site Before After
Default Simple Screenshot 2025-06-17 at 16 18 54 Screenshot 2025-06-17 at 16 22 38
Default Atomic Screenshot 2025-06-17 at 16 20 33 Screenshot 2025-06-17 at 17 02 26
Classic Simple Screenshot 2025-06-17 at 16 19 28 Screenshot 2025-06-17 at 16 23 58
Classic Atomic Screenshot 2025-06-17 at 16 22 02 Screenshot 2025-06-17 at 17 01 42

Note that the "Dashboard > Updates" submenu is still not visible on Simple sites, so the "Dashboard" menu won't display any submenus. In a follow-up (see DOTCOM-13619), we'll add "Dashboard > Updates" to Simple sites, and this will cause the "Dashboard > Home" to show up.

Other information:

  • Have you written new tests for your changes, if applicable?
  • Have you checked the E2E test CI results, and verified that your changes do not break them?
  • Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

N/A

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

No

Testing instructions:

  • Apply these changes to a WP.com Simple site and to a WP.com Atomic site.
  • Test the following scenarios:
    • Simple site / Default admin interface (Calypso)
      • Dashboard: ✅ Visible
      • My Home: ✅ Visible
    • Atomic site / Default admin interface (Calypso)
      • Dashboard > Home: ✅ Visible
      • Dashboard > Updates: ✅ Visible
      • My Home: ✅ Visible
      • My Home > Updates: ❌ Not visible
    • Simple site / Classic admin interface (WP Admin)
      • Dashboard: ✅ Visible
      • My Home: ✅ Visible
      • Hosting > My Home: ❌ Not visible
    • Atomic site / Classic admin interface (WP Admin)
      • Dashboard > Home: ✅ Visible
      • Dashboard > Updates: ✅ Visible
      • My Home: ✅ Visible
      • Hosting > My Home: ❌ Not visible

@mmtr mmtr self-assigned this Jun 17, 2025
@mmtr mmtr added [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it [Status] Needs Team Review Obsolete. Use Needs Review instead. labels Jun 17, 2025
Copy link
Contributor

github-actions bot commented Jun 17, 2025

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 dotcom-13618-untangling-ia-dashboard-home branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack dotcom-13618-untangling-ia-dashboard-home
bin/jetpack-downloader test jetpack-mu-wpcom-plugin dotcom-13618-untangling-ia-dashboard-home

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 github-actions bot added [Feature] Masterbar WordPress.com Toolbar and Dashboard customizations [mu wpcom Feature] Wpcom Admin Menu [Package] Jetpack mu wpcom WordPress.com Features [Package] Masterbar labels Jun 17, 2025
Copy link
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 a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  • ✅ 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!

Copy link

jp-launch-control bot commented Jun 17, 2025

Code Coverage Summary

Coverage changed in 5 files.

File Coverage Δ% Δ Uncovered
projects/packages/masterbar/src/admin-menu/class-base-admin-menu.php 168/244 (68.85%) -1.64% 4 💔
projects/packages/masterbar/src/admin-menu/class-atomic-admin-menu.php 75/161 (46.58%) 0.29% -1 💚
projects/packages/jetpack-mu-wpcom/src/features/wpcom-admin-menu/wpcom-admin-menu.php 0/297 (0.00%) 0.00% -2 💚
projects/packages/masterbar/src/admin-menu/class-admin-menu.php 179/228 (78.51%) 0.49% -2 💚
projects/packages/masterbar/src/admin-menu/class-wpcom-admin-menu.php 43/154 (27.92%) 0.36% -2 💚

Full summary · PHP report · JS report

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

@mmtr mmtr added the I don't care about code coverage for this PR Use this label to ignore the check for insufficient code coveage. label Jun 17, 2025
@mmtr mmtr requested a review from a team June 17, 2025 15:03
xavier-lc
xavier-lc previously approved these changes Jun 18, 2025
Copy link
Contributor

@xavier-lc xavier-lc left a comment

Choose a reason for hiding this comment

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

Works as described

@BogdanUngureanu
Copy link
Contributor

BogdanUngureanu commented Jun 18, 2025

Screenshot 2025-06-18 at 12 37 04

Tests well on Simple and Atomic, however, there's a small priority issue on p2s.

By moving the My home out of hosting for classic interface, it means the overview would become the default page. Not a problem, but it would be interesting to see what's the impact of this (more domains, more staging sites usage, etc) since in theory it would receive more exposure.

@mmtr
Copy link
Member Author

mmtr commented Jun 18, 2025

there's a small priority issue on p2s.

Actually, it's not only P2s, but all sites. Great catch. And like you said, not a problem, but would be nice if as a side effect of this change users are more aware of the Hosting Dashboard.

@BogdanUngureanu
Copy link
Contributor

BogdanUngureanu commented Jun 18, 2025

there's a small priority issue on p2s.

Actually, it's not only P2s, but all sites. Great catch. And like you said, not a problem, but would be nice if as a side effect of this change users are more aware of the Hosting Dashboard.

Sorry, I should've been more clear. That comment is about two separate things :D

  • The priority problem on p2s (My home is not besides the Dashboard) (small bug)
  • The default page of Hosting is now different on all sites (not a bug)

@mmtr
Copy link
Member Author

mmtr commented Jun 18, 2025

The priority problem on p2s (My home is not besides the Dashboard) (small bug)

Got it, thanks for clarifying! Just pushed a fix for that, along with another fix to prevent the "My Home" menu from being visible to super admins who are not members of the site (and thus without Calypso access for that site).

Copy link
Contributor

@BogdanUngureanu BogdanUngureanu left a comment

Choose a reason for hiding this comment

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

LGTM! 🚢

@mmtr mmtr merged commit bed5306 into trunk Jun 19, 2025
67 checks passed
@mmtr mmtr deleted the dotcom-13618-untangling-ia-dashboard-home branch June 19, 2025 13:17
@github-actions github-actions bot removed the [Status] Needs Team Review Obsolete. Use Needs Review instead. label Jun 19, 2025
mikestottuk pushed a commit that referenced this pull request Jun 26, 2025
- Stops replacing the "Dashboard" menu with "My Home". This way, the "Dashboard" menu is consistently visible across all sites (previously, only visible with the classic admin interface).
- Always registers "My Home" as a top-level menu, so it's consistently in the same level across all sites (previously, it was a submenu of "Hosting" on sites with the classic admin interface).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Masterbar WordPress.com Toolbar and Dashboard customizations I don't care about code coverage for this PR Use this label to ignore the check for insufficient code coveage. [mu wpcom Feature] Wpcom Admin Menu [Package] Jetpack mu wpcom WordPress.com Features [Package] Masterbar [Tests] Includes Tests [Type] Enhancement Changes to an existing feature — removing, adding, or changing parts of it
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants