You can find the full meeting transcript on Slack (login required)
Meeting coordinator: @kjellr
Notes kept by @ashiquzzaman
Gutenberg Updates:
- theme.json no longer fails silently if you miss a comma: https://github.com/WordPress/gutenberg/pull/3240
- On FSE adoption and “universal” themes, this issue has gained some additional traction this week: https://github.com/WordPress/gutenberg/pull/31235. This filter would allow themes with block templates to opt in or out of using the full-site editor. This would allow universal themes to support the customizer while FSE is under development (even with the Gutenberg plugin installed), and then gracefully enable the full-site editor when it’s ready.
- A call to attention on how block themes look in 5.8 (without the Gutenberg plugin active). Today, some block themes have implemented fallbacks or messages about requiring the plugin. But it varies per theme. From the discussion, it sounds like themes might get better built-in messaging like that for the 5.8 release. You can follow along with that or weigh in here: https://core.trac.wordpress.org/ticket/53410
Open Floor/ Q&A:
@scruffian highlighted the process on how authors are using Global Styles (especially – colors) as a mechanism for customizing their site. If you have a color that is used extensively in your site and then you want to change it, the only way to do so is to update that color in every place it’s used, which is quite laborious.
@onemaggie voiced the same concern with fonts, if a theme uses two fonts through multiple blocks, the user needs to go block by block if they want to change both
@aristath highlighted an update from GutenbergLand: theme.css files now also have the ability to be “lazy-loaded” when a block gets rendered, and there’s a PR to allow adding multiple stylesheets per-block. https://github.com/WordPress/gutenberg/pull/32510