Settings: open Jetpack Settings support links in Help Center on WordPress.com

[escapemanuele]

Part of DOTCOM-17147

Proposed changes

• Centralize Dotcom-aware behavior in components/support-info:
  • New optional wpcomLink / wpcomPostId props. When isWpcomPlatformSite() is true and wpcomLink is provided, the "Learn more" link renders as WpcomSupportLink so it opens inside the Help Center (or falls back to a new-tab anchor when the Help Center store is not present).
  • On WordPress.com (Simple/Atomic), hide the "Privacy information" link — it is not relevant to Dotcom users.
  • Standalone Jetpack continues to use the existing jetpack.com/redirect link, unchanged.
• Add wpcomLink to every settings card called out in the issue: Security (monitor, protect, sso), Performance (media, speed-up-site), Writing (composing, custom-content-types, theme-enhancements, widgets, post-by-email), Sharing (publicize, share-buttons, likes), Discussion (comments), Traffic (related-posts, seo, site-stats, shortlinks, sitemaps, verification-services), Monetize (ads, payments / donations / pay-with-paypal).
• earn/index.jsx: thread a new wpcomSupportLink prop through EarnFeatureButton into the shared support object so each earn feature card can specify its own Dotcom doc.

Related product discussion/links

• DOTCOM-17147

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

No. The existing recordJetpackClick tracking on the "Learn more" link is preserved (the onClick is passed through to WpcomSupportLink).

Testing instructions

WordPress.com (Atomic, Business / Commerce plan)

1. Sandbox the Jetpack plugin on an Atomic site (or run the Jetpack plugin from a branch build).
2. Go to Jetpack → Settings and click through the Security, Performance, Writing, Sharing, Discussion, Traffic, and Monetize tabs.
3. On each settings card, click the (i) info icon and then Learn more.
4. Expected:
   • The link opens inside the Help Center (the Help Center panel slides in showing the matching wordpress.com/support article), not a new browser tab.
   • The "Privacy information" link is not rendered in the popover.

Standalone Jetpack site (Jurassic Ninja / self-hosted)

1. Connect Jetpack on a non-WordPress.com site.
2. Go to Jetpack → Settings and open any settings card's info popover.
3. Expected:
   • Learn more opens jetpack.com/redirect in a new tab (unchanged behavior).
   • The Privacy information link is still rendered (unchanged behavior).

🤖 Generated with Claude Code

[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 fix/dotcom-17147-jetpack-settings-wpcom-support-links branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack fix/dotcom-17147-jetpack-settings-wpcom-support-links

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

Cannot generate coverage summary while tests are failing. 🤐

Please fix the tests, or re-run the Code coverage job if it was something being flaky.

Full summary · PHP report · JS report