Editor chat summary: 11 May, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, May 11 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.2 released 11 May.
Whats new in Gutenberg 13.2.

WordPress 6.0

WordPress 6.0 Project board
Project board for Dev Notes
Help Wanted: Test WordPress 6.0

Key project updates

Task Coordination

@amustaque97

I will be looking into issue: Post Comments block: Whitespace on top of warning message

@tomasztunik

A while ago I’ve shared a core Search Block extensibility feature request to give the ability for 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. variations to provide custom search query parameters. Since then I’ve also shared a proposed implementation and I’d love some feedback. This would allow projects like WooCommerce or other projects that introduce custom post types to re-use the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. search experience to provide custom search components for their extensions.But it would also allow creating custom searches for core WordPress experience ie. searching only within specific categories, tags or authors.

Open Floor

Announcements, questions and discussions.

@annezazu

I’d like to start a discussion around adding a new label to the new label to the Gutenberg repo around issues that impact adoption. The aim would be to have an easier way to see, at a glance, what big issues are impacting the adoption of Gutenberg.

  • Would folks find value in having those issues clearly communicated?
  • Does a new 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/ label seem like the right approach? If not, what other approaches would work well?
  • If a new GitHub label works well, what name would work best?

Here are a few suggestions:

  • [Type] Adoption Blockerblocker A bug which is so severe that it blocks a release.
  • [Type] Impacts Adoption

@marybaum
I like Adoption Blocker.
Could also make it active: Blocks Adoption.
@fabiankaegy
I also like the idea of that. Though it is difficult to really gauge the actual impact it has on the party that is blocked from adoption. I guess I’d like to understand what requirements a ticketticket Created for both bug reports and feature development on the bug tracker. needs to fulfill in order to “justify” getting that label applied.
@tomasztunik
I think if people had this at the back of their heads when triaging issues or evaluating feature requests this could shift the perspective toward the product and ecosystem more than the problem itself. Like another “standard” question to ask yourself when evaluating something.
@priethor
This is an example of an issue that would need that label: something already existing in WP but that Gutenberg doesn’t support, preventing Gutenberg adoption and users needing to stick with classic implementations:
https://github.com/WordPress/gutenberg/issues/3144
@mikachan
Another alternative for the label itself could be ‘migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. blocker’ (or ‘impacts migration’ / ‘blocks migration’).

@ndiego

This is a thought-provoking question that I asked earlier in #6-0-release-leads (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/.). When we fix bugs in Gutenberg (and also in Core), they can have unintended consequences when users upgrade to the new versions where the bugs have been fixed. Thought I would share it here as well.

To get more details go directly to the Open Floor discussions in the Core Editor Slack channel.

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