Jetpack Manage: 192 - add NextSteps component to Overview page

[tbradsha]

Resolves Automattic/jetpack-manage#192 - add NextSteps component to Overview page

Proposed Changes

This introduces a NextSteps component for the Overview page. Of note:

• The four tasks are currently static; they will be connected to the tour triggers in Server Side Rendering: Stub/replace components that depend on the DOM/BOM #194.
• Upon completion, one receives the option to dismiss the card.
• The card should not show on mobile size screens (<=600px).
• Tracks will fire when clicking on each task or when dismissing the card (possible upon completion).

Originally I found the Launchpad component, but in the end it is tightly integrated with Calypso Blue and would require implementing a new set of listeners + API calls, so I dug a bit deeper and used the Checklist component it uses internally.

Testing Instructions

One can manually update the completed booleans for each task and see the correct states. Tracks should fire when clicking on each task and when dismissing the dialog.

The hidden task can be brought back by clearing the key out of localStorage:

delete localStorage.jetpack_manage_hide_next_steps;

No tasks completed:

Two tasks completed:

Fully completed:

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

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

[matticbot]

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

Sections (~1673 bytes added 📈 [gzipped])

name                    parsed_size           gzip_size
jetpack-cloud-overview      +5699 B  (+1.4%)    +1633 B  (+1.2%)
write-flow                   +241 B  (+0.0%)      +20 B  (+0.0%)
videopress-flow              +241 B  (+0.0%)      +20 B  (+0.0%)
subscribers                  +241 B  (+0.0%)       +9 B  (+0.0%)
link-in-bio-tld-flow         +241 B  (+0.0%)      +20 B  (+0.0%)
home                         +241 B  (+0.0%)      +11 B  (+0.0%)
earn                         +241 B  (+0.0%)      +20 B  (+0.0%)
build-flow                   +241 B  (+0.0%)      +20 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 (~50 bytes added 📈 [gzipped])

name                                                 parsed_size           gzip_size
async-load-masterbar-launchpad-navigator                  +241 B  (+0.4%)      +28 B  (+0.2%)
async-load-calypso-my-sites-stats-stats-subscribers       +241 B  (+0.1%)      +22 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.

[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/jp-manage/192/add_next_steps_component on your sandbox.

[gogdzl]

@yashwin suggested in #85488 (comment) to separate the emoji from the text.

[tbradsha]

Unless there's a good reason to change it, I think it's best to keep it as-is. Splitting it means less flexibility for translators, which in general is a bad idea (though honestly I prefer no emojis).

[gogdzl]

Aside from my comment, the code looks good and works as advertised!
Great job!

Approving this as my comment is not a blocker.

[a8ci18n]

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

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

[a8ci18n]

Translation for this Pull Request has now been finished.