Editor chat summary: 31 March, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, March 31, 2021, 04:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

WordPress 5.7.1

WordPress 5.7.1 maintenance release.
The following release schedule is being proposed:
Release Candidaterelease candidate 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).: Wednesday 7 April, 2021 around 23:00 UTC.
Final release: Wednesday 14 April, 2021 around 23:00 UTC.

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/ 10.3

What’s new in Gutenberg 10.3.

5.8 Pre-planning

5.8 schedule

Monthly Priorities

March monthly priorities. Along with Key Project updates.

Global Style

Update from @nosolosw

• This week’s status report: ongoing work for the major tasks necessary for the MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia.
• Continue to prepare the changes for theme.json.
• How to filter block_editor_settings & global styles settings.
  Conversations about the settings for the different editors and mobile:
• Add a new endpoint that exposes global styles settings through the REST API.
• Editor: Abstract block editor configuration
• Block Editor: Standardize loading default block editor settings
  

Navigation Editor

Update from @grzegorz

• Currently, we are working on rebuilding the process of saving the configs in the navbar:
• make all config from InspectorControl saved on clicking the save button
  With an effort to add indicators that a user has unsaved changes:
• Better handling of unsaved changes 
• Detect unsaved changes, and only enable the save button when there are unsaved changes
  It is still in the concept phase so any kind of feedback would be appreciated.
• indicators, that a menu is being/has been deleted was added
• Submenus have been polished
• Fixes in styles and regressions
  There are some PRs waiting for your feedback/review:
• Fix behavior of snackbars in navigation editor
• Unification MenuSwitcher in UnselectedMenuState and Header

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

Update from @mkaz

• making good progress on improvements and additional features, see tracking issue for full details.
• One call out is the hamburger/responsive navigation is making good progress, it depends on a change to allow JS on the front-end for the first time so defining new methods and process to allow. Any extra eyes and reviews appreciated.
• Plus plenty of refinements abound, see the closed list  for what’s done and there are a handful of open PRs that can use review too.

Mobile

Update from @hypest

• Pretty much the same in-progress items as reported before from the native mobile folks. In addition:
• The draft PR for the interim dual license of future contributions to Gutenberg is up, please have a look!

Full Site Editing

Update from @annezazu

• In relation to FSE Outreach Program.
• The third round of testing finished last week and a summary post was added highlighting various issues found while people created wonderful, custom 404 pages.
• There is another call for testing, building a restaurant themed header that hopefully will be both equally as fun and full of new insights about how to enhance the FSE experience.
• Finally, I want to mention the recent WP Briefing episode with Matías and Josepha talking about FSE: https://wordpress.org/news/2021/03/talking-full-site-editing-with-matias-ventura/ Check it out!

Task Coordination

@annezazu

• Mainly focused on FSE Outreach program (daily fse testing, reporting issues, writing up summaries, writing tests, amplifying!) and a few CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement post ideas in the pipeline.

@aristath

• Focus FSE and getting things ready for our MVP for inclusion in core.
• Past week focused on implementations for hybrid themes, and also adding skip-links to FSE themes.
• Focus on reviewing PRs.

@ntsekouras

• Switch to proper settings tab based on the selection in site editor.
• Please test: Suggest Pattern transformations that are contextual to the currently selected blocks.
• Lot’s of triaging and reviews.

@mamaduka

• Focused on WordPress 5.7.x Must Haves project board.
• Fixed regression with authors Combobox, causing 403 error for non-adminadmin (and super admin) users.
• Made a core ticketticket Created for both bug reports and feature development on the bug tracker. for “Reusable Blocks” admin menu.
• Currently working on “most used tags” feature.

@poena

• Reviews.
• Testing Full Site Editing.
• Reporting issues and creating pull requests toward the FSE MVP.

Open Floor

Discussing the Full Site Editing MVP.
To summarize the discussion that happened during the meeting and after, here are the top takeways:

• There is confusion of what MVP for Full Site Editing consists of.
• As has been previously shared, the MVP should make it possible to build a version of the Twenty Twenty-One theme, using only blocks, without any coding knowledge.
• Widgets & Navigation work are not included in FSE but they are seen as complementary projects to help with adoption.
• At the moment we have two targets: the full site editing MVP & what would be introduced in 5.8.

A link to the full discussion on Slack.

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