Editor chat summary: 8 December, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, December 8 2021, 03:00 PM CET in Slack. Moderated by @fabiankaegy.

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/ pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party releases:

Gutenberg 12.1 was released.

What’s new in Gutenberg 12.1.0.

Parts of 12.0 and 12.1 were backported into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and will be part of WP 5.9.

WordPress 5.9

Beta 2 was released on December 7.
You can get an overview of how to help test WordPress 5.9 Features in this helpful post: https://make.wordpress.org/test/2021/11/30/help-test-wordpress-5-9-features/

@noisysocks shared the following update:

@mkaz shared that there are lots of Dev Notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. that need writing here: https://github.com/orgs/WordPress/projects/11/

Key project updates

Based on the scope for Site Editing projects.

Template Editor

@paaljoachim & @mamaduka

Global Styles


  • We are working on a redesign of how colors appear on the 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. inspector https://github.com/WordPress/gutenberg/pull/37067 To make the UIUI User interface simpler and less poluted


@Antonis Lilis


  • Fixed parsing issues on generating the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. bundle by using a newer version of the WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ command


  • Upgrade to ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native v0.66.
  • GSS Font size, line height and selected text color

Components Package

@Marco Ciampini


  • Some design polish was applied to both ColorIndicator and ItemGroup, which are both used extensively in the new Styles sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme..


In Progress:

  • We’re exploring approaches for maintaining focus when using components like Navigator (used, for example, in the Styles sidebar). 
  • We’re updating the LineHeightControl used in typography tools to use NumberControl internally instead of TextControl, which should provide more consistent styles and behavior.
  • There are a number of open PRs being discussed involving more consistent support for size variants across components, including CustomSelectControlFontSizePicker, and LineHeightControl.

Task Coordination:

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.


  • I’m primarily focused on Site Editor bug fixes and remaining items from WP 5.9 Must-Have list.
  • Trying to help with PR reviews.
  • Currently trying to track down cause of the two issues (probably related) with Template Parts.


If someone would like to help me with a review on this one, I’d be grateful! 


I am been testing WP 5.9 and will continue with testing.
Giving feedback to various Template Editor PRs.
I worry a bit about not having Custom templates included in WP 5.9, as it can create some confusion that one is not able to add a template.
I also think about the Preview control drop down in the Post Editor and Site Editor. These are too similar but not identical. We need a better diffraction between the two.


My main priority is finishing the color UI redesign and address some of the issues we found during the process.

Open Floor:


I am wondering if we still have time to get Custom Templates into WP 5.9?

This discussion was continued here: https://github.com/WordPress/gutenberg/issues/36860#issuecomment-987189021


Just wondering if 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. schema is still open for PRs. I have noticed that the appearanceTools is marked as a valid option but when added, triggers an error  – I need to open a ticket about it still

@mkaz and @oandregal chimed in here and deemed this to be a documentation change which is still ok to merge


I was wondering if this could be considered for WP 5.9?

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary