Editor Chat Summary: 9th March 2022

This post summarises the weekly editor chat meeting (agenda here) held on 2022-01-19 14:00 UTC in Slack. Moderated by @get_dave.

Status Updates

• The RC for Gutenberg 12.8 was released – thanks to @priethor for leading this one.
• We’re just over a month away from the Beta 1 for WordPress 6.0.
• Key project updates:
  • Navigation block
  • Comments loop block
  • Site editor
  • Patterns
  • Styling
  • Mobile Team
  • Components Team

Task Coordination

The following items were shared by folks to update us on what work is in progress or where help is needed:

@zieladam:

• I keep expanding the Create your First App with Gutenberg Data tutorial, three parts are already shipped and the part 4 is in a draft stage
• Shipped useEntityRecord and useEntityRecords convenience hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same., recently I also proposed a convenience-oriented set of throwing actions for creating, deleting, and updating entity records
• Also, I merged TypeScript definitions for entity records and I keep working on TS signatures for core-data selectors such as getEntityRecord
• Added resolution error handling to @wordpress/data  – surprisingly, it was missing
• I also encourage everyone to participate in two discussions about an API error handling policy and multi-entity permissions control

@mamaduka – I’m working on Block Locking UI and PR is ready for review/testing.

@get_dave – I’ve been working on both refactoring the Nav blockBlock 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 improving the its UIUI User interface feedback when importing classic menus and creating empty menus.

@paaljoachim:

• I went through the call for testing: https://make.wordpress.org/test/2022/02/23/fse-program-testing-call-12-hyping-headers/
• Made a new issue for the Site Editor in relation to adding the ability to sort by template name, latest update, type etc. https://github.com/WordPress/gutenberg/issues/39307
• Added feedback to block locking UI: https://github.com/WordPress/gutenberg/pull/39183#issuecomment-1062833856 Look forward to having a lock mechanism for Reusable blocks.

@zebulan:

• Table of Contents block PR needs just one approving review so it can be merged.
• Some bugs were found since the last time it was brought up in a meeting, but those are now fixed.
• There does remain one quirk, as described in the latest comment, but I don’t think it’s a blockerblocker A bug which is so severe that it blocks a release..
• Really wanting to get this one merged in time for GutenbergGutenberg 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/ 12.8.

@scruffian – I’ve been working on Theme Export in Gutenberg.

@alexstine has an important a11y PR up which finds the most appropriate focus target in non-contenteditable blocks. More reviews encouraged.

Open Floor

The full Open Floor discussion is available on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Using useEntityRecord in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks

• @cbravobernal asked when it would be suitable to include the new useEntityRecord hook in Core blocks?
• @get_dave @gziolo and @zieladam all suggested using in one or two blocks as a testing ground before rolling out further.

New contributor – @mehedi890

• @mehedi890 said he’d like to contribute core team.
• @get_dave suggested the Good First Issue/Review labels as a good place to start.
• @paaljoachim left a good thread of specific suggestions for where to start.

Request for Core team input on Standardized Design Tokens and CSSCSS Cascading Style Sheets. proposal

• @cbirdsong asked whether there is an update from the Gutenberg Core team on Proposal: Standardized block markup, theme.json design tokens, and CSS classes to improve interoperability.
• This PR has being getting a lot of community interest and summarises a number of previous threads and Issues which discuss similar topics.
• @gziolo noted the relationship to an ongoing project which is trying to improve how the block styles are handled.
• @get_dave promised to follow up with other Core team members to check when we can expect a response.
• @matveb, @youknowriad and others have since responded.
• @glendaviesnz has suggested some next steps.

Feedback request: editing Navigation menus in isolation from the Nav block

• @get_dave highlighted two interesting PRs happening on the Navigation Menus system to allow menus to be manipulated in isolation from the Navigation block:
  • Dedicated Navigation sidebar.
  • POC Isolated Navigation focus mode.
• Contributors would really appreciate testing and/or feedback on these PRs as they address one of the major points of feedback we received from WP 5.9.
• Feedback can be technical or design/UXUX User experience. No prior experience required.
• Never tested a Gutenberg PR before? Just follow this guide.

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