WordPress.com: Add the Help Center App ✨

[alshakero]

Proposed changes:

This enqueues one of four bundles from widgets.wp.com. It chooses the bundle based on the context:

• help-center-gutenberg.min.js: for GB editor in a connected site.
• help-center-wp-admin: for wp-admin in a connected site.
• help-center-wp-admin-disconnected.js: for wp-admin in a disconnected site.
• help-center-gutenberg-disconnected: for GB editor in a disconnected site.

It also adds 12 new end points that proxy Atomic requests to wpcom. These endpoints are copied from ETK almost verbatim and have been battle tested for months/years.

Other information:

• [x] Have you written new tests for your changes, if applicable? No, but I will move tests from ETK in a follow up.
• [x] Have you checked the E2E test CI results, and verified that your changes do not break them?
• [x] 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

There have been many discussions around moving the Help Center to Jetpack. But the most recent one is: p1718801409878749-slack-C0347E545HR

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

No.

Testing instructions:

Simple sites

1. cd into projects/packages/jetpack-mu-wpcom.
2. Sync using pnpm run build-production-js && jetpack rsync mu-wpcom-plugin wpcom-sandbox:~/public_html/wp-content/mu-plugins/jetpack-mu-wpcom-plugin/sun
3. Go to the editor on a sandboxed site and smoke test the Help Center.
4. Go to /wp-admin on a sandboxed site and smoke test the Help Center.
5. Verify that it's loaded from Jetpack by checking the path of the help-center bundle in the Network tab of the DevTools.

Connected Atomic site

1. cd into projects/packages/jetpack-mu-wpcom.
2. Sync jetpack-mu-wpcom with your WoA site using this command jetpack rsync mu-wpcom-plugin wpcom-atomic:htdocs/wp-content/plugins/jetpack-mu-wpcom-plugin-dev. Assuming you have an ssh host pointing to a WoA site.
3. Important: Edit ~/htdocs/wp-config.php and add define( 'JETPACK_AUTOLOAD_DEV', true );.
4. Important: Edit ~/htdocs/wp-config.php and add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true );
5. Go to the editor and smoke test the Help Center.
6. Go to /wp-admin and smoke test the Help Center.
7. Verify that it's loaded from Jetpack by checking the path of the help-center bundle in the Network tab of the DevTools.

Disconnected Atomic site

1. Disconnect a JP site by going to /_cli and running jetpack disconnect blog.
2. Go to /wp-admin/post-new.php.
3. Click the Help Center.
4. It should take you to wp.com/help.
5. Repeat in wp-admin.
6. It should take you to wp.com/help.
7. Reconnect your site by going to https://jptools.wordpress.com/debug/?url=YOUR_SITE and click "Restore User Connection".

[github-actions[bot]]

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 WordPress.com Simple 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, and enable the move/help-center branch.
  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin move/help-center

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[bot]]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• :white_check_mark: Include a description of your PR changes.
  
• :red_circle: Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• :white_check_mark: Add testing instructions.
  
• :white_check_mark: Specify whether this PR includes any changes to data or privacy.
  
• :white_check_mark: 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 :robot:

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped. Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged. If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

---

Mu Wpcom plugin:

• Next scheduled release: August 6, 2024.
• Scheduled code freeze: July 29, 2024.

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

---

Wpcomsh plugin:

• Next scheduled release: August 6, 2024.
• Scheduled code freeze: July 29, 2024.

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

[heavyweight]

The static analysis is failing. But the cause of this is from another PR

[agrullon95]

Testing in progress:

Simple site:

• [ ] Go to the editor on a sandboxed site and smoke test the Help Center. Im not able to see the Help Center Icon in the Editor (Calypso)
• [x] Go to /wp-admin on a sandboxed site and smoke test the Help Center.
• [x] Verify that it's loaded from Jetpack by checking the path of the help-center bundle in the Network tab of the DevTools.

Atomic site:

• [x] Go to the editor and smoke test the Help Center.
• [x] Go to /wp-admin and smoke test the Help Center.
• [x] Verify that it's loaded from Jetpack by checking the path of the help-center bundle in the Network tab of the DevTools.

Disconnected Atomic site:

• [x] Go to /wp-admin/post-new.php, click the Help Center, it should take you to wp.com/help
• [x] Go to /wp-admin, click the Help Center, it should take you to wp.com/help