Editor chat summary: 7 April, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on 2021-04-7 14:00 UTC in Slack. Moderated by @annezazu.


Monthly Priorities & Key Project Updates

Full Site Editing from @youknowriad

  • Making the margins the same between frontend and backend (no opinionated margins provided by 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. editor by default).
  • Working on adding a way to use block templates in classic themes as well which should provide a nice transition point.

Global Styles from @nosolosw


  • Block Supports: added a gutenberg_block_has_support helper function and support for padding in dynamic blocks 30322, border for search block #30227.
  • Fixes: title in the save panel of the site editor 30521, fix for themes without 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. support but with experimental link color support 30452.


  • Block supports: border for button block #30194, add border color/style/width properties #30124, spacing #30333 #30371.
  • Theme.json: Update format #29891, there’s now a draft PR at #30541, conversation about whether and how to expand the use of CSSCSS Cascading Style Sheets. Custom Properties #29714

Navigation Block from @mkaz and @andraganescu

Updates and improvements keep chugging along! The dependency on responsive nav will likely get merged today, and then the responsive PR can move forward. A new update attempts to fix the HTML produced by the block. This is blocked by the lack of advancement in the discussions opened by @talldanwp (Issue30007 and Issue30006). Any help moving those points forward would be greatly appreciated! Plenty of other refinements and updates continue too, for example the placeholder state was updated. The best way to follow along is by labels in 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/ PRs or this tracking issue.

Navigation Editor from @andraganescu

The Block based Navigation editor is advancing with a host of PRs aimed at polishing various functionality (PR30374PR30403PR30524 PR30340) and some that could use a review and testing (PR30446PR30440PR30349).

WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor from @andraganescu

Block based Widget Editor work is focused on tidying up blocks in customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. for better accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) and various bugs.

Mobile Gutenberg from @mattchowning


  • Block transforms
  • Removing ability to switch to the Classic editor when editing a post
  • Significantly the number of blocks that are tested on native by CI on each PR (relevant PR)

New In Progress

  • Slash inserter

Still In Progress

  • Dual licensing Gutenberg: planning to merge the PR with interim license this week
  • Global Style Support
  • Reusable blocks
  • Search block
  • Adding search to the block inserter
  • Embed block
  • Simplification of media insertion flow

Task Coordination




  • Still working on the “Most used tags” feature.
  • Fixed “the same key” prop issue for gallery list items.
  • Started doing PR reviews by testing and adding comments. Hopefully, this can help the “Gutenberg CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.” team a little bit.
  • Currently figuring out the best way to filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. PRs for reviews.


  • I’d love feedback on the approach in this PR for 24337, please. If it seems appropriate, I can built it out for the rest of the existing blocks that support the feature, but thinking it’s possible this change should happen higher up somewhere so that blocks don’t have to adjust for it.


  • I’ve mainly focused on the FSE Outreach Program responding to the current call for testing and pausing to get some feedback for how to improve the program.
  • I plan to ship another call for testing shortly after this current one ends alongside a summary post.
  • I want to experiment tomorrow too with holding a friendly, casual zoom call for about 30-45 min to talk through some fun FSE issues/designs/PRs that have caught my attention! Join #fse-outreach-experiment to stay tuned if that’s of interest.


  • I’ve been working on ways to make hybrid themes a reality. Among other things, there’s a PR to allow loading a block-based header & footer in classic themes which should help theme-authors to slowly start transitioning parts of their themes to FSE.
  • Other than that, lots of PR reviews.
  • Next week I will probably keep working on the same things: FSE MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia & hybrid-themes.


  • I’ve been continuing on the Navigation block, polishing and polishing. While it’s in a good place, it’s opening up some grand questions about the next steps, all exciting ones. And I’m excited to delve into patterns for it as soon as I can.

Open Floor

Are there any updates for a home/name for Site Editor Documentation? Raised by @poena.

Carolina brought up a previous post from early February asking whether there was an update around the name and place for documentation as currently it’s causing blockers/confusion for how to proceed. Currently, the documentation in the block editor handbook that’s related to FSE is in several places and pretty difficult to find. At the same time, as interest grows around FSE, people are seeking out more information. For example, one of the concerns that Carolina shared was around how if the documentation is in the theme developer handbook or the block editor handbook, it will be difficult to find and likely not visible enough for when a large number of people are first introduced to FSE. Carolina then passed along a suggestion to have a “front page” with basic explanations of the key concepts that then guides visitors to user or developer docs depending on their interests.

After some back and forth discussion, a loose consensus was reached on the following:

  • The lack of a decision around name and placement shouldn’t stop us from creating docs and organizing them properly when these things get clarified.
  • The go/no go dates should provide clarification this month around what needs to be documented first.
  • An introduction page that can guide people curious about FSE likely needs to be created or at least explored.
  • Exploring renaming the “Block Editor Handbook” to something more general might help alleviate some of these concerns by making the Handbook more flexible to allow for FSE items.

Next steps: @mkaz will kick off a discussion for renaming the handbook and create an issue for an initial intro FSE page to direct people.

#core-editor, #core-editor-summary, #gutenberg