Sites: add domains page CTA

[mpkelly]

Closes https://github.com/Automattic/dotcom-forge/issues/2846

Mockup:

Proposed Changes

• Add a link button /domains/manage

Rvq9s7.mp4

Existing Tracks event:

Testing Instructions

• Try it out at /sites
• Check mobile and desktop match the Figma design
• Is the existing Tracks event enough?

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 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-ajp-p2)?

[matticbot]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-71970

Jetpack Cloud live (direct link)

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

[matticbot]

This PR modifies the release build for editing-toolkit

To test your changes on WordPress.com, run install-plugin.sh editing-toolkit add/manage-all-domains-button-to-sites on your sandbox.

To deploy your changes after merging, see the documentation: PCYsg-mMA-p2

[matticbot]

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

Sections (~243 bytes added 📈 [gzipped])

name                     parsed_size           gzip_size
sites-dashboard               +238 B  (+0.1%)      +73 B  (+0.1%)
import-hosted-site-flow       +238 B  (+0.0%)      +77 B  (+0.0%)
import-flow                   +238 B  (+0.0%)      +92 B  (+0.0%)
site-setup-flow                +23 B  (+0.0%)      +12 B  (+0.0%)
plugins                        +23 B  (+0.0%)      +12 B  (+0.0%)
media                          +23 B  (+0.0%)      +12 B  (+0.0%)
activity                       +23 B  (+0.0%)      +13 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.

Async-loaded Components (~12 bytes added 📈 [gzipped])

name                                               parsed_size           gzip_size
async-load-design-playground                             +23 B  (+0.0%)      +12 B  (+0.0%)
async-load-design-blocks                                 +23 B  (+0.0%)      +12 B  (+0.0%)
async-load-design                                        +23 B  (+0.0%)      +12 B  (+0.0%)
async-load-calypso-post-editor-media-modal               +23 B  (+0.0%)      +12 B  (+0.0%)
async-load-calypso-post-editor-editor-media-modal        +23 B  (+0.0%)      +12 B  (+0.0%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

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.

[zaguiini]

Working fine 👍

Is the existing Tracks event enough?

Yes, we can track link clicks.

[a8ci18n]

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

Thank you @mpkelly for including a screenshot in the description! This is really helpful for our translators.

[saygunnyc]

Thank you for quickly implementing this.
Can we ensure the secondary CTA uses the same styling as this other secondary CTA – Yes, make it My Home?

[a8ci18n]

Translation for this Pull Request has now been finished.