Podcast: Polish dashboard spacing and CTAs

[DevinWalker]

Fixes JETPACK-1788

https://www.loom.com/share/64185a7935124e1fb1bfdfc23ac45283

Proposed changes

• Add 32px outer spacing around Podcast setup/settings-style content wrappers.
• Preserve the narrow settings/distribution content width while adding outer insets.
• Align the welcome hero, pricing cards, benefit cards, and setup card to the same horizontal inset.
• Keep the Free and Growth pricing CTAs at their natural text width instead of stretching across the cards.
• Add a Podcast package changelog entry.

Related product discussion/links

• JETPACK-1788: https://linear.app/a8c/issue/JETPACK-1788/podcast-polish-dashboard-spacing-and-ctas

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

No.

Testing instructions

• Run jp build packages/podcast.
• Run jp test js packages/podcast and confirm it skips because the package has no test-js script.
• Run jp test php packages/podcast.
• Run jp phan packages/podcast.
• Open the Podcast welcome/enable screen in a local Jetpack dev site and confirm the hero, pricing cards, and lower benefit cards share the same left/right inset with 32px top spacing.
• Open the Distribution and Settings tabs and confirm their tab content has 32px top/bottom and left/right spacing while preserving the narrow content width.
• Open the Stats and Episodes tabs and confirm their tab content wrapper has no added padding.
• Confirm the Free and Growth pricing CTAs fit their text instead of stretching full-width across each card.

[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 codex/jetpack-podcast-ui-touchups branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack codex/jetpack-podcast-ui-touchups

bin/jetpack-downloader test jetpack-mu-wpcom-plugin codex/jetpack-podcast-ui-touchups

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

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