The WordPress core development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
These “Core Editor Improvement…” posts (labeled with the #core-editor-improvementtag) are a series dedicated to highlighting various new features, improvements, and more from Core Editor related projects.
With Gutenberg 12.5 and the soon to be released Gutenberg 12.8, a block theme author can now bundle multiple sets of Styles with their theme, allowing anyone using the theme to quickly switch between them as shortcuts for customization. These different Style presets can change both settings available, like turning on/off font weight, and style options, like the default color palette. For a practical example of what this looks like, check out the quick demo below showing off how a theme could offer both light and dark Style presets:
This Styles feature gets even more exciting when it’s paired with new enhancements like the fonts API in theme.json coming to Gutenberg 12.8. That opens the door for a wide range of styles per theme — look for more and more themes to leverage this in the coming months. The following video shows off some new creative possibilities that are opened up by these new features in combination:
@afragen: Much of feedback has been in form of questions that I’ve done my best to answer. The biggest is will it be possible to add a non-dot org plugin as a dependency. The answer is that it will be up to lead developers. It could be possible by adding a simple filter and leaving the heavy lifting to the plugin developer… essentially need lead developer buy-in.
encourage further comments and testing of both PRs to see how it might look.
@pbiron: I think non-dot-org dependencies are very important use case (e.g., Gravity Forms addons) but also think that it would be fine if they weren’t included in the first version that lands in core
Highlight of message by @sergeybiryukov: I would like to invite anyone interested to test and review the latest PR for creating temporary backups when updating plugins or themes: https://github.com/WordPress/wordpress-develop/pull/2225. I think it’s very close to being ready for commit, and would appreciate more eyes on it and more testing. More on the slack post.
Component Maintainers – if you think you would like to help manage a component, this refresher gives more information. More maintainers are needed.
Props to: @marybaum for the agenda and leading the meeting, to Mary and @audrasjbfor reviewing the notes; and to @webcommsat for the summary of the meeting. Could you help with next week’s notes? Contact team reps @audrasjb and @marybaum
“What’s new in Gutenberg…” posts (labeled with the #gutenberg-newtag) are posted following every Gutenberg release on a biweekly basis, discovering new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project.
We are editing a template, either on site editor or post editor.
The inserter is at the root level.
The content being inserted is between other blocks (neither as the first block nor as the last one).
The template part (e.g. Header / Footer / Sidebar) creation flow will now also show patterns, making it easier to create more advanced compositions than adding blocks one by one.
Work will continue improving the logic that decides to show a pattern or a block, so feel free to share your feedback in the Gutenberg repository!
Allow themes to highlight Patterns
Themes can now highlight specific patterns to their users!
Also, when you click on a block in the editor, the List View will expand to show the selected block for better visibility of the selection’s context within the block tree.
Changes to frontend HTML when using layouts and image blocks
In order to add consistency to the block editor, we are removing some wrappers divs that were generated on the editor in order to add alignment to some blocks.
Keep in note that this div cleaning can affect themes that support layout and many blocks that have this alignment support. Many contributors helped with testing, but theme developers are encouraged to check their themes and leave any feedback they may encounter.
Other notable highlights
Gutenberg 12.7 provides a few other iterative enhancements worth highlighting.
To avoid backward compatibility issues reported in WordPress 5.9, the automatic anchor generation for headings introduced in Gutengerg 11.8 is now opt-in. To enable this feature, simply add:
Recognizing and celebrating contributors, both and new, becomes more efficient and effective! A contributor props list has been automated when creating the release and added to the changelog! Any user who merges a PR during a Gutenberg release cycle will be aknowledged.
The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.
Post Editor
Version
Time to first block
Keypress event
Gutenberg 12.7
5.0 s
41 ms
Gutenberg 12.6
5.1 s
40 ms
WordPress 5.9
5.2 s
40 ms
Site Editor
Version
Time to first block
Keypress event
Gutenberg 12.7
4.7 s
30 ms
Gutenberg 12.6
5.2 s
29 ms
WordPress 5.9
5.2 s
29 ms
Kudos to all the contributors that helped with the release! 👏
Latest Gutenberg Release is 12.7 RC from last week. The final release for 12.7 is scheduled for today. Huge thank you to Carlos Bravo @cbravobernal for leading this release.
We used to exchange key project updates synchronously during the chat. However, many of the key Gutenberg projects sustain a regular cadence of updates on their tracking issues on Github.
This week we tried async updates. The attendees are encouraged to read the latest updates directly from the following tracking issues at everyone’s leisure:
@talldanwpwrote: “I just wanted to provide an update and raise awareness of a project I’m undertaking to make each of our editors implement preferences in a consistent way. Here’s the tracking issue –. Migrate editor preferences to new package Last week I merged a PR that added a new `wordpress/preferences` package, and this week I’m going through each of our editors migrating them to use this new package. Let me know if you have any feedback or spot any bugs. Thanks!”
* Site Editor export archive now includes theme.json file. * Looking for a code sanity check on Site Editor server-side redirection PR. * Currently working on Block Locking UI and hope to share some early results this week.
NOTE: The initial plugin release, 1.0.0-beta.1, will take place on Monday, March 7, 2022 at 07:00 PM UTC. We will hold a release party chat in the #performanceSlack channel at that time and all are welcome! See the Infrastructure section below for more details on the release.
Want to reassess the interest for this as a focus group
Please re-vote on the focus group spreadsheet here by adding/removing your WP.org username from the groups that you want to work on in Column D, Contributors wordpress.org username
Please only enter your name on two or fewer groups. If you’ve already voted and want to revise, remove your name from other areas.
We’ll reassess focus groups based on updated votes next week
@flixos90: The critical WebP module changes have now been merged and only a few PRs left to merge in the milestone so proposing that we publish our first release 1.0.0-beta.1 next Monday 7 March, including:
Images – WebP Uploads
Site Health – Audit Enqueued Assets, WebP Support
Object Cache – Persistent Object Cache Health Check
@flixos90: Had a conversation with @spacedmonkey about if we should have a rule that two people have to approve all PRs. Been assuming that we should be aiming for two people approving each PR, though not a hard and fast rule. Open to thoughts.
@gagan0123: Two pair of eyes are always better than one; speed impact is minimal but quality of code is significantly better
@spacedmonkey: If we can enforce this on GitHub, let’s go for it (with no self-reviews)
WordPress 5.9.1 was released yesterday. This maintenance release features 82 bug fixes in both Core and the block editor.
Async key project updates
We used to exchange key project updates synchronously during the chat. However, many of the key Gutenberg projects sustain a regular cadence of updates on their tracking issues on Github.
This week we tried async updates. The attendees are encouraged to read the latest updates directly from the following tracking issues at everyone’s leisure:
Highlighted: Move post/page title to the top bar as a good issue that will help a lot of users on various levels. @vdwijngaert Koen worked on it but has not had the time to followup on it.
Is working on various issues that he gives design feedback to.
There are a lot of people who work on custom themes who are struggling with some of the style and markup changes in 5.9 and don’t understand the roadmap for the future-compatible theme customization.I’m working on a proposal for one way to handle this that should be out later this week, but I want to just get it onto folks’ radar ASAP. In many ways, I don’t think there has to be a huge change in direction, but some new standards and an adjusted block approach to settings could go a really long way in supporting custom themes.
and later also added this follow up:
@luehrsen added to the above that any feedback on the discussion above would be very appreciated.
You must be logged in to post a comment.