-
Notifications
You must be signed in to change notification settings - Fork 7
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
Tutorial on using block style variations in WordPress 6.6 #270
Comments
I'm working on this post here: https://docs.google.com/document/d/1tLiVODp8FYo8J8CkXml58oUghhVwtSrOqByudRG2OBU/edit?usp=sharing |
This one is ready to review now. |
Great article @justintadlock. Added some notes/suggestions. |
@justintadlock I read through about 3/4. I mainly wanted to understand this feature because I feel out of the loop. I left some relatively high-level reflections as comments in the document. Please feel free to disregard them and consider them just me thinking out loud. Thanks for writing this up and taking the time to share it all. |
Finished with the first review. @colorful-tones - Want to read the last 1/4 and wrap up the 2nd review? |
@justintadlock I finished reading 😄 . I like the update with Section 1 + Section 2; it solves the contextual use case well. 👍 I particularly like the authenticity of the following:
🫶 🤘 |
Thanks, @ndiego and @colorful-tones! I've went through everything and did another editing pass myself. Planning to publish tomorrow. Note to self: Check if the linked Dev Note in the post is published. If not, reword the sentence and add the Dev Note link later. |
Social Copy:
|
scheduled for July 24 |
Discussed in #268
Originally posted by justintadlock June 4, 2024
Block style variations will see some major improvements in WP 6.6:
theme.json
, which was previously limited to Core-only variations (styles.blocks.blockName.variations
).styles.blocks.variations
./styles
folder with theblockTypes
property.See:
These are major improvements to the block style variations system that could potentially save 100s of lines of custom CSS and consolidate most theme styling to the standard
theme.json
.It's also a good opportunity to call for testing of potential breaking issues with reduced style specificity:
A tutorial for the Dev Blog would be welcome that explores what each of these changes mean for styling themes and how that compares to what was previously possible. It should also explore any potential pitfalls or areas where you still need to rely on custom code. But the big thing is to share the major "wins" that these update bring to theme design.
A side note to consider: this could be the precursor to opening custom style variations via the Styles panel in the editor UI.
The text was updated successfully, but these errors were encountered: