Agenda, Dev Chat, Wednesday Aug 14, 2024

Announcements

There are no announcements from the last week.

Forthcoming releases

Next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: 6.7

We are currently in the WordPress 6.7 release cycle. WordPress 6.7 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. 1 is scheduled for Tuesday, October 1 (7 weeks away!)

Next maintenance release: 6.6.2

The next maintenance release will be 6.6.2. RC1 is scheduled for August 19, and the full release is planned for August 26. Here is the Trac milestone for the release.

Next 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/ release: 19.0

Gutenberg 19.0 is scheduled for August 14.

Discussions

Reminders:

• WordCamp US is coming up on September 17–20. Please let @courane01 know if you would like to help lead the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tables on Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/..
• There is a Gutenberg Hallway Hangout on Thursday August 15, 2024 at 15:00 UTC

Please suggest other important topics for the agenda in the comments of this post.

Editor updates

You can keep up to date with the major Editor features that are currently in progress by viewing these Iteration issues.

Props to @annezazu for putting together these updates:

• 6.6 Specificity/Style tracking issue was opened to help gather and fix related specificity issues from the 6.6 release.
• Adminadmin (and super admin) design: an issue for Systematising typography styles in the admin UI was opened to “ensure design consistency and ease of maintenance”.
• Design Share #61 (Jul 15-Aug 9) — recent recap post of design efforts and a great way to see what’s top of mine for design contributors as well as how to get involved.
• Canonical blocks: New tracking issue for blocks to expand pattern/theme design with a PR underway to add an Accordion Block.
• Comments pagination 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.: efforts were kicked off to Deprecate Comments Pagination block
• Components: design efforts have started to update TimePicker component design. Great spot for accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) to get involved.
• Data views: outside of quick improvements to grid density and ease of us, a PR is underway to bring support for quick editing in the list view layout.
• Block supports & Extensibility: Stabilize the __experimentalDefaultControls block supports property & Stabilize border block support keys
• Fonts: a new issue explores exposing the Font Library for classic themes & and another discusses whether to make elements font options referenceable. Both are excellent for themers to dive into.
• Gallery block: Add lightbox option in gallery block link control.
• Grid: various issues are underway to improve grid support including broader discussions regarding major flows and questions around what should be the default mode (manual or auto).
• Media: very early PR for [WIP] Add experiment for client-side media processing which “lays the foundation for client-side media processing in Gutenberg—meaning we can do things like thumbnail generation, cropping, compression, and format conversion (transcoding) all in the browser.”
• Performance: PR Inserter: Try improving pattern loading to both improve performance and the experience of patterns in the Inserter to lessen any jumpiness in the UIUI User interface for users.
• Post formats: PR underway for Query loop / Post template: Enable post format filter which touches on broader ideas around bringing post formats to block themes.
• Templates: PR landed Add plugin template registration API greatly easing plugins registering templates with some follow up issues opened already including Template registration API: allow setting the template author to something different from a plugin. Tied to this an issue was opened around adding template states to the Site Editor, similar to block states.
• Writing: Drag & drop: allow direct block drag, Improve visualization of side by side dragging
• Zoom out: an iteration issue has been opened to track efforts for 6.7 and includes PRs like Zoom Out: Escape when clicking directly on the canvas or pressing enter on the canvas to help sort through how to engage and disengage from this option.

Open floor

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting for discussion or if you will be async.