-
Notifications
You must be signed in to change notification settings - Fork 798
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
Social: Add recommendation steps for the V1 plan #38219
Conversation
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
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 appearing at the bottom of this PR are passing or skipped. Jetpack plugin: The Jetpack plugin has different release cadences depending on the platform:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works fine
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a good first step. The suggestion from Marketing was to have a recommendation for all sites, promoting the free version. Perhaps we could repurpose the Basic recommendation for that? It would be fine to do that as a separate change of course.
@@ -41,12 +41,12 @@ export const RECOMMENDATION_WIZARD_STEP = { | |||
WELCOME__SEARCH: 'welcome__search', | |||
WELCOME__SCAN: 'welcome__scan', | |||
WELCOME__SOCIAL_BASIC: 'welcome__social_basic', | |||
WELCOME__SOCIAL_ADVANCED: 'welcome__social_advanced', | |||
WELCOME__SOCIAL_V1: 'welcome__social_v1', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to keep the Advanced flow for now in case people are activating the legacy plans? If not, then do we need to keep the Basic recommendations?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is that still sellable? Even if it is, I'm not sure we should support that with the onboarding as it's deprecated anyway.
cc @spsiddarthan
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can get rid of the old plans here
We can let those be for now, Jetpack Manage hasn't deprecated the old plans yet.
return { | ||
question: __( 'Welcome to Jetpack Social!', 'jetpack' ), | ||
description: __( | ||
"With your new advanced plan you unlocked unlimited sharing, access to upload photos and videos with your posts, and usage of Social Image Generator.<br/><br/>Let's start with connecting your social media accounts, if you haven't already.", | ||
"With your new Social plan you unlocked priority support, access to upload photos and videos with your posts, and usage of Social Image Generator.<br/><br/>Let's start with connecting your social media accounts, if you haven't already.", | ||
'jetpack' | ||
), | ||
ctaText: __( 'Manage Social Media Connections', 'jetpack' ), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should update this link too. I suppose we could bring up the connections modal on this page, but it might be better to send them to the Sharing settings instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 67bb287
Because of p1720428043465199-slack-C02JJ910CNL, I made it so on the welcome pages we open the sharing section in a new tab, to not mess up the onboarding flow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After my investigation that's an issue on trunk and with Calypso. p1720514740440389-slack-C02JJ910CNL Fixed in https://github.com/Automattic/jetpack-reach/issues/446 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works well!
Fixes https://github.com/Automattic/jetpack-reach/issues/439
Proposed changes:
Other information:
Jetpack product discussion
https://github.com/Automattic/jetpack-reach/issues/439
Does this pull request change what data or activity we track or use?
Testing instructions:
jetpack docker wp option delete jetpack_options
. You'll have to reconnect Jetpack after this.CleanShot.2024-07-05.at.14.03.53.png.mp4