WordPress / developer-blog-content

In this GitHub space, WordPress team coordinates content to be published on the Developer Blog. Discussions and montly meetings (first Thu - 13:00 UTC) in WP Slack #core-dev-blog
https://developer.wordpress.org/news
40 stars 5 forks source link

theme.json custom CSS tutorial #97

Closed bph closed 1 year ago

bph commented 1 year ago

Discussed in https://github.com/WordPress/developer-blog-content/discussions/93

Originally posted by **justintadlock** March 28, 2023 WordPress 6.2 will allow developers to create per-block CSS via `theme.json`: https://github.com/WordPress/gutenberg/pull/46571 This topic idea is to walk theme authors through the process of using this feature, compare it with using stylesheets, and its relationship with the Styles interface in the editor. It will provide code examples for creating CSS to handle use cases that the built-in design tools are unable to.
justintadlock commented 1 year ago

Beginning work on this here: https://docs.google.com/document/d/1JePD4Cb0MnHP50IdU18WEY7zsxYl_YbB3vZ94PcMo0Q/edit?usp=sharing

justintadlock commented 1 year ago

The first draft is now ready for review in a Google Doc.

Note: I still have a screenshot I need to update, but it shouldn't affect the content of the post.

marybaum commented 1 year ago

Excellent! I’ll be home in 20 minutes and take a look in the next two hours.MB... from my phoneOn Apr 20, 2023, at 8:39 AM, Justin Tadlock @.***> wrote: The first draft is now ready for review in a Google Doc. Note: I still have a screenshot I need to update, but it shouldn't affect the content of the post.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

marybaum commented 1 year ago

Done!

justintadlock commented 1 year ago

Thanks, @marybaum. Great feedback, as always!

justintadlock commented 1 year ago

Published: https://developer.wordpress.org/news/2023/04/per-block-css-with-theme-json/

Thanks to @marybaum, @bph, and @carolinan for feedback and review.