Editor chat summary: 8 June, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, June 8 2022, 03:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

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

Gutenberg 13.4 was released 8 June.

WordPress 6.0.1

WordPress 6.0.1 project board

Key project updates

Task Coordination

No tasks shared.

Open Floor

Announcements, questions and discussions.

@ndiego

Highlight:
I would love to get some additional eyes on this issue: Backport fixes for wp/v2/block-patterns/patterns and /wp/v2/pattern-directory/patterns endpoints to Gutenberg issue. The related PRs need to be backported to Gutenberg and I am not sure what that process looks like.

Once these are backported, I have a fix for When removing core pattern, allow theme.json pattern slugs to be listed in inserter.

@luehrsen

Question:
I wanted to ask for guidance around this issue: Explore options to add back semantic classnames to block wrappers. Where can we help, what can we do to move this forward? This affects our day to day business, so we are more than happy to help. Especially since 6.0 rolled out features that ignore semantic classnames. (Group Row/Stack)

@torounit

Question:
PR: Migrate list block test to Playwright.
The e2e test passes on GithubGitHub GitHub is a website that offers online implementation of git repositories that can 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/-Actions, but when I run it on my machine some tests fail. ( tests with names starting with should undo asterisk transform with backspace )
This problem does not occur when I run step by step. ( use debug mode. )Adding new Promise( ( resolve ) => setTimeout( resolve, 300 ) ); to the line after createNewPost succeeds, but it doesn’t seem like a good way.
Is there a better way?

Question:
Do we still need wp.blocks in our documentation? PR: Add supports to basic sample code.
@import metadata “. /block.json” I thought it would be easier to understand.

@skorasaurus

Highlight:
I triaged the issue WP 5.9 adds default Duotones before closing the body there are users who feel burned about the decision that was made (to introduce duotones) and load them by default. Several users are still unsure how to dequeue/remove them. This is representative of a broader pattern where Gutenberg is introducing new features or options without the means of disabling them and the need to communicate these decisions more clearly.

We had multiple questions/comments during the Open Floor which still need feedback.

To get more details go directly to the Open Floor discussions in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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.

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