This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, August 11 2022, 04:00 PM GMT+1 in Slack. Moderated by @paaljoachim.
Gutenberg 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/ plugin 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.9 RC1 was released 11 August.
Thank you for @oandregal for handling the release.
This includes the following enhancements:
- Style engine: Prettify combined selectors. (#43003)
- Style engine: Prettify output. (#42909)
- Style engine: Rename a global function. (#42719)
- Shortcuts: Add Ctrl+Y for redo on Windows. (#42627)
Gutenberg 13.9 RC2 was released. This includes:
Gutenberg 13.8.2 patch 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. was released to fix the following:
- Paste from Slack: interpret paragraph markup (#43114)
- Quote: fix raw transform handler (#43093)
Key project updates
Key project updates:
Announcements, questions and discussions.
Some points that need to be added in the roadmap IMHO, because those are systematic needs:
- About the Query Loop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. Block 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., i do not see the basic need “exclude current post from results” in the Query Loop Improvement V2 List.
- The Query Loop block should also be extended to become the Gutenberg Swiss knife, like the Clickly Query Builder, to cover more usages and add flexibility during content creation (also with WooCommerce). Otherwise we will enter in a tunnel to fine tune blocks by iteration, release after release… i can see some works are done in such area, but perhaps you can be more ambitious!
- About navigation, there is no sticky option on the roadmap ? another highly needed feature, for anyone building some websites with WP (yes there are third part plugins but this is needed by more than 80% of websites).
- Another “quick win feature” (i.e an every day project need) is Add a current-menu-ancestor class to navigation items (PR waiting for merge), but there were some discussions recently around this (cannot find the global related isuse) and @get_dave is following these. It is already in the roadmap but as normal priority. Should a nice addition to the 6.1 release (it is also a systematic need).
Replies from @ntsekouras and @paaljoachim
- “Exclude current post from results” has been added to the overview issue.
- [Block Library – Query Loop]: Try filters with ToolsPanel has been merged. A feature request issue would be helpful to create for additional suggestions on how to improve this feature.
- Sticky option for the Navigation block has been added to this issue: Fixed Position Header and Footer Template Parts. (Title does not mention Sticky for the Navigation block. Making it more difficult to find.)
- No feedback.
Birgit shared this post.
Kick-off WordPress 6.1 release docs.
11 August Hallway Hangout: Editor Tech Lead role 101 was held. A video recording is available in the Hallway Hangout post.
@mamaduka and I have been running the weekly Editor Bug Scrubs for a few weeks and have run into countless old issues that are actually no longer issues in Gutenberg and/or Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. I am thinking about a concerted “marketing” effort to encourage the broader community to review any old Gutenberg issues that they may have created and check if they are still relevant. Sort of a “community cleanup” effort ahead of 6.1. Obviously not looking for a decision here, but just general thoughts if anyone has any. Wasn’t sure if something like this was tried before?
Reply from @paaljoachim
That sounds like a very good idea Nick!
Perhaps a make core post could be created as it would give additional focus on cleaning up the old issues.
To get more details go directly to the Open Floor discussions in the Core Editor Slack channel.