Channel: #themereview
Facilitated by @kjellr
Gutenberg + Themes Highlights
- WordPress 5.6 was released last week.
- Header blocks will soon have a font-weight setting
- We want to load the Site Editor in an iFrame to give us a clean slate for styles in the front and back end.
- Custom units are now an option for the spacing control.
There are more Gutenberg updates in the latest Gutenberg + Themes post.
Twenty Twenty-One (TT1) Blocks
Work is accelerating on the new Block version of TwentyTwentyOne. This is centered around this project board.
The aim of this project is to reevaluate all of the Block specific CSS in TwentyTwenty one and determine if it’s still needed, and if it is, whether to move to Gutenberg; make it configurable via Global Styles, or add it to TT1 Blocks.
In many cases this is resulting in new issues and PRs in Gutenberg. We are keeping track of these on the board. Cards that are blocked by a Gutenberg issue should be moved to “Blocked” until the Gutenberg issue is fixed. This will give us a comprehensive list of all the issues we need to fix to get TT1 Blocks launched.
With the FSE Outreach Program starting up again soon, we’d like to add TT1 Blocks to the Theme Repository to make it easier for users to test Full Site Editing. We’ll use the name TT1 Blocks to ensure that users don’t get confused with the default theme TwentyTwentyOne.
Requirements for Block Themes
There was some discussion about the requirements for full site editing themes. The following changes were proposed:
- Make the theme.json file a requirement
- Remove the requirement for specific php templates (e.g. header.php)
We need to ensure that the block markup in a theme submission is valid. Exactly how we go about this is something which still needs exploring.