This post summarizes the weekly editor chat meeting agenda. Held on 2020-11-11 14:00 UTC in Slack. Moderated by @paaljoachim.
WordPress 5.6 Upcoming Release
WordPress 5.6 Beta 3 (beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 4 will be released Thursday) is now available with WordPress 5.6 slated for release on 8th December. This software is still in development, so it’s not recommended to run on a production site A production site is a live site online meant to be viewed by your visitors, as opposed to a site that is staged for development or testing..
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/ Version 9.3
Gutenberg 9.3 (Released 4th November)
Main features: Stability work for 5.6 and contributors also focused on improvements to the Full-site editing flows.
5.6 Project Board
The 5.6 Project board for “must haves”.
The November 2020 Monthly Plan
Here is the overarching plan for November 2020.
A lot of focus on preparations for WordPress 5.6, Full Site Editing, the Query 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. and Global Styles.
Key Project Updates.
Updates for key projects such as Global Styles, Widgets screen and Full Site Editing.
For GlobalStyles the current focus is on tightening up things and fixing the flows, specially by testing what we have with the TwentyTwentyOne blocks theme. We’re also in the process of making some things stable, so we can prepare a core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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. early in the 5.7 cycle. Progress can be follow at the (tracking issue) Block Styles Breakdown and also by checking the global styles label.
The Widgets editor work continues, any help picking up issues from Widgets editor project would be greatly appreciated. I would like to also highlight How the new widgets screen works overview issue which will eventually turn into documentation which works as a good intro to the architecture of the new editor.
Gave an update on issues being worked on from the native mobile editor side of things. Fix SASS related regression from the move to (Dart) Sass compiler and a re-port Gallery to use InnerBlocks.
No updates made during the meeting on Full Site Editing.
- Duotone is nearly ready for review
- #26612 fixes a keyboard accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issue and needs review before duotone will be ready
- docs: block supports, some newly added style properties
- extract theme json processor => first step in extracting meaningful pieces for global styles in the server that also fixes a couple of issues
I’ve been working on the Full Height Alignment feature.
Wants to bring extra attention to: Undo / redo (keyboard shortcuts) affecting the whole document rather than the focussed TextControl
Essentially, this is a 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. everyone has pretty much encountered at some point, but probably learnt to live with (or not noticed) but its also prevents future development of doing anything inside modals/popovers. I am looking into it from what I can, but not sure I know the architecture well enough to guide this further.
Since Widgets has been punted to 5.7, does that mean the widgets which have already been converted to blocks are coming out as of 5.6, or are they staying in?
The widgets which have already been converted to blocks will remain as they were released previously.
Confusion around the [ + ] button. It considerably changes the UI User interface with the insert button. It is a nice chance to dive into the code. A request for developers.
@bobbingwide and @aristath
When a discussion continues in a closed issue. One should open a new issue and continue the discussion there.
Raising awareness on some other native mobile editor news:
- Improved media multi-select behaviour on Android PR here
- Using Dependabot to update the Gutenberg git submodule hash in gutenberg-mobile and test it. PRs here and here. This helps with noticing regressions sooner.
- Native editor is cut as we speak in case you want to follow the progress/process. Various smaller fixes included there.
#agenda, #core-editor, #core-editor-summary, #meeting-notes