Newsletter: label subscription placement options with a section header

[CGastrell]

Fixes #

Proposed changes

From the p8oabR-1P8-p2 feedback on the modernized Newsletter dashboard: the subscription form placement options (overlay / pop-up / Subscribe block) had no heading. This adds a "Homepage and posts" section header above the options grid, matching the existing labeled section below it (the label mirrors the component's own internal "Homepage and posts" naming). Labeling only — no behavior change.

Related product discussion/links

• Call for Testing: Modernized Jetpack Dashboards (Newsletter, VideoPress & Social) p8oabR-1P8-p2

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

No.

Testing instructions

• On a site with the modernized Newsletter dashboard, go to Jetpack → Newsletter → Settings and scroll to the subscription form placement options (overlay / pop-up / Subscribe block).
• Confirm a "Homepage and posts" section header now appears above the options grid, consistent with the labeled section beneath it.
• Confirm nothing else in the Settings tab changed — this PR is labeling only.

[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), and enable the change/newsletter-add-subscriber-copy-cft branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack change/newsletter-add-subscriber-copy-cft

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!

---

Jetpack plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[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