Premium Analytics: match the Insights board default widgets to the prototype layout

[chihsuan]

Part of WOOA7S-1786

Proposed changes

Update the default Insights board to match the prototype's row order and sizing:

• Highlights and Posting activity are each full width.
• Latest post is paired with the newly added Popular post.
• Total views and Total visitors replace the temporary All-time stats widget and share a row with Most popular time and Most popular day.
• The four leaderboard widgets fill the final row.

Highlights now uses its built-in default metrics from #51052. The layout test also verifies the complete widget order and placement instead of two selected widgets.

Existing customized boards are unchanged; the new defaults apply only to untouched boards and resets.

Known gaps, tracked elsewhere

• WOOA7S-1846 — Most popular time and Most popular day can still crop at single-row height.
• WOOA7S-1855 — The Traffic views activity is omitted because its widget does not exist yet.

Related product discussion/links

• WOOA7S-1786

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

No.

Testing instructions

• Check out this branch and build packages/premium-analytics, or use a site already running it.
• As a user who has never customized the Insights tab, open Stats v2 -> Insights.
• The rows should be: Highlights full width, Posting activity full width, Latest post + Popular post, Total views / Total visitors / Most popular time / Most popular day, then Most commented posts / Most commented authors / Top social media shares / Top tags & categories. Every row fills the four-column grid.
• Highlights should show Posts, Words, Likes, and Comments without any saved attributes.
• All-time stats should no longer be on the board by default, but should still be available from the widget picker.
• If you have customized the tab before, use the tab's Reset action first — a stored layout takes precedence over the default.

Or

Compare layout with https://sweetly-steep.jurassic.ninja/wp-admin/admin.php?page=analytics-dashboard#insights

[github-actions]

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 wooa7s-1786-default-insights-widgets branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack wooa7s-1786-default-insights-widgets

bin/jetpack-downloader test jetpack-mu-wpcom-plugin wooa7s-1786-default-insights-widgets

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]

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!

[jp-launch-control]

Code Coverage Summary

No summary data is available for parent commit c219085, so cannot calculate coverage changes. 😴

If that commit is a feature branch rather than a trunk commit, this is expected. Otherwise, this should be updated once coverage for c219085 is available.

Full summary · PHP report · JS report