Every one of these features are just so, so fantastic. Really excited for all of them, but I love that the overrides to synced patterns feature is up next. That's going to allow me to keep sites nice and organized across pages with minimal effort required (and less detaching patterns - I always hate when I have to detach patterns just to change a few words!)
It's really great to hear you're excited about thee features. I agree that overrides to synced patterns is going to be super powerful. Users have been requesting this feature for some time but we needed to wait for the editors APIs to evolve in order to deliver a robust experience and we are finally there!
@@DaveOnWP I just tested it out a bit and I'm wondering if the following functionality is possible. If you set up a pattern with, say, a heading block, paragraph block and a button block (enable overrides on all of them), is it possible to leave one of these blocks empty on an instance of that pattern and have it completely omit that block from rendering? So removing the text from the heading block in that instance would have it simply not render on the front end. Currently, it looks like it does output the block HTML on the front end, it's just an empty element that takes with it the margin, padding defined in the source pattern.
@@steamboat9592 It's a good use case which I'm not sure is possible right now. We still have time to fix that though. To that end I've passed on your feedback to the contributors working on the Tracking Issue github.com/WordPress/gutenberg/issues/59819#issuecomment-2088165643
@@DaveOnWP Cheers, Dave! That would allow you to have an "all the possibilities" pattern so the user can omit pieces that aren't needed in each instance.
Agreed. Section styles + Compose Zoom Out mode will making assembling Pages so much better. I'm looking forward to seeing if this matures in time for 6.6!
Supercool. Thank you both for sharing! This is the type of content I’d like to see far more often. Such content could help engaging people to hop on with contribution, beginning with needed feedback. Please, go on!
Thank you Carsten! It's great to hear this type of content was useful. I'll be looking to reprise it for the next cycle post WordPress 6.6 so look out for that video. Maybe @richtabor will join me again 🤞 As you say, the aim is precisely to encourage contributions and get feedback so I'm hopeful this will spur folks to engage and help shape the direction of WordPress. Thanks again for taking the time to comment I really appreciate it 🙇
Glad you like that. It's currently a stylistic treatment that's isolated to Compose / Zoom Out mode so that it's clear things are "different". Perhaps it could evolve elsewhere in future. Let's see where it takes us.
Yes, I am not sure about it being different in just one spot. What I like about it is that it has much more contrast, as the regular version is really something one has to search for at times. Its tone-on-tone style is really not my thing, and Brizy has proven that the black version is pretty effective on layouts.
I didn't understand how are you going to give posibilitisi to user change the some params for grid structure. Can you explain? Let's say in my design I have a .block {display:grid; grid-template-columns: 300px, 1fr, 1fr;} @media (max-width: 450px) { .block {grid-template-columns: 1fr, 1fr;} } and @media (max-width: 390px) { .block {grid-template-columns: 1fr;} } How can this be achieved?
The editor is not currently optimising too allow users control over low level features such as media queries. Rather the aim is to allow for Intrinsic Design where things "just work". That does mean some more advanced layouts are going to continue to require CSS for a while longer. If you are looking to understand more about why the editor takes this approach then you might like to watch this Hallway Hangout on Intrinsic Design: make.wordpress.org/themes/2024/01/30/hallway-hangout-intrinsic-design/
You are very welcome. I hope it brings some visibility to things that are already public but perhaps not obvious to those who don't work on the project full time.
🔗RESOURCE LINKS 🔗
🔍Tracking Issues
1. Advancing the Site Editor - github.com/WordPress/gutenberg/issues/59659
2. Overrides to Synced Patterns - github.com/WordPress/gutenberg/issues/59819
3. Composing with Patterns via Zoomed Out View - github.com/WordPress/gutenberg/issues/50739
4. Section Specific Styles - github.com/WordPress/gutenberg/issues/57537
5. Grid Layout - github.com/WordPress/gutenberg/issues/57478
👨Rich Tabor
- Website: rich.blog
- Twitter / X: twitter.com/Richard_Tabor
- Shaping WordPress Newsletter - blog.us6.list-manage.com/subscribe?u=e7267bfd563b8f29ef95ba846&id=3ad25ea4f0
📖Other Resources
- Follow Dave on Twitter/X - twitter.com/get_dave
- WordPress Admin redesign - github.com/WordPress/gutenberg/issues/53322
- Patterns as Sectioning Elements - github.com/WordPress/gutenberg/issues/39281
- WordPress Playground - wordpress.org/playground
- WordPress 6.6 Development Cycle - make.wordpress.org/core/6-6/
- Hallway Hangout on what’s next in Gutenberg - th-cam.com/video/JaZoPXu57-c/w-d-xo.html
Every one of these features are just so, so fantastic. Really excited for all of them, but I love that the overrides to synced patterns feature is up next. That's going to allow me to keep sites nice and organized across pages with minimal effort required (and less detaching patterns - I always hate when I have to detach patterns just to change a few words!)
It's really great to hear you're excited about thee features. I agree that overrides to synced patterns is going to be super powerful. Users have been requesting this feature for some time but we needed to wait for the editors APIs to evolve in order to deliver a robust experience and we are finally there!
@@DaveOnWP I just tested it out a bit and I'm wondering if the following functionality is possible. If you set up a pattern with, say, a heading block, paragraph block and a button block (enable overrides on all of them), is it possible to leave one of these blocks empty on an instance of that pattern and have it completely omit that block from rendering?
So removing the text from the heading block in that instance would have it simply not render on the front end. Currently, it looks like it does output the block HTML on the front end, it's just an empty element that takes with it the margin, padding defined in the source pattern.
@@steamboat9592 It's a good use case which I'm not sure is possible right now. We still have time to fix that though. To that end I've passed on your feedback to the contributors working on the Tracking Issue
github.com/WordPress/gutenberg/issues/59819#issuecomment-2088165643
@@DaveOnWP Cheers, Dave! That would allow you to have an "all the possibilities" pattern so the user can omit pieces that aren't needed in each instance.
Section styles will be helpful. Just read rich's post about patterns on automattic dot design, and can't wait to apply styles to them like that.
Agreed. Section styles + Compose Zoom Out mode will making assembling Pages so much better. I'm looking forward to seeing if this matures in time for 6.6!
Wordpress is definitely an underrated web development environment, love that you are sharing upcoming upgrades to it. 🥂
Absolutely. And more proof of that is available when you realise you can run WordPress in your browser:
wordpress.org/playground/
Supercool. Thank you both for sharing!
This is the type of content I’d like to see far more often. Such content could help engaging people to hop on with contribution, beginning with needed feedback.
Please, go on!
Thank you Carsten! It's great to hear this type of content was useful. I'll be looking to reprise it for the next cycle post WordPress 6.6 so look out for that video. Maybe @richtabor will join me again 🤞
As you say, the aim is precisely to encourage contributions and get feedback so I'm hopeful this will spur folks to engage and help shape the direction of WordPress.
Thanks again for taking the time to comment I really appreciate it 🙇
The black on the toolbar is so much better!
Glad you like that. It's currently a stylistic treatment that's isolated to Compose / Zoom Out mode so that it's clear things are "different". Perhaps it could evolve elsewhere in future. Let's see where it takes us.
Yes, I am not sure about it being different in just one spot. What I like about it is that it has much more contrast, as the regular version is really something one has to search for at times. Its tone-on-tone style is really not my thing, and Brizy has proven that the black version is pretty effective on layouts.
Thanks Dave. I don't use core blocks much but the grid would be useful feature for many.
Grid is going to be HUGE. It's still got time to improve in terms of the UI and UX so let's see what's ready for WordPress 6.6.
I didn't understand how are you going to give posibilitisi to user change the some params for grid structure. Can you explain? Let's say in my design I have a .block {display:grid; grid-template-columns: 300px, 1fr, 1fr;} @media (max-width: 450px) { .block {grid-template-columns: 1fr, 1fr;} } and @media (max-width: 390px) { .block {grid-template-columns: 1fr;} } How can this be achieved?
The editor is not currently optimising too allow users control over low level features such as media queries. Rather the aim is to allow for Intrinsic Design where things "just work".
That does mean some more advanced layouts are going to continue to require CSS for a while longer.
If you are looking to understand more about why the editor takes this approach then you might like to watch this Hallway Hangout on Intrinsic Design:
make.wordpress.org/themes/2024/01/30/hallway-hangout-intrinsic-design/
Thanks for this
You are very welcome. I hope it brings some visibility to things that are already public but perhaps not obvious to those who don't work on the project full time.
Someone interview Rich about his skincare routine.
😆decent lighting is 90% of it.
😊
overkill
Thanks for your comment. Hopefully the power of the new features coming to WordPress will change your opinion in the future.