Editor chat summary: Wednesday, 27 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 27 2022, 04:00 PM GMT+1

General Updates

Brian Alexander had a few suggestions in his post Help Test WordPress 6.0

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

The attendees are encouraged to read the latest updates directly from the following tracking issues at everyone’s leisure:

Task Coordination



  • If you create an issue or PR that fixes a 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. related to the 6.0 release, please ensure it is added to the 6.0 Project Board. That is the best way to make sure we do not miss anything. Thanks!

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

Open Floor


I’ve got a PR which promotes __experimentalFetchLinkSuggestions to non-experimental API.
It will now be fetchLinkSuggestions. As this 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. has been around in experimental form for a number of years, renaming it could cause regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in 3rd party Plugins. Therefore, I want to raise awareness of the change well in advance

As a general rule ‘__experimental*’ APIs are undocumented, not maintained, can change at any time and are not backwards compatible.
@fabiankaegy commented: “In an ideal world I would love it if the __experimental API’s need to be stabilized before shipping in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..”
@get_dave noted: “We have a lot of experimental stuff now. Needs to be whittled down.”

Side note: Discussion on how to approach reducing experimental and unstable APIs on the Gutenberg development has started on GitHub


“We are running Core Editor bug scrubs on Tuesdays at 14 UTC. This was started recently to prepare for the 6.0 release. What does everyone think about making this a standard thing moving forward, even after the release? We have thousands of issues and having a dedicated time each week to start wading through them as a team, I think, would be beneficial. Just trying to get some initial feedback on this idea.”

This was received with excitement. Nick will conceptualize it and prepare a Make Core post for public comment and to raise awareness.


“I just wanted to take the opportunity to celebrate @Tomasz has become part of the Gutenberg contributor team. It’s always great to see new folks joining our efforts!”


I wanted to mention this report about the Site Editor “freezing” for some users. It needs more testing and a way, we can constantly reproduce the problem.


“A while ago I shared some questions about contributing to core  Search 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. extensibility and shared the first proposal and PR (with some questions) that adds the ability to extend the search block with custom query vars.  Would love some feedback there to the proposed take.”

Props to @paaljoachim for his review 👏

Read the complete transcript

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