This post summarizes the weekly editor chat meeting on Wednesday, 16 June 2021, 14:00 UTC held in Slack.
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/ 10.8 release.
The first topic was the Gutenberg 10.8 release. The release was already shipped a week before the chat https://make.wordpress.org/core/2021/06/10/whats-new-in-gutenberg-10-8-9-june/.
@jorgefilipecosta referred the main features of the 10.8 release (more 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. design tools and template editor enhancements) and added the Gutenberg 10.9 RC One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). was going to be released soon.
@mamaduka will handle the 10.9 release, with @get_dave in the “shadow” and @youknowriad coordinating. Thank you all!
Monthly Plan and key project updates.
- Reusable blocks rendering and converting to normal blocks.
- RN upgrade to 0.64.x – Merge is very close
- In progress
- Gallery Block Refactor – Almost done
- Editor Onboarding
- Global Style Support – Colors
- Adding search to the block inserter
- Embed block
- iOS The operating system used on iPhones and iPads. share extension
The navigation block is still on deck and is getting home link improvements, invalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. item flagging, and hopefully soon separate overlay colors. The big nav markup also remains on the to-do list.
- Exploring methods to provide a better way to disable/enable nav block features for the nav editor. Watch for incoming Issue on this soon!
- Exploring creation of a reordering endpoint extension for the Menus API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. endpoint.
- Looking into converting the persistence to utilise the REST bulk API.
Feel free to join to chat for this feature over at #feature-navigation-block-editor.
Block based Widget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Editor
The bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixing work is in progress, every week a big set of issues is solved.
This week’s highlights:
- Needs discussion/opinions/Review: Working on allowing more than 1 block-styles per-block (#32510). Will help with blocks that need to load styles from other blocks (example: comment-form loads button styles) and will also allow 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 & theme-authors to style individual blocks more efficiently.
- Needs review: Allow decimals in spacing controls when using units like
rem etc – #32692
- Merged: Did for
theme.css the same we did for
style.css a few months ago to increase performance and load styles when a block gets rendered on the front (#31239)
- Merged: Fixed a performance issue with the latest-posts block when there are many users in the database (#32620)
- Backported commits from Gutenberg to wp-core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
- Lots of PR reviews
Next week: Continue working on performance improvements, styles & scripts loading, PR reviews, and any bugs that come my way
- Finally merged the addition of rich previews when previewing external URLs in the link UI User interface (rich text only at the moment). https://github.com/WordPress/gutenberg/pull/31464
- Helping out with Widgets screen bug fixes.
- Continued to beaver away on the Navigatoin Editor foundational issues.
Is focusing on fixing Reusable block features.
At the moment focusing on adding a lock to the toolbar. A PR has been created here that could use some feedback: https://github.com/WordPress/gutenberg/pull/32710.
- Fixed “cover block exists” check for Image Block.
- Worked on logic to hide settings from the “Options” menu in Widget editor on small screens.
- Helping with new Widget Screen issues.
- Helping with PR reviews.
During the last week the main focus was the theme.json/global styles changes. For the next week: will help ship the theme.json dev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.; Review PR’s that are pending review; Fix some bugs where he was pinged, and plans on restarting the work to advance the global styles UI. Will also help to ship the new enhancements to our locking API.
Is focused on advancing the text based tasks around the widgets project (docs, dev note etc).
Transforms vs convert API
@get_dave brought the following topic:
I’ve followed up on the `transform` vs `convert` API discussion with x2 options/suggestions for how we could come to a decision.
It’s not a huge problem, but it would be nice to see us unify around a single API for this action. Indeed `convert` has been “experimental” for over 2 years.
I believe this needs guidance from the Core team.
Adding that there are two options:
transform in favour of
- Augment the argument signature of
transform and ditch
On the issue @talldanwp referred that he is in favor of deprecating transform in favor of convert. During the chat and then in a comment in the issue @youknowriad said @talldanwp thoughts sound reasonable.
Dot in the Publish/Update button
What happened to the dot in the Publish/Update button?
It’s still there when I edit a reusable block. https://sneak-peek.me/2021/06/16/what-does-the-dot-next-to-update-mean/
@jorgefilipecosta said the best path forward would be to have an issue where this issue could be discussed. @paaljoachim created the issue.
Click through vs lock for some blocks
I think we need a way to figure out if a block should have a click through or/and also a lock. Reusable block could really use a lock similar to the edit button in WP 5.6.
I worry that a lock icon and toolbar action will not be an obvious affordance for editing the contents, or help indicate why this block is any different from the surrounding blocks which you can click and edit. I think some of Jays designs from the previous ticket Created for both bug reports and feature development on the bug tracker. have potential.
This is a UX User experience decision and the discussion will continue on the issues and related PR’s.