Editor Chat Summary: 22nd April, 2020

This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was 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 15, 2020,14:00 UTCand was moderated by @paaljoachim.

WordPress 5.4.1 Upcoming Release

Note: There was a miscommunication around this release and these notes originally expected the launch to happen the same day as the meeting. This has been corrected.

@jorgefilipecosta shared a comment prior to the meeting detailing the plan for 5.4.1 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).. All 5 PR’s to include were in 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/ 7.9, meaning they were tested in at least one 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 release. This RC release is slated for Friday with the full release planned for next Wednesday per an update from @whyisjake.

Weekly Priorities

No discussion on weekly or monthly priorities

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.


  • Needs reviews for a Table of Contents PR. Ideally would like a G2-style 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. icon, but can merge with the current dashicon.
  • Needs technical and design feedback on a PR to update the heading level control in the Heading block.
  • Needs reviews for Two Reusable Block PRs with 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. fixes.
  • Needs reviews for a Custom HTML Block PR.
  • Needs reviews for 3 quick PRs: polishing black wrapper, new icon for navigation block, and matching SmugMug URL regex to core.
  • Stuck on a List Block Color Controls PR after running into a problem around priority with styles between the default editor and the block. 
  • Ran into an issue with a Navigation Links PR where focus doesn’t move to the previous navigation link after removing the block. 


  • Has been working on the ability to create a Navigation block from existing WP Menus. @karmatosed posted a new design route that we need feedback on if people have time to review.  


Open floor

Should we keep CONTRIBUTORS.md? Raised by @soean.

Only 140 people are listed, but we have more than 550 code contributors, so it is not up-to-date. We don’t use this file in other repos. A 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/ -> WordPress connection is now built in on wp.org.

Discussion ticket started by @mkaz:

  • We don’t use this kind of file in other WordPress repos. 
  • The file overall is a bit confusing and it doesn’t seem to be a great way to acknowledge all contributors currently. 
  • There are inconsistencies in who is added with some long term contributors missing.
  • The file itself seems to be for highlighting non code contributors to the project.
  • The contributors tracking that GitHub provides only shows contributors for specific timeframes. 
  • @soean shared this neat project https://allcontributors.org/ that might be interesting to explore.

Next Steps: @mkaz will update the file to provide a link to the code contributors listed on GitHub, followed by the list of non-code contributors. If people have other thoughts, please add to the ticket to discuss. 

Is using `render_callback` a good solution for handling conditionally loading assets? Raised by @mkaz.

This question is based on a long standing but stalled out ticket trying to address this within Gutenberg automatically. @mkaz wrote a post examining `render_callback` but this approach  requires each plugin/block to set it up. If this is determined to be a best practice to move forward on, we should likely update documentation to encourage developers to take a similar approach. 

Next Step: We didn’t have enough folks online to have a robust discussion about this so @mkaz will create a discussion ticketticket Created for both bug reports and feature development on the bug tracker. to carry the conversation forward. 

Problems with the Drag & Drop Experience explored in this ticket. Raised by @jules-colle.

There are general concerns around how the current experience is continuing negative perceptions of Gutenberg for end users. Right now the problems are adding up leading to both a rough experience and an overwhelming set of problems. Right now, it seems the issues would benefit from being broken down into smaller pieces.  

Next Step: Thoughts are welcome on this main ticket.

Should we give more folks access to @here abilities in slack?

At the beginning of the meeting, we realized no one had permissions to @here in slack to alert folks to the meeting. This led to a quieter meeting this time around but we likely should expand access to those who run meetings so we can ensure better meeting engagement.

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