Add DIFM-specific functionality for WoA sites

[aneeshd16]

Fixes https://github.com/Automattic/martech/issues/3505

Proposed changes:

Fixes https://github.com/Automattic/martech/issues/3505

This PR contains the following changes:
When the difm-lite-in-progress sticker is active for a WoA site, and the user is NOT proxied:

• Always show the Coming Soon page.

• Hide the admin bar.

• Hide all menu items in wp-admin except for Hosting->{Email, Domain, Purchases}.

• Replace wp-admin page content with this notice:

  • If content has not been submitted:
  
  • If content has been submitted:
  

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• 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

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

Testing instructions:

Setup

• Ensure you have a WoA site on a Business plan.
• Go to https://wordpress.com/start/do-it-for-me and choose "Existing site". Choose the WoA site from the first step.
• Ensure that you are not store sandboxed and complete the purchase.
• SSH into the WoA site.
• Add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file. (Usually in /htdocs/wp-config.php)
• Go to the Blog RC and toggle off the difm-lite-in-progress sticker.
• Install the Jetpack Beta Tester Plugin.
• Go to /wp-admin/admin.php?page=jetpack-beta&plugin=jetpack-mu-wpcom-plugin.
• In the "Search for a feature branch box", enter add/wpcom-difm-functions. (This branch)
• Go to the Blog RC and toggle on the difm-lite-in-progress sticker.

Testing

Proxy Off

• Visit the website URL. Confirm that the Coming Soon page is shown.

• Confirm that the admin bar is not shown. The following is a screenshot of the admin bar.
  

• Go to /wp-admin

• Confirm that only the Hosting menu is present in the side bar and contains the following items:
  

• Confirm that the sub menu items point to the correct URLs.

• Confirm that the content area is replaced by this:
  

• Click on the button in the above notice.

• Confirm it takes you to the content submission form and submit content.

• Go to /wp-admin.

• Confirm that the content area is replaced by by this:
  

Proxy On

• Visit the website URL. Confirm that the Coming Soon page is not shown and the full website is visible.
• Confirm that the admin bar is shown.
• Go to /wp-admin
• Confirm that the all menu items are present in the sidebar.
• Confirm that the regular wp-admin content is shown.

[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 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 add/wpcom-difm-functions 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 add/wpcom-difm-functions
  

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/wpcom-difm-functions
  

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 Team 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 🤖

---

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.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen semi-continuously (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly. The next release is scheduled for none scheduled (scheduled code freeze on undefined).

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

[oskosk]

Hi, can you add any context for this PR? Thanks

[aneeshd16]

Hi @oskosk, this is a very early draft, and depending on feedback, we may or may not proceed with it. As the PR progresses, I'll keep adding details and testing instructions. For now, I have added the GH issue link to the PR. Hope that it's okay!