-
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
Add/editing toolkit coming soon #45167
Conversation
Caution: This PR affects files in the Editing Toolkit Plugin on WordPress.com D48549-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 |
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~17 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~1370 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. Async-loaded Components (~181 bytes added 📈 [gzipped])
React components that are loaded lazily, when a certain part of UI is displayed for the first time. 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. |
9c445d3
to
b99f501
Compare
f6a6fb2
to
2af7ddc
Compare
I don't have much to add yet, but this is coming along nicely already! I was pleasantly surprised at how easily this seems to be able to override the existing coming soon mode by just setting public to 0, and therefore none of the existing coming soon behaviour will fire. I think I might have been overthinking things in regards to supporting coming soon v1. I'm not too sure where you're up to in the PR yet, but I was able to successfully display the fallback coming soon on my test site, but switching a page to Coming Soon from the pages view looks like it's doing the correct thing in Calypso, but doesn't appear to show the page for me yet. Calling |
thanks for testing @andrewserong !!
I was just trying to get that working this afternoon when time ran out. Feel free to take a stab tomorrow if you dare ;) |
Thanks @ramonjd! Got it working, just needed a tiny update to D45700-code (the site option was set to |
I thought I might have a go at copying over the markup for the existing Coming Soon page to this PR later on this afternoon — but let me know if I'll be stepping on toes by messing around in this PR and I can branch off this one, or look at a different area (like getting the launch / logged in coming soon banner to support the new public coming soon mode). |
Awesome, thank you for catching that one I missed!
Go ahead to do whatever you want. Don't wanna break your stride. I'll peel off and look at something else. |
Fallback coming soonI've added the current Coming Soon markup as the fallback and got it to load Recolata
Coming soon page selectedHere's what it looks like if I pick a Coming Soon page (here I've just created a simple page with a big Cover block and gradient background): Other screenshots of the current state of the PRJust adding a couple of other screenshots to show the current state of the PR for anyone else looking on :) There's still heaps more to do of course! |
Amazing progress! Settings Page
Pages List
Live site
|
Thanks for capturing these ideas!
Maybe we could start on this, putting it behind some query option in
To the editor version? Either way, good idea. Noted.
This would be worth looking into now too @roo2 Not sure what the right logic would be, but I guess we should be able to switch between home and coming soon types as we wish. Noting that if a user switches a coming soon page to be the home page, they'll fallback back to the default coming soon page (if the feature is activated.
I guess so. I think only the user themselves sees the full site if they're logged in (and with coming soon enabled)
Maybe we could address that in #44888 ? |
Great, yea I'd quite like to take a look at this on this PR/branch |
Taking great inspiration from #43831
Renamed wpcom_coming_soon_mode to wpcom_coming_soon
0fc52af
to
4b266c1
Compare
rebased |
remove_action( 'wp_head', 'global_css', 5 ); | ||
remove_action( 'wp_footer', 'wpcom_subs_js' ); | ||
remove_action( 'wp_footer', 'stats_footer', 101 ); | ||
wp_enqueue_style( 'recoleta-font', '//s1.wp.com/i/fonts/recoleta/css/400.min.css' ); |
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.
No strong opinion on this, but you might also look at importing in CSS from the typography package. That'll keep it more in one source of truth for fonts.
Did a bit of work on this in #45581 let me know if all that is ok to push into this, I'm not sure I've done the typography import right so didn't feel too comfortable pushing into this PR directly. |
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.
Closing this one in favour of #45581 |
Changes proposed in this Pull Request
This is a PR to try things out. Test our approach.
Testing instructions
D45700-code
Fixes #