This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 29th January 2020 held in Slack. Moderated by @youknowriad.
We are getting closer to the WordPress 5.4 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. releases.
11 February 2020 – Beta 1 – Deadline for new features (after this date, only 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. fixes for regressions in the release).
18 February 2020 – Beta 2
25 February 2020 – Beta 3
3 March 2020 – RC1
10 March 2020- RC2
17 March 2020 – RC3
24 March 2020 – RC4
31 March 2020 – 5.4 Release day
The main priority is making sure we don’t send an unfixed critical issue on the first WordPress 5.4 beta. To track the issues we have a project board:
We should give particular care to issues raised after 18th of September (date of the last 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/ release that was included in WordPress 5.3).
Gutenberg 7.4 on Feb 5 (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). on Feb 3)
(Exceptional release) Gutenberg 7.5 on Feb 12 (RC on Feb 10)
Both will be included in WP 5.4.
What do you think about the current state of things?
Currently it seems we are on track. Some new features like the custom gradient picker may need some focus to be polished and could benefit from tests/feedback. https://github.com/WordPress/gutenberg/issues/16662 and https://github.com/WordPress/gutenberg/pull/19582
I would also like to request everyone that implemented experimental 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.’s to think if they could be made stable before WordPress 5.4. It would be good to reduce experimental API’s as much as possible.
I will soon add a comment on https://github.com/WordPress/gutenberg/issues/17743 pinging the authors of API’s I think could be stabilised.
We are discussing with @mcsf 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. variations. It is nice to have for 5.4.
I believe that Social Icons is still not exposed for WordPress core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. so we only would include this new API paired with Social Icons block.
I also don’t feel that we can make the accessible toolbar for 5.4 but maybe it’s better to have it enabled together with the block toolbar redesign. In the gist, it’s change in the tabbing behavior where every toolbar is only one tab stop and you can navigate between items with arrow keys, home, end, etc. Super important from 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) standpoint.
We started a draft PR iterating on Social Icons adjust implementation to allow for no-duplication of assets and making extendable, but there are some trade-offs being considered:
I’ve had my head deep in Figma working on global styles. Focusing on the minimum version first. I also have been diving into controls. I also have been working on some iterations to color picker. Along the side there is as always a constant flow of triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors..
Still working on the Dashicons and gathering all icons under the same package. Wrote some blog (versus network, site) posts about Gutenberg Extensibility APIs and Modularity. https://make.wordpress.org/core/2020/01/23/controlling-the-block-editor/
Reviewing, triaging as I can.
I’m hoping to continue on the icons and to circle back to the keyboards shortcuts package work as there’s still some improvements to make to allow third-party shortcuts to show up in the modal.
I started the work on the global styles, proposed the resolver system.
Iterated on the angle picker and merged it.
Triaged issues relevant for WordPress 5.4 & submitted bug fixes.
Audit experimental APIs. Stabilize some API’s I proposed.
Audit dev notes 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. and create an issue summarizing all the dev notes needed.
Continue the work on global styles.
Continue the work on the custom gradient picker.
Continue the WordPress 5.4 preparations by triaging and fixing issues.
I am working on adding features to the author block.
We have some cool image editing tools we’d love to get in at some point, appreciate some feedback and guidance. Issue and details added here, 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 available for testing: https://github.com/WordPress/gutenberg/issues/13748#issuecomment-574903126
Been working a fair bit around the LinkControl component and related implementations (Popovers, etc). I expect to be continuing this in the next week.
Discussing user preferences persistence using meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.. There’s been a lively discussion in https://github.com/WordPress/gutenberg/pull/19177
I’ve also been diving into GlobalStyles (master issue at https://github.com/WordPress/gutenberg/issues/19611) pairing with Jorge and Q. My focus at the moment is accommodating the prototypes shared in the issue into the proper data structures, client side.
Need a tech review at https://github.com/WordPress/gutenberg/pull/14930
Merged create-block package for block scaffolding, still not published to npm until next Wednesday.
Landed Variations API integration with the inserter.
Some more work to improve the workflow for syncing Gutenberg and WP core.
I plan more work on the Variations API and smaller accessibility improvements I started earlier.
I have been focusing on the Block Patterns Variations API with @gziolo and exploring applying that to Social Links: https://github.com/WordPress/gutenberg/pull/19887
Discussing what @epiqueras initially proposed of server-side rendering support for parent attributes context:
Improved the way RichText blocks do or don’t automatically transform content into another block: https://github.com/WordPress/gutenberg/pull/19727
Continue with Global Styles work. Pairing with @karmatosed, @nosolosw, and @jorgefilipecosta for various parts. Also diving deeper into the technical aspects/flow and planning.
Updates to the RangeControl component in wordpress/components at https://github.com/WordPress/gutenberg/pull/19916
Background color support for Columns block has landed: https://github.com/WordPress/gutenberg/pull/17813
Tidied up labels/titles to use sentence case formatting: https://github.com/WordPress/gutenberg/pull/19903 and https://github.com/WordPress/gutenberg/pull/19901
@SvenWeber asked about this issue: https://github.com/WordPress/gutenberg/issues/19898
@aduth added a comment to the issue.
How can I replicate the “Add to Reusable Blocks” functionality on my custom Gutenberg Block which I need to allow users to save to a custom post type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept.. So users will be able to save the block to a defined post type like core add to reusable functionality.
I think he means saving the blocks to a different CPT.
You just need to save a
wp.blocks.serialize( block ) and save as “content” of your CPT.
A brand new recurring meeting in the #themereview channel. It’s dedicated to crafting the future of block-based themes in concert with the full-site editing work happening in Gutenberg. It will be held bi-weekly on Wednesdays @ 16:00 UTC, beginning Feb 5th. Look for an official post about the meeting on make.wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org//themes later today.