-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prototype: Move goals step to front of onboarding if onboarding/goals-first
flag
#96866
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~5598 bytes added 📈 [gzipped])
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. Generated by performance advisor bot at iscalypsofastyet.com. |
01507d6
to
c7e10a6
Compare
c7e10a6
to
ab74f20
Compare
This PR modifies the release build for the following Calypso Apps: For info about this notification, see here: PCYsg-OT6-p2
To test WordPress.com changes, run |
ab74f20
to
af0199d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and can access the Goals step in logged out state 👍
The original /start flow is not affected by the changes in this pr
@@ -170,6 +170,7 @@ | |||
"onboarding/trail-map-feature-grid-structure": false, | |||
"onboarding/trail-map-feature-grid": false, | |||
"onboarding/user-on-stepper-hosting": true, | |||
"onboarding/goals-first": true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm...it seems the default value should be false on both dev and staging since it is far from complete and it changed the behavior after creating a new site with proxy...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Proposed #97219
The goals step was unintentionally removed from all flows on staging in #96866. But we only want it removed when the user began on the `onboarding` flow.
The goals step was unintentionally removed from all flows on staging in #96866. But we only want it removed when the user began on the `onboarding` flow.
The goals step was unintentionally removed from all flows on staging in #96866. But we only want it removed when the user began on the `onboarding` flow.
Closes #96756
Proposed Changes
Uses an
onboarding/goals-first
feature flag to move the goals step to the very beginning of the onboarding flow. This PR allows you to prototype the change, but it is far from complete.CleanShot.2024-11-28.at.21.02.46.mp4
Why are these changes being made?
We want to start moving more onboarding tasks in front of the paywall. This creates a skeleton of that change. Once this PR is merged—hidden behind a feature flag—we can add tasks for each of the TODOs I've left in the code and have multiple people working on it.
CC @Automattic/vertex this PR is adding a feature flag to the
onboarding
flow as mentioned here p1732691488986329-slack-C02T4NVL4JJTesting Instructions
/setup/onboarding?flags=onboarding/goals-first
onboarding
flow/setup/onboarding
/start
/start
site-setup
stepper flow, that's the only place this might make unintentional changes to that flow.Pre-merge Checklist