Sharing: open up sharing block recommendations

[jeherve]

Follow-up to #85180

Related:

• Sharing: add notice in Calypso Sharing settings to explain that this doesn't impact the sharing block jetpack#34327
• Sharing block: ensure compatibility with global settings set in module jetpack#34117

Proposed Changes

Now that the sharing buttons block is widely available, both on WordPress.com Simple and on stable Jetpack releases, we can remove the previous flag and display the new screen to everyone, as long as they're on WordPress.com or using a recent version of Jetpack (the sharing buttons block was added to the plugin in version 13.1).

This PR also does a few other things:

• It updates the look of the sharing buttons block recommendation screen to link to the support docs, with an external link button, and with the right doc depending on your platform.
• It updates the wording on the sharing screen to try to make it clearer that the blocks is what you want to go with when using a block-based theme.
• It offers a quick option to deactivate the sharing module when you use a block-based theme.

Testing Instructions

Note

It's important to test this change on both WordPress.com and Jetpack sites, on sites that use a classic theme and sites that use a block-based theme.

• On a self-hosted site, go to Jetpack > Settings > Sharing and activate the sharing module.
• Go to http://calypso.localhost:3000/marketing/sharing-buttons/
  • Ensure the display is relevant to the state of your site, following the screenshots below.`

Jetpack, block-based theme, legacy sharing module active

Jetpack, block-based theme, legacy sharing module inactive

Jetpack, classic theme, legacy sharing module active

-> No changes to that scenario

Jetpack, classic theme, legacy sharing module inactive

-> No changes to that scenario

WordPress.com, block-based theme

WordPress.com, classic theme

-> No changes to that scenario

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-100151

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-100151&env=jetpack

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~174 bytes added 📈 [gzipped])

name       parsed_size           gzip_size
marketing       +447 B  (+0.1%)     +174 B  (+0.1%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[andrii-lysenko]

This looks reasonable and intuitive for me 👍

[a8ci18n]

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/11592784

Some locales (Hebrew, Japanese) have been temporarily machine-translated due to translator availability. All other translations are usually ready within a few days. Untranslated and machine-translated strings will be sent for translation next Monday and are expected to be completed by the following Friday.

Thank you @jeherve for including a screenshot in the description! This is really helpful for our translators.

[a8ci18n]

Translation for this Pull Request has now been finished.