Core editor chat summary 4th December, 2019

This post summarizes the weekly editor chat meeting agenda here. Held on Wednesday, 4th December 2019 held in Slack. Moderated by @ellatrix.

Full Site Editing and themes

The idea here is to recap what’s being worked on, what has been discussed in #themereview yesterday’s meeting and provide some space for feedback and discussions about the next steps.
Must Read:
– Summary for yesterday’s #themereview meeting
– Documentation for the current state of Block-based themes

The main takeaways/action items for me are:
– Let’s have theme authors experiment with these in Github/personal themes and provide feedback: Gather a list of Missing blocks?
– Potentially help build a demo theme in Gutenberg in this folder
– From the editor side, continue on the current PRs/work

Sounds good to me, in addition we will also be doing more to get stuck in and help you all out with comments, PRs and testing as we all make time for it in the coming weeks.

If I’m a theme author and read these incredibly helpful links and have some questions or comments, where should I put them?

I think at the moment (only during experiment phase), it should be fine to ask here and raise Github issues for bugs. We should also take these as opportunities to document things as we move forward from both themers and devs.

Weekly Priorities

I’d like to share the new priorities post for December in case you missed it
An emphasize on Block content areas / Full site editing and also a push for Block Patterns APIs and usage across blocks and inserter in addition to a few tightening up items.

Task Coordination

I’ve been focusing more on framework-y stuff:
– Get types checking in place
– A never-ending crusade to stabilize Travis build
Hoping in the next week to revisit some feature work:
– Better _fields handling in wordpress/apiFetch and/or wordpress/data
– Revisit spoken messages in Notice pull request
– Also been fixing up a few theme interoperability issues, notably around background colors for custom editor styles:

I’m somewhat looking at deprecating the wordpress/nux package but mostly reviewing PRs this week.

I’ve been working on “Lighter block DOM: detached controls in popovers”, improvements on Popover, multi block selection, and paste on multi block selection.

I’ve been working on…
…a PR to allow parent blocks to capture the Block toolbars of all child blocks which is just waiting on a thumbs up from @jorgefilipecosta:
…adding justification tools to the Navigation Block:

Past week:
– Reviewed some media-related PR’s, namely the refactor to the gallery, to increase reusability with the native mobile APP.
– Helped the enhancements to useColors and merged the PR that uses the hook in the paragraph.
– Finish the remove editor module usages in block-editor by applying changes to the reusable blocks, rich-text, and native inserter. Some PR’s are waiting for a review.
– Updated the release tool to move readme and changelog files to the Github repository.
– Submitted several bug fixes.
– Continued the interactions/enhancements on the PR’s I have open e.g.: custom gradients.
Next week:
– Increase my involvement with the FSE work (by reviewing PR’s and working on a subtask — Suggestions for a possible subtask are welcome 🙂 ).
– Continue giving my support to some media-related PR’s by reviewing and testing them, and maybe submit follow up enhancements.
– Rebase Update the buttons block PR and try to unblock the PR.
– Address reviews Add a mechanism to set a width on withViewportMatch
– Fix some widget related issues.

I’ve mostly trying to make sure everyone is not blocked and also worked on some PR’s related to the block toolbar/UI (fixed toolbar, select/edit modes…) and some code quality refactorings.

I have a PR for adding background color support to the Columns block:

I have a small docs PR that explains how to work with the changes to serverSideRender location:

Last week:
– Worked on fixes for regression introduced in the block toolbar.
– Refactoring towards using the new accessible version of Toolbar component.
– Core patch to simplify the process of updating Gutenberg packages after every plugin release.
Next week:
– Resume work on Patterns API once we decide which blocks should be integrated (Table?, Cover?).
– Resume work on block.json transformation on the client side to allow automatic handling of translations.

Open Floor

Resume work on Patterns API once we decide which blocks should be integrated (Table?, Cover?)
We have Columns block integrate, we use some sort of setup step for Table block, should we integrate it with Patterns API as well?
The challenge is that it needs to allow the custom creator as well.

We tried Media & Text but we abandoned this idea
Information here:

There was additional conversations about patterns and transforms during the open floor: