Editor chat summary: Wednesday, 4 May 2022

This post summarizes the weekly editor chat meeting on Wednesday, 4 May 2022, 14:00 UTC held in Slack.

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 13.2 RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta).

George Hotelling is going to release Gutenberg 13.2 RC. The PR’s part of the release are available at https://github.com/WordPress/gutenberg/milestone/177. The release contains 154 PRs.

WordPress 6.0 Project board & WordPress 6.0 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 4 & WordPress 6.0 RC 1

WordPress 6.0 RC was released on the 3 of May. Everything is going according to the plan no critical or blocking issue has been found. There are still some tasks on the 6.0 board https://github.com/orgs/WordPress/projects/27, these tasks will probably be part of 6.0.1.

Help Wanted: Test WordPress 6.0

Any help testing the latest version and making sure there are no issues there can have a great impact. Please try your development website with the last RC. And in case you find any issue please report it so the team can fix it.

Key projects updates

Patterns & Styles

@jorgefilipecosta share the updates for patterns and styles as follows:

Right now, we have a style object on the blocks that follow a similar shape to the theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. styles, but they are not equivalent, and also, not everything theme.json supports is supported there. The idea is to have blocks support local settings and style objects @oandregal started the work on the settings part. On the styles front we had tremendous progress that makes the style theme.json object color and typography keys be supported https://github.com/WordPress/gutenberg/pull/40332. Thank you @ramonopoly!

In order to have settings with semantic meaning, a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. instance needs to have a name and probably information related to the type of section keywords, etc. @jorgefilipecosta started and iterated on the work to implement the metadata infrastructure for these sections https://github.com/WordPress/gutenberg/pull/40393.


@santosguillamot said regarding comments he just published an update on the tracking issue of the PRs that have been merged and included later in the RC.

Task coordination



  • To merge the section’s metadata PR.
  • Help the exploded view PR get merged and the refactors it involved including the popover.
  •  Finish some tasks I have pending related to the list v2 block.


Has earlier been giving feedback through issues to various Comments block features and Going forward plans on testing WP 6.0 Beta/RC releases.


Has worked on performance improvements for Navigation blocks and a few more last-minute fixes for the WordPress 6.0 release.

Open floor

UIUI User interface to create a single template

@jessica asked if there is a specific reason we can’t add single templates in the site editor?

@jorgefilipecosta said he thinks that the task is available for someone to pick.

@jessica submitted a PR fixing the issue after https://github.com/WordPress/gutenberg/pull/40830.

Wide alignments on nested blocks

@cbirdsong asked why when theme.json is enabled one can not use wide/full alignments on nested blocks liking to the issue https://github.com/WordPress/gutenberg/issues/33374. Adding that, This is the core reason my custom theme builds don’t use theme.json, and as more features are gated behind using it, he was wondering if there is any chance of some re-evaluation of disallowing nested wide/full alignments.

The team discussed this issue and concluded the issue could be divided into two parts:

  • First, the cover block is missing a layout panel.
  • The default for blocks is not “inherit default layout”.

@cbirdsong will follow up and create the two issues.

#agenda, #core-editor, #editor, #summary