Search: improve upgrade/feature messaging#10137
Conversation
This is automated check which relies on Generated by 🚫 dangerJS |
|
@gibrown LGTM, but I just pushed some changes to the labels and descriptive text so we refer to it as Jetpack Search more explicitly. Here are screenshots of my changes:
^ you'll notice that I missed the header label text ( |
|
Do we want do update the messaging in the prompt in the Plans page while we are at it?
We could also look at the widget's description:
|
jeherve
left a comment
There was a problem hiding this comment.
This seems to work. I just have a small comment about one of the links.
Also, not something we can fix in Jetpack but I'll mention it since it is somewhat related: the 2 "get started" buttons on the upgrade page we link to (https://jetpack.com/features/design/elasticsearch-powered-search/) from the upgrade prompts in the traffic settings once your site is connected don't actually do anything. They just link to the #get-started anchor on the page.
I ended up scrolling down to the bottom of the page to click on the "Get Search in Jetpack Professional" button, but that wasn't a successful flow either. It led me to a connect page, although my site is already connected. Since the previous Jetpack.com landing page had my site URL as a query string in the URL, I at least would expect my site to be pre-filled here. Here is the URL:
As it is, it is quite difficult to upgrade.
For reference, I was using a Jurassic Ninja site that was running this branch, and that I had just connected to WordPress.com a few minutes earlier. I also had purchased a Premium plan for it.
| support={ { | ||
| text: __( 'Replaces the default WordPress search with a faster, filterable search experience.' ), | ||
| text: __( 'Jetpack Search supports many customizations.' ), | ||
| link: 'https://jetpack.com/support/search', |
There was a problem hiding this comment.
Should we link to the customization support page here? https://jetpack.com/support/search/customize-search/
|
@jeherve agree that both the Plans page and widget description should both be updated. Thanks for catching those! You bring up a great point about the upgrade experience from that jetpack.com page—ideally we'd be able to detect that you were logged in to WPcom and then take you to the Calypso checkout page for the upgrade from Prem to Pro at |
|
@joanrho That certainly sounds possible, but I'm not familiar with the Jetpack site and how much work might be involved. I took a quick look at the site and it doesn't appear to be a trivial change. @jeffgolenski is probably better equipped to answer that bit. |
|
@jeherve good call on the plans page. Fixed. I'm merging this in. |
* Readme: add boilerplate for next release, 6.6 * Add 6.5 to the changelog.txt file * Set boilerplate testing list for 6.6 * Readme: update stable tag to 6.5 * Add bullets to 6.5 changelog items * Readme: add link to previous changelogs This will help folks who want to know more about past releases, while keeping the readme.txt short so as to not overwhelm translators and site owners only looking for information about the last release. * Changelog: add information at the top of the changelog file. * Changelog: add #10054 * Changelog: add #10078 * Changelog: add #10079 * Changelog: add #10064 * Changelog: add #10094 * Changelog: add #10096 * Testing list: add more information based on #10087 * Changelog: add #9847 * Changelog: add #10084 * Changelog: add #9918 * Changelog: add #7614 * Changelog: add #10116 * Changelog: add #10108 * Changelog: add #10041 * Changelog: add #10121 * Changelog: add #10134 * Changelog: add #10130 * Changelog: add #10109 * changelog: add #10137 * changelog: add #9952 * changelog: add #10120 * changelog: add #10162 * Changelog: add #10163 * Changelog: add #10092 * changelog: add #10156 * Changelog: add #10154 * changelog: add #10122 * Changelog: add #10101 * changelog: add #10105 * changelog: add #10190 * Changelog: add #10196 * changelog: add #10152 * Changelog: add #10153 * Testing list: add more details to Site Verification testing steps. @see #10143 (comment) * changelog: add #10194 * Changelog: add #10193
Fixes #9747
Makes changes to the upgrade messages. The exact language was iterated on a bit in Automattic/wp-calypso#27059 and this PR has them matching. Similar to that PR I also moved the site search settings further down on the page.
The changes affect the UI in the Jetpack dashboard:
Screenshots of the new upgrade wording: