Big Sky: Redirect from /home/

[artpi]

Fixes https://github.com/Automattic/big-sky-plugin/issues/2841
Fixes BSKY-191

What it does

• For sites that are part of ai-site-builder onboarding flow
• And on a plan different than one of the plans with Big Sky
• Redirect to a Big Sky modal

Testing instructions

• Create a site using setup/ai-site-builder flow
• Go to https://calypso.localhost:3000/home/siteslug
• Observe being redirected

The big thing to test is all the sites that are NOT big sky if they are not redirecting by accident

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

Sections (~159 bytes added 📈 [gzipped])

Details

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

• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug big-sky-redirect-home on your sandbox.

[kthai15]

The redirect from /home works, but do we need to worry about the other calypso paths, like /themes, /plugins, etc?

[dereksmart]

@kthai15 I think those would be caught if we did this https://github.com/Automattic/big-sky-plugin/issues/2841#issuecomment-2740638746

[kthai15]

I can confirm that there's no redirect on

• sites that were created outside the ai-site-builder flow
• sites that were created with the ai-site-builder flow but on a paid plan

If we're ok without implementing this or doing it as a followup then I think this is safe to merge

[artpi]

If we're ok without implementing https://github.com/Automattic/big-sky-plugin/issues/2841#issuecomment-2741609845 or doing it as a followup then I think this is safe to merge

I'm thinking we still allow /sites and block the launching on API end until you are on a paid plan