-
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
Woo Installer: Landing page redesign #57419
Comments
This was referenced Oct 28, 2021
Use top part only for now |
Closing via #58179 but we may want to add additional content in the future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Redesign the /woocommerce-installation/ landing page based on the design in figma r6eTqDpL2GGk96hcPLhsBb-fi-0%3A1
I believe the images were placeholders so please confirm copy / images are good to use before starting (cc @JanaMW27)
Currently only business sites on atomic can load the existing page. The existing page renders a confirmation screen and then takes you through a plugin installation process. Eventually this will be completely replaced by the new onboarding flow leaving only your new landing page in its place.
The navigation menu is controlled by Jetpack and wpcomsh, it is currently only shown to atomic sites using wpcomsh. You can enable displaying the menu navigation item by adding the 'woop' flag in blogrc or using wpsh to add the site sticker.
For now we just need the landing page redesigned for these business+atomic site users, we will later swap out the installation step with the new onboarding flow under
/start/*
Implementation suggestion: Build this as a standalone new component under
client/my-sites/woocommerce/some-new-landing-page-thing
as we should be able to remove everything else that is currently in there once the new onboarding flow is completed.For now you should be able to import your new landing page component into this render function and pass in
startSetup
as the CTA handler.<SetupNotices />
Screenshot from figma (see there for more variations, ignore the premium plan upgrade stuff for now)
![Screenshot(45)](https://user-images.githubusercontent.com/811776/139239156-03a60470-cfde-4d5e-931d-01beb6affc91.png)
The text was updated successfully, but these errors were encountered: