Editor chat Summary: 29 January, 2020

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 29th January 2020 held in Slack. Moderated by @youknowriad.

Weekly Priorities

We are getting closer to the WordPress 5.4 beta releases.
Release dates:
11 February 2020 – Beta 1 – Deadline for new features (after this date, only bug 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 release that was included in WordPress 5.3).

Gutenberg 7.4 on Feb 5 (RC 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’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 variations. It is nice to have for 5.4.
I believe that Social Icons is still not exposed for WordPress core 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 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:

Task Coordination

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.

Still working on the Dashicons and gathering all icons under the same package. Wrote some blog 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.

Last week:
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.
Next week:
Audit experimental APIs. Stabilize some API’s I proposed.
Audit dev notes 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.
PR reviews.

I am working on adding features to the author block.
https://github.com/WordPress/gutenberg/issues/19696 and

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 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. 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

Open Floor

@SvenWeber asked about this issue: https://github.com/WordPress/gutenberg/issues/19898
@aduth added a comment to the issue.

@Munirkamal asked:
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. 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/themes later today.