Created initial structure to My Home Launchpad using the entire home

[paulopmt1]

Related to #98348 and #98349

Proposed Changes

• We're adding a new feature flag called home-launchpad which will add support to the Launchpad using the entire Home
• Hide all home content except the Launchpad when the feature flag home-launchpad and the launchpadOnly get parameter is received at the home page

Note: We're adding both the feature flag + URL parameter because in the following iterations, some components will use the feature flag to behave differently and the /home page will use both parameters. With this feature flag we can easily isolate the deliverables of this project.

Why are these changes being made?

• This is part of Launchpad In My Home project: pet6gk-1T7-p2

Testing Instructions

• Go to your home page and add the following parameters to it: ?flags=home-launchpad&launchpadOnly=true

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

Sections (~55 bytes added 📈 [gzipped])

name  parsed_size           gzip_size
home       +168 B  (+0.0%)      +55 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

• blaze-dashboard
• command-palette-wp-admin
• help-center
• notifications
• odyssey-stats
• whats-new

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/prepare-my-home-launchpad on your sandbox.

[candy02058912]

Tested and it works ✅

I do wonder if we want to create a new version of /home with only the launchpad so the logic doesn't feel tangled with feature flag + params.

We'll control which /home the user gets to through the feature flag at a higher level like here:

wp-calypso/client/my-sites/customer-home/controller.jsx

Line 30 in 1ec67d4

context.primary = <CustomerHome key={ siteId } />;

For example the newsletter flow will redirect over to the new home with launchpad only page.

Would love to hear other thoughts 👂

[zaguiini]

I do wonder if we want to create a new version of /home with only the launchpad so the logic doesn't feel tangled with feature flag + params.

+1, it feels like we're just gating a small feature, but this is almost a full-page redesign. I'd appreciate splitting it entirely between files.

[zaguiini]

We're moving forward with #98476