This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor Slack 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.
Async key project updates
Read the latest updates directly from the following tracking issues:
@ntsekouras Updates on Query Loop 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 block 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.
@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 API 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 Core 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.
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:
@carlosgprim Update from the mobile team
[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.”
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