Editor chat summary: 19 May, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, May 19, 2021, 04:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

WordPress 5.8

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/ 10.7 is the last 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 version to be included into WordPress 5.8.
Project board.

@youknowriad who is the technical lead for 5.8 gave this reminder on Tuesday on 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/..
“Reminder: It’s feature freeze day (19 May) in Gutenberg, in general that means one of the most stressful days in our release lifecycles. I’ll be milestoning the PRs that I ideally should make it in the 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). with “Gutenberg 10.7″ to ensure we all help review and move these forward. All of these might not make it but that will allow us to know where to prioritize our time for today.”

Gutenberg 10.7 RC

The release candidate of Gutenberg 10.7.0 can be downloaded here.

Gutenberg 10.6

@vdwijngaert  took charge of releasing Gutenberg plugin 10.6! His very first release of the Gutenberg plugin. Koen also wrote the “What’s new in Gutenberg 10.6?” Make coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post.

Widgets editor in WordPress 5.8.

A call for testing of the new widgets editor.

Monthly Priorities

May monthly priorities. Along with Key Project updates.

Global Style

Update from @nosolosw

  • The focus getting tasks ready for Gutenberg 10.7. Most have been landed.
    Will start the merge process in core (got an initial PR for this).
  • Shipped this week. 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. supports: margin, duotone, font-family, layout, typography and link color.
    Settings: REST Request for mobile.
  • Ongoing. Block supports: typography, border, add letter-spacing and migrate more blocks to the hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. system.
    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.. Show both core & theme colors. Link color not to use CSSCSS Cascading Style Sheets. Custom Property. Core merge. Add settings for all editors.
  • Priorities. Merge process for theme.json APIS in core.

Check out the Github comment for additional details.

Block based 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

Update from @andraganescu

  • The widgets block editor has had a good number of fixes and missing features merged for the Gutenberg 10.7 release. Soon a core patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. for the Widget Editor feature will be worked on.

Navigation Block

Update from @joen and @andraganescu.

Full Site Editing


Update from @mattchowning

  • Block picker search almost done, progress on embeds block, ready to ship first iteration of reusable blocks, working hard to finish up ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native upgrade.

Refactored gallery block

Update from @glendaviesnz
Regarding incorporating the new Gallery block into Gutenberg plugin 10.7 and WordPress 5.8.
We are waiting on two things in order to be able to make a decision on this:

  • The mobile/native code needs to be brought into line, and there have been some issues to resolve with this in terms of backwards compatibility with old versions of the app. Hopefully by next week we will have a better understanding of the timelines around getting this work finished.
  • We are exploring options for providing backwards compatibility in terms of plugin /theme support with the move from an unordered list format. Hopefully we can get some decisions on this by next week as well.

Task Coordination



Open Floor

Feedback needed

A comment from @zebulan
Improving the Table of Contents block so it can be re-enabled (it was disabled shortly after merge due to implementation concerns). Following PR needs feedback: ToC block: use static markup and only support core Heading and Page Break blocks.

Adding action hooks into FSE

Question from @bobbingwide
How easy will it be to get some do_action() hooks into FSE template and template part logic, to aid problem determination?
I have started work on backporting the template resolution logic to Core (currently collecting notes at https://core.trac.wordpress.org/ticket/53176). Did you have any specific hooks you wanted added?
Yes. Two new ones which I have currently called rendering_template and ‘rendering_template_part.
Add debug divs to templates with appropriate CSS

Regarding Theme.json

Comment from @bobbingwide
Documentation shows JSON with // comments. People are copy and pasting verbatim and it’s not working. But there’s nothing visual to say theme.json is broken. Just an entry in debug.log
1- Can the documentation be changed?
@nosolosw Added this PR: Make the theme.json examples copy-pasteable. (PR has been merged.)
2- Can the parsing failure be surfaced?
Removing comments from the docs is something we should fix asap. In the future, I expect us to have a semi-official tool for building and validating theme.json files, which would answer the question of parsing failures.

Documentation for block themes

Comment from @daisyo
I have started an issue here to discuss documentation for block themes.
Needs feedback. Discussion: Block Theme Developer Documentation.

Expanding the link control with hooks

Comment from @bula
It would be very beneficial to give developers a hook to extend it.
Is it possible that the link popover could be extended with a block hook?
Link Control: Add more controls.

Regarding failing e2e tests.

Comment from @jffng
Is the recommended process to rebase until the checks pass? Or when is it “safe to merge”?
All tests are halted on new PRs, so rebasing etc won’t make a difference… We’ll need to wait for 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/ to resolve its issues.

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