Update 100-year domain copy

[fditrapani]

Proposed Changes

This PR adds custom copy for the 100-year domain purchase flow and it fixes a bug on mobile where the foldable card icon is not visible.

Before

After

Why are these changes being made?

We currently have stale copy for the 100-year domains. This PR updates it with new copy.

Testing Instructions

Visit /setup/hundred-year-domain/domains and compare against production (wordpress.com/setup/hundred-year-domain/domains)

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-129150

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[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 add/100-year-domain-content on your sandbox.

[matticbot]

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

Sections (~1518 bytes added 📈 [gzipped])

name                  parsed_size           gzip_size
update-design-flow        +1032 B  (+0.1%)     +466 B  (+0.2%)
link-in-bio-tld-flow      +1032 B  (+0.1%)     +482 B  (+0.1%)
copy-site-flow            +1032 B  (+0.2%)     +464 B  (+0.3%)

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.

[a8ci18n]

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

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

[a8ci18n]

Translation for this Pull Request has now been finished.

[southp]

This works and is probably the only way under the current structure. However, it would be better if info-modal simply shows the copies assigned to it, rather than conditionally showing different copies based on the flow name.

Decoupling this is non-trivial though.

• We'd need to extract the mechanism of customizing step wrapper component: https://github.com/Automattic/wp-calypso/blob/trunk/client/landing/stepper/declarative-flow/internals/steps-repository/domains/index.tsx#L305
• We'd also need to implement the mechanism of passing . In this case, conceptually only hundred-year-plan and hundred-year-domain flows know what to show in the info modal, so those should be configurable right in their flow implementation, e.g. https://github.com/Automattic/wp-calypso/blob/trunk/client/landing/stepper/declarative-flow/hundred-year-domain.ts#L65 .

@alshakero Are there existing ways that we can better structure this?

[fditrapani]

Thanks for taking a look @southp. Should we handle restructuring this code in a separate PR? Can we go ahead and merge this?

[leonardost]

LGTM, checked and everything looks good! 👍 Sorry for the delay for this review!