Editor chat summary: 27 March 2019

This post summarizes for the weekly editor chat meeting on Wednesday, 27th March 2019, 14:00 GMT.


Block Registration RFC

Block Registration is a central API in Gutenberg, so if you haven’t yet read this Request For Comments, please chime-in, discuss, and share your thoughts.

A proposal to open the Gutenberg repository for more RFCs to encourage more discussion of APIs, big technical issues, and also serve as a skeleton for documentation surrounding decisions being made.

Expect a post about this new module in the upcoming weeks.

Highlights

Our current roadmap priorities include:

  • The section block PR is open for feedback and close to merge.
  • Widgets 2 Block API as well as enhancements to the legacy widget block are being worked on. A preliminary bootstrapping the UI of the new page can be found here.
  • Layout blocks including improvements to the Media & Text block and improvements to the Columns block. Possible enhancements include resizing columns including a setup state to bootstrap some column layouts.

Task Coordination

  • @getdave @mapk @kjellr are wrapping up the section block.
  • @youknowriad and @aduth are working on the Widget Screen Bootstrap and block-editor follow-ups.
  • @jorgefilipecosta is working on iterations for the legacy widget block
  • @marek and @mapk are working on iterations for the Media & Text block
  • @marek @mapk and @aduth are interested in exploring enhancements to the Columns block
  • @nerrad is working on the effects 2 block refactoring
  • @nosolosw is starting to look at Drag & Drop support for the gallery block
  • @getdave is working on the InnerBlock’s block appenders
  • @gziolo is working on the block registration RFC explorations
  • @gziolo and @aduth are interested in working on some a11y fixes

Note: Anyone reading this summary outside of the meeting, please drop a comment if you can/want to help with something.

Open floor

  • @notnownikki has written an e2e test to cover a bug in core, and asks for help. Tests need to be written so it does not break other code, eg things like autop breaking if filter priorities are changed around.
  • @nerrad would like to have a basic template for RFC’s to follow.
  • @matias recommends an overview of areas that could use proposals
  • @mppfeiffer proposes a new block, the “logos” block. The “logos” block is a list of logos that can be used to, e.g., display logos of customers, partners, sponsors, etc. and link out to them directly. You can find more details in this related issue.

The agenda for the next meeting is here, please add anything you want to discuss.

#meeting-notes, #core-editor, #editor, #gutenberg