Editor chat summary: Wednesday, 20 April 2022

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, April 20 2022, 03:00 PM GMT+1

General Updates

Async key project updates

We used to exchange key project updates synchronously during the chat. However, many of the key 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/ projects sustain a regular cadence of updates on their tracking issues on 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/.

This week we tried async updates. The attendees are encouraged to read the latest updates directly from the following tracking issues at everyone’s leisure:

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.

Open Floor


Announced that there is a new Pull Request template that got introduced lately, it follows the What? Why? How? format. In today’s discussion, some feedback to that template was surfaced, such as:

  • What? Why? How? may read abrupt
  • Achieving additional clarity seems easy
  • More discussion would make for a great next iteration

And so I opened this issue to iterate on the template: https://github.com/WordPress/gutenberg/issues/40470


Raised that he wants to propose removing the Reusable 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. edit locking feature from WP 6.0. He commented summary of the recent discussion in the tracking issue – https://github.com/WordPress/gutenberg/issues/29864#issuecomment-1103592492.


Raised that if anyone had PRs/Issues that are related to WordPress 6.0, please make sure they are added to the 6.0 Project Board. This is the first place we are looking when triaging issues and we don’t want to inadvertently miss anything.


Raised that after watching the 6.0 Product Walk-Through, he didn’t find the following blocks in 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. 2:

  • Post Author Name
  • Post Comments Count
  • Post Comments Form
  • Post Comments Link

With WP 6.0 Beta 2, it’s not possible to build a comment section as there is no Post Comments Form, and the Post Comments block has been deprecated. Will they be included in WordPress 6.0?


Raised that they were trying to test #45021, they got this jarring click ignore. I suppose that’s not a Media issue though, is it? They wanted to figure out whether it was already an issue, that the click is being ignored?

Read the complete transcript

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