-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Layout: Document the current state of the layout block support #42619
Conversation
56a5d88
to
1dbb50a
Compare
8df0b84
to
4db074e
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.
Content is good and clear.
Thank you for writing this!
Co-authored-by: Ramon <ramonjd@users.noreply.github.com>
Co-authored-by: Ramon <ramonjd@users.noreply.github.com>
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.
Thanks for writing this out, it's very comprehensive! Just one small nit re: naming but looks good otherwise 🎉
Co-authored-by: tellthemachines <tellthemachines@users.noreply.github.com>
Thanks for all the feedback @ramonjd and @tellthemachines, I've pushed updates to address each of the notes. I doubt the performance tests will be finished before I wrap up for the day, so I'll look at merging this in tomorrow.
On this note, I always love detailed feedback on grammar, so very happy for these sorts of comments and explanations! 🙇 |
What?
Following on from #40875 and as part of #39336, this PR attempts to document the current state of the Layout block support.
Why?
While the Layout block support is currently an experimental feature, it is only experimental in the sense that the API is unstable and likely to change. The feature is in use in core and production sites, so while it is experimental, let's attempt to document the current state of the layout support, the purpose and intention behind it, and what it outputs.
The goal with this PR should be to help make it easier to understand how and why things are happening, and also how to opt-in or opt-out of the behaviour as needed (tying into #42544)
How?
styles
architecture page to include a section on Layout. If need be, we could always pull Layout into a separate file, but I think it makes sense to keep it with the other styles topics.Tasks
blockGap
styles and expose the UI for itis-layout-constrained
now that the constrained layout type has been added: Try "constrained" content width as new layout type #42763Testing Instructions
👀 Proofread and verify that the information is accurate 😄