Editor chat summary: Wednesday, 4 January 2023

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), 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, January 04, 2023, 14:00 UTC.

General Updates

• Gutenberg 14.9.0 has been released and is available for download!
• State of word 2022 Recap 

Async key project updates

Read the latest updates directly from the following tracking issues:

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

@ntsekouras Updates on Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.

• Fetch terms suggestions dynamically
• Connect scoped block variation to inserter variations
• Moving color block support to the Post Template 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.

Task Coordination

@poena

• This week I have mostly worked on the post-featured image block
• For phase 2, per block custom CSS is looking good, the user permission check still needs to be added.
• I’d be interested in working on Global Styles: Allow saving, importing, exporting, copying from another theme without switching to it but it’s a huge task.
• Other PRs needing review and design/design feedback
• Excerpt length
• Details/summary block

@hellofromtonya Update on the WebFonts API

• Status: Blocked by architectural work. (Dec 12/19)
• Done:  The major architectural redesign (See #41481) is now merged. The new architecture is a code rewrite which has breaking changes. Some high-level details:
  • Changes data structures and publicly exposed functions/methods.
  • Includes a temporary backwards-compatible (BC) layer that throws deprecation notices to alert developers of where they need to modify their code to use the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. This BC layer will not be backported to CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
• Next:  There are 2 more architectural tasks that need to be completed to unblock the remaining bugs, performance, and feature work can continue.

• Blocking: Webfonts: Consider renaming “webfont” to “web font” or “font” #42868 > PR [Webfonts] Rename to Fonts API #46749 in review 
• Nonblocking: Webfonts API Architecture: Remove external access to internal-only functionality #41484 > WIP
• Where can you help?
  • What should the rename be? Share your thoughts here Webfonts: Consider renaming “webfont” to “web font” or “font” #42868.
  • Test: Please test the new architecture and share feedback and testing reports.
  • Using the Webfonts API? Update your 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/theme to the new API.

@annezazu
Latest Phase 2 work update As expected, a number of PRs are now stalled due to folks taking time off. This is a wonderful and expected pause in the work! Some brief things to note:

• Two issues remain needing developer efforts: Global Styles: Allow saving, importing, exporting, copying from another theme without switching to it & Navigation Overlay – reference as template part
• Various issues seem to all be relying on what happens with browse mode and I want to be sure we’re aware of them so we don’t lose track: Re-Introduce Content Editing in the Site Editor, Add a shortcut for template browsing, Move post/page title to the top bar.

@carlosgprim Update from the mobile team
Recently fixed/improved

• Disable Unsupported Block Editor Tests (Android)
• Disable emulator’s animations on Android
• Update E2E tests by removing some in favor of integration tests
• E2E Tests – Fix block insertion flakiness
• Mobile BlockToolbar: improve useSelect for fewer rerenders
• Block Actions Menu – Fix block title regression and adds integration tests
• Block Editor Settings Endpoint – Use wp_get_global_styles instead of gutenberg_get_global_styles
• Add capabilities to force only Core blocks and control Support section
• Align hook – Add integration tests

Open Floor

@wildworks
[New Block] Add post time to read block #43403 I believe the code base is almost complete, but I would like your advice on ideas for moving forward with this PR or if it is releasable.”

@bph

The  WordPress 6.2 Planning Schedule Proposal is out and there are open slots on the release squad.

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.

Read complete transcript

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