Core Editor chat summary: 2nd November 2022

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

Status Updates

• WordPress 6.1 “Misha” was released on the 1st of November.
• @annezazu has published an update on the Phase 2 Customization effort.
• @priethor has created a created a Github project board to track the remaining Phase 2 tasks.
• 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/ 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
  • current version is 14.4.0 (last week)
  • 14.5.0 RC is out

Updates based on updated scope for site editing projects

• Navigation Block
• Site Editor & Templates
• Building with Patterns
• Design Tools
• Layout Block Support
• Layout Option & DesignTools
• Styles
• Style Engine
• Query Block
• Mobile Team
• Components Team
• WebFonts API

Task Coordination

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

@mamaduka – No blockers. I’m primarily working on the “pathway to migrate widgets to block themes” feature this week, and I hope to share my progress soon.

@fabiankaegy – I have two PR’s that I’d like to share because they could use some additional eyes:

• Eslint Plugin: Change plugin dependencies to peer dependencies – This is blocking the addoption of Node 18 for anyone using the package
• Add anchor support for dynamic blocks

@get_dave – I’ve been mainly focused on 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.:

• Working with contributors to prioritise and coordinate on key tasks for the Navigation project in WP 6.2.
• Iterating on a new approach to referencing Navigation Menus by slug from the Nav block. I had to pivot in response to (valid) objections from the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. team who didn’t want us to modify the REST to accept slugs.
• Also fixed a bug in Page List which made it unselectable within the Nav block…which wasn’t helpful. Unfortunately this wasn’t allowed into 6.1 but apparently it might be in the next patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. release.

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/.. It was a quiet meeting…

Editor 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. scrubs

@mamaduka – I wanted to mention that @ndiego and I are hosting a weekly Editor bug scrub every Tuesday at 14:00 UTC. Everybody is welcome to join.

Phase 2 & WordPress 6.2

@get_dave – I was curious to hear more based on this question by @fabiankaegy to @priethor: “How does the Phase 2 roadmap relate to the priorities for WP 6.2?”.

@priethor – The complete WP 6.2 roadmap is not available yet, and there is no release date for 6.2 (we closed the 6.1 release around 12 hours ago), so it’s hard to dive specifics other than we should all push forward to finish the main Phase 2 priorities and be able to say FSE is “ready, out of BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process.” in 6.2.

---

Thanks to everyone who attended the chat.

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