Reader Onboarding: Setup basic framework and feature flag

[DustyReagan]

Related to https://github.com/Automattic/loop/issues/189

Proposed Changes

• This PR introduces the reader/onboarding feature flag.
• It also proposes file locations and a fundamental framework to start building out the Reader Onboarding banner and modals.

Note

This code is behind the reader/onboarding feature flag in the development.config file. It is NOT visible to customers and is only visible if you're running Calypso locally. This PR is meant to be merged but is simply a starting place to begin iterative development.

Screen.Recording.2024-10-08.at.5.15.09.PM.mov

Why are these changes being made?

• To stake out a building site for the Reader Onboarding project.

Testing Instructions

• Open the Calypso Live link and go to /read
• Verify that the banner in the video above is not visible because it's behind a feature flag
• Apply this PR to your local dev environment (be sure to restart yarn so it'll pick up the changes to config file.)
• Go to http://calypso.localhost:3000/read and verify that the banner is visible
• What do you think of the file locations and initial framework?

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

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

Sections (~335 bytes added 📈 [gzipped])

name    parsed_size           gzip_size
reader      +1474 B  (+0.2%)     +335 B  (+0.1%)

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
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug try/reader-onboarding-framework on your sandbox.