Editor chat summary: Wednesday, 10 November 2021

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, November 10, 2021, 03:00 PM GMT+1.

General Updates:

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/ 11.9

Gutenberg 11.9 RC4 was released earlier today and the goal is to publish the stable release Thursday morning APAC time, which should be around the end of the day Wednesday 10th in North America.

See the note from @andrewserong in Slack.

WordPress 5.9

Planning Roundup
Preliminary Roadmap
Feature Go/No Results

@noisysocks shared the following 5.9 related updates:

  • The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. patches have been merged for 5.9. Follow up work from this is ongoing.
  • Gutenberg needs to be updated to work with core trunk. There were CI test failures so we changed CI to run 5.8.2 as a temporary fix. @danr is working on updating Gutenberg, but help is appreciated
  • Please add the backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. label to bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fix PRs
  • Please pick up an issue or two from the Must Haves board. There’s a few things with no assignee

@mkaz shared an update on documentation for 5.9:

I’ve created a new public GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ project to track documentation needs for the WP 5.9 release. You can access it at: https://github.com/orgs/WordPress/projects/11

Let me know if you have trouble accessing that link. GitHub project is a new tool so I’m still getting familiar, but basically a spreadsheet connected to GitHub issues and tickets.

I pulled in all tickets labeled “Needs Dev Notedev 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.” so please if you’ve worked on a ticketticket Created for both bug reports and feature development on the bug tracker. definitely take a look. I’ll reach out and confirm assigned, the ones listed now were pulled in automatically.

The “Doc Type” label is a general categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. I made up for the items.

  • Dev Note is a specific post on Make Core for developers for any breaking changes in a release.
  • User Docs is intended for user facing documentation of new features for non-developers. For example, how do I use Global Styles?
  • Dev Docs is a catch-all for all other developer documentation that isn’t necessarily a specific Dev Note, for example “How do I create 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. theme?” or APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. updates.

One thing to note, the tabs at the top are actually views, so entries are filtered by the type. So if you switch to a “tab” and add an entry, it actually “disappears” since it doesn’t have the correct type to be shown in that view. So adding items is easiest in Overview (all items) and then enter the Doc Type.

Updates on the key projects:

@get_dave shared an update on the GitHub Tracking issue

  • Work has continued on making Navigations reusable across a Site and between Themes.
  • Navigation Area block was added to facilitate the reuse of Navigations between Themes. You can now switch Themes and (if the target Theme is configured correctly) your Navigation will be preserved.
  • This works somewhat similarly to Menu Locations in classic Themes:
    • you add a Nav Area block and configure it to be PrimarySecondary or Tertiary. These terms are provided by default and denote an approximate hierarchy of navigations on a site.
    • you then insert a Nav block inside the Nav Area block. This can be used to configure presentational properties of a given Menu and is ideal for Theme Developers. Note you do not need to add any nav items at this point.
    • you then optionally add items to your Navigation block.
    • when switching Theme, assuming the new Theme also has a Navigation Area block with a matching “area” (e.g. Primary, Secondary, Tertiary), then any nav items from matching Navigation Areas on your old Theme will automatically appear in the associated location in the new Theme.
    • the navigation -> area relationship is saved via site options is a format of  { "primary": 794, "secondary": 112 }where the keys are the navigation areas and the values are the post IDs of Navigation post types.
  • Lots of great work behind the scenes work on the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. which has allowed all of the above to progress.
  • Tweaks to the UIUI User interface and UXUX User experience of the block itself have been ongoing.


@Antonis Lilis

Improvements and Fixes

  • Fix on the synchronisation mechanism for serialising content from the editor on Android
  • Added more Integration tests for Embed block
  • Disabled swipe gesture on BottomSheets to fix scroll-axis issue

In Progress

  • Finalising tweaks to the Embed block
  • Finalising GSS Font size, line height and selected text colours.

Global Styles


  • The focus this week was porting all the infrastructure to the core (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. changes endpoints, etc) and that is done.

Template editor

  • No updates were shared



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.


Always navigation. So much is in flux, but I’m looking at bugfixes related to justification, theming, submenus and others. It would help me if github.com/WordPress/gutenberg/pull/36298 could be approved soon.


I’m primarily working on WP 5.9 Must-Haves, helping with reviews, and trying to fix bugs, now and then.

Open Floor:


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