-
Notifications
You must be signed in to change notification settings - Fork 799
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sharing Block: update messaging in Jetpack Dashboard > Settings > Sharing to mention new block #34325
Comments
Agreed! I think the UI should be dynamic here, showing only the relevant information depending on the type of theme is active at a given time. Legacy themeBlock themeChanges:
The settings UI starts to fall apart a little bit with all the dividers, but let's worry about that later. |
This sounds good to me for a start. Later on, maybe we could explore automatically adding the buttons to single posts templates with a toggle there (or in wp-admin sharing settings, or in both places?). We're having a conversation about that here: |
Support References This comment is automatically generated. Please do not edit it.
|
Fixes #34325 See the designs in #34325 (comment) for more explanation.
…aring block (#34619) * Dashboard: Get sharing block availability for use in dashboard This will allow us to conditionally display different links whether the upcoming sharing block is available or not. Down the road, we can remove those settings when the sharing block will be available for everyone. * Make theme and sharing block info available to Sharing component * Update the interface to account for the sharing block Fixes #34325 See the designs in #34325 (comment) for more explanation. * Add changelog * Link to a different support doc when you use the sharing block * Always display the legacy module toggle, but suggest the block See discussion in #34619 (comment) * update wording
…aring block (#34619) * Dashboard: Get sharing block availability for use in dashboard This will allow us to conditionally display different links whether the upcoming sharing block is available or not. Down the road, we can remove those settings when the sharing block will be available for everyone. * Make theme and sharing block info available to Sharing component * Update the interface to account for the sharing block Fixes #34325 See the designs in Automattic/jetpack#34325 (comment) for more explanation. * Add changelog * Link to a different support doc when you use the sharing block * Always display the legacy module toggle, but suggest the block See discussion in Automattic/jetpack#34619 (comment) * update wording Committed via a GitHub action: https://github.com/Automattic/jetpack/actions/runs/7302442324
…aring block (#34619) * Dashboard: Get sharing block availability for use in dashboard This will allow us to conditionally display different links whether the upcoming sharing block is available or not. Down the road, we can remove those settings when the sharing block will be available for everyone. * Make theme and sharing block info available to Sharing component * Update the interface to account for the sharing block Fixes #34325 See the designs in Automattic/jetpack#34325 (comment) for more explanation. * Add changelog * Link to a different support doc when you use the sharing block * Always display the legacy module toggle, but suggest the block See discussion in Automattic/jetpack#34619 (comment) * update wording Committed via a GitHub action: https://github.com/Automattic/jetpack/actions/runs/7302442324
I think the toggle was still helpful; site editor and fiddling with templates feels a bit more advanced. Can we inject the block into post templates with the toggle turned on, instead of removing this as "legacy"? Block Hooks API I think is the way to go. |
When a site owner uses a block-based theme, they should not be offered an option to turn on the sharing module. Instead, we should suggest they go to the site editor and add the new sharing block to their site templates.
Epic: #19694
The text was updated successfully, but these errors were encountered: