This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was held in the #core-editor 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/. channel on Wednesday, Mar. 3, 2021, 9:00 AM EDT and was facilitated by @andraganescu.

WordPress 5.7 Upcoming Release 

WordPress 5.7 RC 2  is now available for testing.  If you are a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party author and/or a theme developer test your plugins and themes against WordPress 5.7 and update the Tested up to version in the readme file to 5.7. There will likely be a 5.7 RC3 later this week.

The WordPress 5.7 Field Guide is out! It contains a full breakdown of everything you need to know about WordPress 5.7.

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/ Version 10.1

Gutenberg 10.1 has been released! This release includes a number of nice enhancements and as usual many bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes. In addition Full Site Editing, Widgets and Navigation screens and Global Styles saw many improvements.I believe the many recent improvements to the different user flows related to Reusable blocks should be highlighted.

The most recent one is the enhanced creation flow, that also allows you to cancel the action. We now have better clarity on the Image toolbar and more blocks are going to follow. 🙂 Finally we now have spacing options for Social Links and Buttons that will help users achieve more elegant designs effortlessly.

Kudos to all for your help and contributions!

Monthly Priorities

March monthly plan will be released soon.

• FSE – there is a focus on making the theme/template creation process more WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page..  Infrastructure and UI milestone progressed with Persistent List View and previews in the browsing sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. Almost all of the Semantic Template Parts tasks from the milestone have been completed. 
• New 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. based editors – the widgets editor now has  a preview of block support in the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. while the navigation editor is quickly iterating on the UIUI User interface update it got recently. Help is always welcome in any shape to help with the long list of queued up issues.
• Mobile apps – started global style support, work progressed on reusable blocks, Removing ability to switch to the Classic editor switch, dual-licensing Gutenberg, search block, adding search to the block inserter, embed block

Task Coordination

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

@annezazu

• Amplifying the second FSE call for testing (working with marketing, reaching out to a few communities, etc)
• Responding to the second FSE call for testing and filing issues. Thanks to all who have left feedback!
• Some triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. mainly around older issues and testing FSE everyday.
• Helped draft the proposal for dropping IE11 support.
• Working on a Make CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. post about the role of the Gutenberg plugin.
• Working on a Core Editor Improvement post about performance enhancements.

@aristath

• This week I focused mostly on a hybrid-themes proof of concept to allow the use of both php templates and user-created templates: PR 29298This can allow users to manually create templates on any theme (even non-FSE themes) so they can have a regular theme, and create a completely custom frontpage. It would be great to have something like that in the FSE 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, but the interaction part is still a bit unclear and it would need lots of feedback as to how some things can happen. The PR however shows that it’s definitely possible to have both 
• For next week I plan to start tackling some of the items listed in Issue 22724 so we can get the FSE MVP across the finish line on time for 5.8

@paaljoachim

• Made an issue to consolidate setup instructions for core and Gutenberg. Issue 29448
• Added a video showing how to test a PR by downloading a special Gutenberg plugin. Issue comment
• Triage and testing.

@joen

• Still working on navigation block adjacent tasks, and would love eyes on this CSSCSS Cascading Style Sheets. refactor: PR 29465
• Also took a stab at a frustrating embed issue that’s in the 5.7 must have categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.. The PR works, but it needs a developer to bring it home: PR 29510

@itsjonq

• Updates for the new Component System project: Integration is moving along. @sarayourfriend (she/her) and I (mostly Sara ) are continuing to move the new components into Gutenberg. We’re at around 23% integrated.
• The main working issue is here:
• The simple status page for this project is here.

@ntsekouras

• Query Title block spinoff PR from my original one, that handles Archive Title for now as block variation(PR 29428)
• Some fixes for Site Logo and Query blocks

Open Floor

@annezazu asked, and got some good support, if we could use a nudge in a dashboard widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. to get more user testing of upcoming features.

Some concern about the size and novelty of FSE was expressed and also an idea to split existing documentation in byte sized versions.

@Zeb brought up his PR that fixes a bug with the Table of Contents block, asking for some review help.

@itsjonq created an issue for the RTL bug thay affects the current WordPress 5.7 RC 2, mentioned earlier in the meeting by @swissspidy.

In the Gutenberg repository the branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". master is now renamed to trunk. The post describing the change is here and you can find the details on how to update your local on the repository’s home.