You can find the full meeting transcript on Slack (login required)
Meeting coordinator: @jffng
Notes kept by @ashiquzzaman
Time: Wednesday, 19 May 2021, 21:00 GMT+6
Channel: #themereview
Gutenberg + Themes Updates:
The feature freeze for Gutenberg 10.7 is today
- You can now remove the experimental prefix from your theme.json files: https://github.com/WordPress/gutenberg/pull/29981
A fallback was added so it’s not going to break if you still have the experimental-theme.json file name.
- There is on-going discussion and work about how the theme color palette and core color palette interact and are surfaced to users. Very interesting reading and progress: https://github.com/WordPress/gutenberg/pull/31669
In the Full Site Editing project, the template resolution logic was simplified for its inclusion in core: https://github.com/WordPress/gutenberg/pull/31604
- The first iteration of a responsive mobile option to the nav block was merged: – https://github.com/WordPress/gutenberg/pull/30047
- There’s an issue here to discuss feedback to block theme developer docs: https://github.com/WordPress/gutenberg/issues/31999
- And the create block theme tutorial was given a fresh update: https://github.com/WordPress/gutenberg/pull/31269
TT1 Block Updates
@poena highlighted that the theme needs to be tested and packaged for release to .org . It becomes more difficult to do the call for testing in the FSE outreach program without the updated theme on .org. She is also working on removing the theme blocker. All the TT1 reupload to the theme directory can be tracked here – https://github.com/WordPress/theme-experiments/issues/264
Discussion: continue the Universal Themes conversation from last week’s hangout:
The global styles UI will not be in 5.8. As 5.8 is a minimum viable product.
@Grogou how can users configure global styles? @poena replied – Per block, per template, with reusable blocks, and patterns. or, why not let the theme author offer the templates that work well with the theme.
There are some ongoing experiments to see what else can be done (via Customizer) but nothing concrete that can’t already be done via PHP template pages.
So a mix (using theme.json to build a ‘base style’ with php template pages to execute logic from configuration options set in a classic way via Customizer) is the straightest line for 5.8 without the Gutenberg Plugin where Global Styles UI can be leveraged in the FSE.
@aristath mentioned that a lot of concern regarding feature parity between the customizer and the site-editor.
The fact that something can be edited in the site-editor doesn’t necessarily mean that it should also be editable from the customizer.
It is possible to expose all global-styles options in the customizer and save them the way that global-styles get saved, the customizer has the architecture to support that. But someone has to write that bridge, and tbh it’s just not a priority or necessity for anyone at this stage.
@scruffian shared an example of how to change Global Styles in the Customizer: https://github.com/Automattic/themes/pull/3856
@aristath is working on a package that will allow legacy themes to use theme.json : https://github.com/WPTT/theme-json-parser, Being able to use the theme.json file is one step closer to block themes and should allow theme authors to remove a lot of CSS.