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
Gutenboarding: add PlansGrid accordion #45054
Conversation
516473c
to
e962d01
Compare
This still wouldn't launch it to customers, right? Either because we'd not be directing traffic to "experimental" flow yet or otherwise? |
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~1179 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~26 bytes removed 📉 [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. |
Caution: This PR affects files in the Editing Toolkit Plugin on WordPress.com D48381-code has been created so you can easily test it on your sandbox. See this FieldGuide page about developing the Editing Toolkit Plugin for more info: PCYsg-ly5-p2 |
d294d5f
to
9d88006
Compare
Yes, the experimental branch containing feature picker and accordion plans grid would be hidden behind Once this is tested and merged (together with Editing Plugin and wpcom-block-editor widget) we can start sending traffic from some A/B tests. |
isOpen={ isOpen } | ||
onPickDomain={ onPickDomainClick } | ||
disabledLabel={ disabledLabel } | ||
/> |
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.
This is the main change that was actually introduced in this PR. Everything else is mostly just reverting the accordion styled PlansGrid revert while keeping the "stable" multi-column PlansGrid.
I've decided to extract PlansFeatureList
since it's almost identical in both versions of the PlansGrid. I've added multiColumn
prop for now but I'm pretty sure the same effect can be achieved with a fluid layout (decide on the minimum width and let flex-wrap
to automatically decide the number of columns).
cc: @yansern @alshakero
46264e6
to
e2fda01
Compare
Superseded by #45280 |
f93db50
to
53895f3
Compare
…ehind gutenboarding/feature-picker flag
@razvanpapadopol there's at least one E2E failure from Gutenboarding that needs fixing. |
@@ -351,7 +351,7 @@ class CalypsoifyIframe extends Component< | |||
this.props.siteCreationFlow === 'gutenboarding' && this.props.isSiteUnlaunched; | |||
const frankenflowUrl = `${ window.location.origin }/start/new-launch?siteSlug=${ this.props.siteSlug }&source=editor`; | |||
const isNewLaunch = config.isEnabled( 'gutenboarding/new-launch' ); | |||
const isExperimental = new URLSearchParams( window?.location.search ).has( 'latest' ); | |||
const isExperimental = config.isEnabled( 'gutenboarding/feature-picker' ); |
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.
This "isExperimental" = "feature-picker" terminology can feel a bit confusing later on but I think it's fine now, and we'll sort it out later.
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.
Right now this would be easiest stable way to flip the switch between multi-column PlansGrid and accordion PlansGrid + Feature picker for both Gutenboarding and Site Setup flows.
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.
Makes sense 👍
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.
I'll test little more but two small visual findings. These can be follow-up PRs too:
Price loading state is a bit funky:
Hiding the /mo
completely vs placing it next to loading animation probably works best and is easiest.
Another is related to scroll positions:
- Expand all plans
- Click on domain to move to domains step
- Click continue
- Now you land in plans page where everything is collapsed again and scroll position isn't on top:
- Easiest would be at least to ensure we're on top when landing on plans page
- It might be helpful to store expanded/collapsed state during the session
Again, neither should block merging.
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.
Fixed in a659c2e
Fixed in 88877d0 |
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.
Double tested with new site with Chrome; looks like the landing on site title step was caused by something else than this PR (happens also in master
).
Other than that, the flow is looking good and works great. 👍 Let's get this in.
Changes proposed in this Pull Request
gutenboarding/feature-picker
flag in production environment).Testing instructions