Conditionally update UI on DIFM vs. DIY step of migration flow

[donnapep]

Related to https://github.com/Automattic/dotcom-forge/issues/10025.

Proposed Changes

Updates the UI on the DIFM vs. DIY step of the migration flow. These changes are currently behind a feature flag and will be launched as part of a future experiment.

Testing Instructions

• Browse to the DIFM vs. DIY step of the migration flow for a free site.
• Ensure the UI is the same as it was before:

• Enable the migration-flow/experiment feature flag in config/development.json.
• Ensure the UI matches the new design (ay0fZYgdXxPDbZbgPlz3hu-fi-1_3506). Note that I didn't use the same content width as in the design, instead opting to keep the width the same as it was before as it's closer to what other pages in the migration flow use. This is most noticeable in the subheading text:

• Click the Get started button and ensure you are eventually taken to the credentials page.
• Click the I'll do it myself link and ensure you are eventually taken to the migration instructions page.
• Browse to the DIFM vs. DIY step of the migration flow for a site on the Business plan (or replace siteId and siteSlug query params with appropriate values for a Business plan site).
• Ensure the subheading text is updated:

• Check the layout on mobile and ensure it looks good.

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 UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• 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-127259

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

App Entrypoints (~82 bytes added 📈 [gzipped])

name                   parsed_size           gzip_size
entry-subscriptions         +351 B  (+0.0%)      +82 B  (+0.0%)
entry-stepper               +351 B  (+0.0%)      +82 B  (+0.0%)
entry-main                  +351 B  (+0.0%)      +82 B  (+0.0%)
entry-login                 +351 B  (+0.0%)      +82 B  (+0.0%)
entry-domains-landing       +351 B  (+0.1%)      +82 B  (+0.0%)
entry-browsehappy           +351 B  (+0.2%)      +82 B  (+0.1%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Sections (~42 bytes removed 📉 [gzipped])

name                        parsed_size           gzip_size
with-theme-assembler-flow        -114 B  (-0.2%)       -3 B  (-0.0%)
update-options-flow              -114 B  (-0.2%)       -3 B  (-0.0%)
update-design-flow               -114 B  (-0.0%)       -2 B  (-0.0%)
trial-wooexpress-flow            -114 B  (-0.2%)       -5 B  (-0.1%)
tailored-ecommerce-flow          -114 B  (-0.2%)       -3 B  (-0.0%)
site-setup-wg                    -114 B  (-0.1%)       -2 B  (-0.0%)
site-setup-flow                  -114 B  (-0.1%)       -2 B  (-0.0%)
site-migration-flow              -114 B  (-0.1%)       -3 B  (-0.0%)
readymade-template-flow          -114 B  (-0.1%)       -3 B  (-0.0%)
migration-signup                 -114 B  (-0.2%)       -3 B  (-0.0%)
migration-flow                   -114 B  (-0.1%)       -3 B  (-0.0%)
import-flow                      -114 B  (-0.2%)       -2 B  (-0.0%)
hosted-site-migration-flow       -114 B  (-0.1%)       -3 B  (-0.0%)
free-post-setup-flow             -114 B  (-0.2%)       -2 B  (-0.0%)
entrepreneur-flow                -114 B  (-0.1%)       -3 B  (-0.0%)
assembler-first-flow             -114 B  (-0.1%)       -4 B  (-0.0%)
ai-assembler-flow                -114 B  (-0.1%)       -4 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.

[matticbot]

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

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

• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/difm-vs-diy-step on your sandbox.

[a8ci18n]

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

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 @donnapep for including a screenshot in the description! This is really helpful for our translators.

[m1r0]

Looks good and thanks for the tests! 🥂

[donnapep]

@fditrapani for a sneaky peeky of the new experimental UI for the DIY vs. DIFM page.

[fditrapani]

Thanks for the ping! Looks great from the screenshots ❤️

Note that I didn't use the same content width as in the design, instead opting to keep the width the same as it was before as it's closer to what other pages in the migration flow use.

No problem. I'm glad you did this, it's better to work within the system rather than creating one off inconsistencies. We can always adjust the copy later if it feels too long.

[a8ci18n]

Translation for this Pull Request has now been finished.