Update Woo Blaze Jetpack connection copy

[Alameen688]

Proposed Changes

• This PR updates the connect auth and sign-up page copy for Woo Blaze

Testing Instructions

• Create a WooCommerce site, and make sure the Jetpack plugin is deactivated or not installed
• Point widgets.wp.com to your WP Sandbox.
• Run yarn start to start calypso
• Create a plugin build from the woo-blaze plugin repo and install it in your test blog OR run locally as described in repo readme.
• cd apps/blaze-dashboard and yarn dev --sync to sync blaze dashboard to WP sandbox OR run the commands here Update Woo Blaze Jetpack connection copy #90070 (comment)
• In WP Admin, Go to Marketing -> Blaze for WooCommerce
• Click Connect now button and you should see the Jetpack connect flow.

For existing connected users you should see the following connect screen:

For a new user/user without a previous connection attempt you should see the following connect screens:

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• https://wpcalypso.wordpress.com/devdocs/docs/testing/index.md 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-108010

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-108010&env=a8c-for-agencies

[matticbot]

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

Sections (~76 bytes added 📈 [gzipped])

name             parsed_size           gzip_size
jetpack-connect       +449 B  (+0.0%)      +76 B  (+0.0%)

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.

[sbarbosa]

Hi @Alameen688!
We have a PR almost ready with the changes of the new connection page #90160.

Checking this PR; I think we will need to revert some changes to adapt them to that other PR. I think that the only changes we need to maintain are:

• Changes to the jetpack-client code
• Redirection using the connect_url config prop

From our last sync, I think the changes to the connection-info URL are not necessary, because the redirection will be to the backend, and not the frontend.

We can wait until we merged that other PR, and then revert back the changes that are outdated. Let me know what you think.

[Alameen688]

I think we will need to revert some changes to adapt them to that other PR

Yes, I agree. Those changes were just a placeholder for testing pending the implementation of the connect UI. And yes, we don't need the connection-info URL it was under the assumption that the new connect UI on the dashboard might be a separate page but I can see in the other PR #90160 that it is a component conditionally rendered under the setup page/URL.

Also, a long explanation for the connection-info page - as I mentioned in our sync is that it doesn't do anything in this PR it's just an empty placeholder page for when the page reloads to trigger the serverside logic that redirects to the jetpack connection page. the connect URL can be the setup URL or home URL (i.e. just the wc-blaze path), just needed a URL to trigger the onboarding logic which is handled server side, it could have been a window.reload on the client but we just have it as a connect_url to give control/flexibility to the server of what happens when the connect button is clicked in case of a change in the redirect flow, so client-side code changes won't be needed

[sbarbosa]

Thanks for the changes @Alameen688.
The code looks great!

[therocket-gr]

tested and works as described
code changes LGTM

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug add/woo-blaze-jetpack-connection on your sandbox.