This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, July 13 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.7 RC1 was released 13 July.
It was quite a bit release with 154 PRs. Great work everyone!
A big thank you to @bph for handling this release!
Key project updates
I’m worked on a PR for added WhatsApp icon to the Social Icon Block.
Announcements, questions and discussions.
I can’t attend the meeting due to timing, but I want to call attention to #40381 which continually gives me headaches.
It appears that a “Classic”/hybrid theme using
theme.json can only define the
blockGap style if it also supports the
blockGap setting. This doesn’t make any sense, because without the style, the editor displays all blocks with no gaps at all when
theme.json is present.
It seems that simply always defining
–wp–style–block-gap when there is a value present in
theme.json would be a pretty easy way to resolve most of this issue.
I wanted to quickly spotlight a few issues from our Editor Weekly Bug Scrubs. Both have seemly valid PRs and need more testing and review. Both are a bit beyond my expertise level, and would love an extra set of eyes. If anyone has some spare time, it would be greatly appreciated.
No visual feedback when Parent Page dropdown is loading.
The block editor does not trigger the interim login modal early enough
I just wanted to raise this issue that @bph created:
GitHub Action for ‘docs:build’ step after documentation changes.
I’ve seen the required build step of the docs add quite a bit of friction to many first time contributors and even experienced folks trying to help with documentation recently and think it would be great if we could come up with a way to make that step happen in CI.
To get more details go directly to the Open Floor discussions in the Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Slack 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.