Site Editor: Change the < link to the theme showcase

[okmttdhr]

Proposed changes:

• Change the Site Editor's < link to the theme showcase page. See Live Preview: the "Back" button points to the Theme Showcase page with the Classic View wp-calypso#80595.
• This PR works with Theme Previews: Make the back button customizable WordPress/gutenberg#54242 while this does not break anything without Theme Previews: Make the back button customizable WordPress/gutenberg#54242.

• I'll create a follow-up PR to move this into jetpack-mu-wpcom Site Editor: Change the < link to the theme showcase  #32913 (comment)
  • -> Site Editor: Move the feature of changing backlink into mu-wpcom #33024

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?

No

Testing instructions:

• Apply Theme Previews: Make the back button customizable WordPress/gutenberg#54242 to your site (because this PR works with Theme Previews: Make the back button customizable WordPress/gutenberg#54242 while this does not break anything without it)
  • On Simple sites
    • Sync the change to your sandbox with AWE or rsync PCYsg-t5D-p2
  • On Atomic sites
    • Uninstall gutenberg
    • Checkout to Theme Previews: Make the back button customizable WordPress/gutenberg#54242
    • npm run dev
    • Create a new directory with including only build/***, gutenberg.php, lib/***, packages/***, post-content.php, vendor/***, and zip it
    • Upload the zip to ~/htdocs/wp-content/plugins on your site
    • Run unzip gutenberg.zip on your site and activate it
• Apply this patch to your site by doing Site Editor: Change the < link to the theme showcase  #32913 (comment)
  • Note that you must set define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php on Atomic sites.
• Go to the Theme Showcase
• Click the Live Preview option on the three-dots menu on the Theme Card
• Confirm if the < link point to the Theme Showcase page

Related

• Site Editor: dashboard link compat for Gutenberg 14.5 #27601
• Override the backlink on the Live Preview wp-calypso#81387

[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 > Jetpack and enable the add/themePreviewBackLink branch.

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

  bin/jetpack-downloader test jetpack add/themePreviewBackLink
  

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.
  
• ✅ All commits were linted before commit.
  
• ✅ 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.

---

Once your PR is ready for review, check one last time that all required checks (other than "Required review") 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.

---

Jetpack plugin:

• Next scheduled release: October 3, 2023.
• Scheduled code freeze: September 25, 2023.

[arthur791004]

LGTM 🎉

[okmttdhr]

Hello, @arthur791004 @jeherve. I made a change 9993abf to align with the Gutenberg implementation. Could you take a look and ✅ again? Thanks! 🙏