Agenda, Dev Chat, Wednesday May 1, 2024

The next WordPress Developers Chat will take place on  Wednesday May 1, 2024 at 20:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.

Announcements

The WordPress 6.5 retrospective survey is now closed. Thank you to everyone who responded! Expect a follow-up post with collected, anonymized results once @priethor, @marybaum, and @akshayar have finished processing all of the feedback.

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/ 18.2 was released on April 24. Read about what’s new in this release.

Phase 3: the remaining phase 3 related overview issues were created for folks to join Phase 3: Block Library, Phase 3: Workflows, Phase 3: Revisions, and Phase 3: Collaboration index.

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.6

We are currently in the WordPress 6.6 release cycle.

• The 6.6 roadmap draft is well underway with feedback and efforts being coordinated in #6-6-release-leads. It’s aimed for release by end of this week.
• @ellatrix created this tracking issue for coordinating PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher backports from the Gutenberg for this release.

Next maintenance release: 6.5.3

There are currently there are currently 3 open trac tickets and 1 Gutenberg ticket left to resolve. A Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). is planned for May 2, with a tentative release date planned for May 7. There is more information about this release in this post, including the 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. scrub schedule and how you can get involved.

Next Gutenberg release: 18.3

Gutenberg 18.3 is scheduled for May 8 and will include these issues.

Discussions

Last week, we started discussing several topics raised in a recent discussion in the #core-editor channel how we can improve how contributors follow along with editor updates and improve communication within the project. There were several potential actions discussed, including:

• Create more high-level tracking issues that are not tied to a major release.
• Create 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/. channels for high-level features, such as navigation (#feature-website-navigation) and the grid 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. (#feature-grid).
• Create teams on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ for high-level features to create an easy point-of-contact and discussion space for these features.

This week, we’ll dedicate our discussion time to summarizing any action items that still need to be followed up on from that discussion.

Feel free to suggest additional topics in the comments.

Highlighted posts

• What’s new in Gutenberg 18.2? (24 April)

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Updates

Props to @annezazu for helping put together these updates.

• Expanding style variations: Color & Typography Variations for WP 6.6 was created as another iteration issue for work planned for the next release. Included in this is efforts to move color presets into the palette view to better communicate what’s changing when selecting a different color palette from a style variation.
• Data Views: various new issues and explorations are underway including allow users to adjust grid density, and consumers to set default density, add ability to display fields as a badge in grid layout, and a dedicated issue to Extensibility (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 devs pay attention!).
• Block bindings 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.: Add support to all content image and button attributes in block bindings.
• General experience: a few more general issues are worth paying attention to including improve global padding to be more consistent when inserting patterns in different ways, proposal: keep the Inserter open (meaning you have to close it out for it to close), and a recently found bug from 6.5 with a fix underway Can’t swap templates in the post editor
• Overrides in Synced Patterns: an idea has been shared for using the group block in synced patterns as a freeform content area (via pattern overrides). This helps work around the limitation that only certain blocks can have overrides and offer an open area for folks to customize.
• Unify Site Editor details view with the Inspector view: questions and concerns came up after the duplicate post functionality was merged and can be viewed here Follow up questions on the duplicate post and page feature. Please add any on your mind to that issue so we can address collectively. Outside of that, a PR is underway to move around wordcount, post status and last edited info in page summary.
• Zoomed out view: Add shuffling for header and footer template parts when zoomed out, matching current functionality with patterns.
• Components: there’s a discussion underway to betterdocument our deprecation procedures, along with a range of PRs for assessing whether certain components can be stabilized.
• Design updates: various recent PRs have been merged to refine the Site Editor experience including, update list view spacing was merged to reduce the amount of scrolling required and adjust frame animation profile for the site editor,

Tickets for assistance

Tickets for 6.6 will be prioritized.

Please include detail of tickets / PR and the links into comments, and if you intend to be available during the meeting if there are any questions or will be async.

Open floor

Items for this can be shared in the comments.

Props to @annezazu and @mikachan for reviewing.

#agenda, #core, #dev-chat