The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
It’s time to get WordPress 6.7 ready for release, and help is needed to ensure it’s smooth and bugbugA 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.-free. Whether you’re an experienced contributor or joining in for the first time, everyone is welcome at our bug scrubs! 🎉
Schedule Overview
Regular bug scrubs are being held every week leading up to the WordPress 6.7 release, with some cases including two sessions a day to cover a broader time frame. As the release date approaches and activity ramps up, the number of scrubs may be increased if necessary. These efforts will help ensure everything is on track for a smooth launch. Participation is welcome at any of these sessions, so feel free to join. Bring questions, ideas, and let’s scrub some bugs together!
This post summarizes the latest Default Theme meeting (agenda).
Status update
The work on Twenty Twenty-Five is happening in the GitHub repository. At the time of the meeting, there were 54 open issues and 19 open pull requests.
There were about 45 patterns designed in total. 31 patterns were built/merged or had open in-progress PRs. 14 patterns were not yet built.
There were 34 templates designed in total, 22 templates are built (the default personal blogblog(versus network, site) and alternative ones for personal, photo and news blogs). Due to time constraints, the “blogging with sidebar” alternative likely won’t get built.
There’s an open issue to create the “combined” global style variations. 1 of the 8 variations has been created, 4 others are assigned.
It is possible to see what’s 🟢 built/ 🟡 not built/ 🔴 may not be built in the Figma file.
Some important information regarding the project timing was shared: the theme needs to be more or less complete before October 1, 2024, after that it is bugbugA 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. fixes only. And text strings need to be final before October 22, 2024.
Priorities
BlockBlockBlock 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. patterns are the highest priority now, and need to be completed as soon as possible to be used to create the other layouts such as landing pages and homepages. There are “High priority” labels and they will also dictate what’s becoming a priority along the project.
Call notes
According to the agenda, a short, informal call happened to take a look at what’s built and what’s not, and determine if some of the original designs need to be left out. Those present were @beafialho, @poena, @juanfra, @luminuu and @oncecoupled.
The call focused on the progress and challenges of the development of Twenty Twenty-Five.
Key points:
The completion of personal default templates and alternatives, with some patterns still pending-
Four patterns are blocked due to the lack of image support for categories in search templates and the new accordion block’s delay, leading to the possibility to leave out three “categoryCategoryThe 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.” patterns
The team discussed the feasibility of adding patterns directly from the patterns sidebarSidebarA sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. and the need for consistent naming and ordering of section styles
The team also considered the impact of WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US contributions and the need for thorough testing and accessibilityAccessibilityAccessibility (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) checks
Action items:
Follow up on the new accordion block PR and status
Evaluate building search result patterns or leaving them out
Consider adding a “page” category for patterns
Eventually pingPingThe act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” accessibility reviewers for testing
Next major releasemajor releaseA 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 BetaBetaA 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. The Road Map post was recently published.
Next minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.6.2
The next maintenance release will be WordPress 6.6.2. RC1 is scheduled for Sept 4, and the full release is planned for Sept 10. See the Trac milestone for the release.
Next GutenbergGutenbergThe 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.2
The next Gutenberg release will be 19.2, scheduled for September 11.
Discussion
When discussing WordPress 6.7, we highlighted that @joen has listed some items that could use some help here, and @noisysocks reminded us that it’s always worth checking the Editor tasks board, especially items in the “Todo” and “Needs review” columns.
@noisysocks confirmed that the last Gutenberg RCrelease candidateOne 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). before the feature freeze is September 18, and these are the biggest items to keep an eye on:
WordPress 6.6.2 Release Candidate 1 (RC1) is available for testing! Some ways you can help test this minor release:
Use the WordPress Beta TesterpluginPluginA 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
As this is a minor RCrelease candidateOne 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). release, select the Point Release channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in the 6.6 branch.
Use WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/ to test: wp core update https://wordpress.org/wordpress-6.6.2-RC1.zip
Multiple fixes in this release are related to CSS specificity leading to front end sites not looking as intended. If you reverted to 6.5 due to this issue, please test this release candidaterelease candidateOne 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). on your staging site.
The following coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets from TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are fixed:
The following blockBlockBlock 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. editor issues from GitHubGitHubGitHub 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/ are fixed:
The dev-reviewed workflow (double committer sign-off) remains in effect when making changes to the 6.6 branchbranchA directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..
The final release is expected on Tuesday, September 10, 2024. Please note that this date can change depending on possible issues after RC1 is released. Coordination will happen in the WordPress.orgWordPress.orgThe community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.#6-6-release-leads channel.
A special thanks to everyone who helped test, raised issues, and helped to fix tickets. With this release candidate, testing continues, so please help test!
WordPress 6.7 is set to be released on November 12th, 2024. Along with a new default theme, there are new features, like the ability to zoom out to compose content with patterns, and new APIs, like the Template Registration APIAPIAn 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.. More than anything though, this release brings refinement to how everything connects together to create a more seamless WordPress experience, whether you’re trying to upload an HEIC image to your site or display a selection of posts with the Query LoopLoopThe 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.blockBlockBlock 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..
As always, what’s shared here is being actively pursued, but doesn’t necessarily mean each will make it into the final release of WordPress 6.7.
For a more detailed look at the work related to the block editor, please refer to the 6.7 board and review the currently open Iteration issues. After a recent organization effort, Iteration issues are meant to reflect active work that’s been scoped down for a major releasemajor releaseA 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.. To get a sense of some of what’s being worked on both for this release and beyond, check out the demos shared in a recent hallway hangout.
New default theme
6.7 marks the next edition of a default WordPress theme, designed to showcase the latest in WordPress and set a new standard for block themers. This year the theme seeks to be the ultimate use case for a spectrum of bloggers: simple blogs, suitable for personal blogs like ma.tt; photo blogs, tailored primarily for photography or portfolios, and complex blogs, suitable for websites that require a wider set of blocks, with more complexity in content, like a news site.
The Query Loop block is one of the more powerful and complex blocks in the site building experience. While it’s important for the block to be robust in what it can accomplish, it also needs to strike the balance of being intuitive to customize. From reviewing the block’s settings copy to improving the context detection, the Query Loop is being intentionally revisited and improved.
With patterns getting more feature-rich and pervasive, the option to zoom out to edit and create at the pattern level over granular block editing is underway. This effort aims to provide a new, high-level approach to building and interacting with your site, with several key features in development:
A zoomed out experience in the editor when inserting patterns to facilitate high level overview of the site.
A zoomed out experience when adding a new page that emphasizes patterns.
Ability to manipulate patterns in the template via moving, deleting, etc while zoomed out, including a new vertical toolbar.
Improvements to UXUXUser experience for dragging patterns (e.g. vertical displacement).
Option to toggle zoom out on and off in the preview panel.
Option to enter and exit editing at the block level when zooming out.
Adding and interacting with media is taking a big leap forward in this release with HEIC support, auto sizes for lazy loaded images, and more background image support at an individual and global level:
View metaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. boxes in the iframed Post Editor
Previously, after an effort to iframe the post editor, meta boxes prevented the editor content from loading in an iframeiframeiFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser., causing a fair amount of disruption and workarounds. To resolve this and ensure that both metaboxes and canvas content is visible when working on content, a split view is being implemented to allow you to access both. This change will provide a consistent WYSIWYGWhat You See Is What You GetWhat You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page. experience between the Editor and frontend views.
Review the PR introducing this change for more information.
Design tools
Consolidating and expanding block supports
Various blocks are loaded up with more supports to achieve ever more designs with a special shout out to the long requested shadow support on Group blocks for designers and themers alike:
Buttons: Add border, color, and padding block supports. (63538)
Post ExcerptExcerptAn excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox.: Add border support (64022)
Term Description: Add border block support (63630)
Verse block: Add background image and minimum height support (62498)
Edit and apply font size presets
The Styles interface introduces an enhanced feature for creating, editing, removing, and applying font size presets allowing users to easily modify theme provided presets and provide custom options. For each preset, custom or otherwise, this also includes the ability to toggle on fluid typography for baked in responsiveness with the option to set custom fluid values.
To ensure confidence in using typography block supports for extenders, work is underway to stabilize these options by removing their _experimental status.
A new API is set to land for WordPress 6.7 to streamline registering templates and template parts for the many plugins that register their own. Previously, plugins needed to rely on several filters to get started, adding a barrier of entry and adoption. With this new API, there will be a more seamless extension experience for developers that aligns with what users have come to expect when interacting with templates and template parts.
Review the PR introducing this API for more information.
Preview Options API
A new API seeks to extend the Preview dropdown menu in the post/page editor allowing plugins to add custom menu items to the Preview dropdown. This extension point allows for greater flexibility in preview functionality, enabling pluginPluginA 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 developers to integrate custom preview options seamlessly into the WordPress editor with the following key features:
Introduces PreviewDropdownMenuItem component for adding custom items to the Preview dropdown
Allows plugins to add menu items with custom titles and click handlers
Maintains the existing Preview dropdown structure while allowing for extensibility
Review the PR introducing this API for more information.
Interactivity API
In WordPress 6.7, work will continue on internal improvements to ensure that the Interactivity API’s code is as simple and stable as possible and to make the Interactivity API resilient when used asynchronously (e.g., adding directives or stores after initialization). This will pave the way for performance improvements such as directive code splitting or lazy loading of interactive blocks. Finally, efforts are underway to add more built-in functionality to current blocks, starting with adding lightbox support to the Gallery block.
The Block Bindings API launched in 6.5 and iterated upon in 6.6 allows you to bind dynamic data to block attributes, solving many use cases for custom blocks and powering other features, like overrides in synced patterns. After the 6.6 iteration, several dedicated areas of work are underway with a key focus around adding a user interface (UI) that allows users to connect attributes with their binding sources, making it possible to create bindings through the UI instead of the Code Editor. The block bindings editor’s APIs also need refinement to be more accessible for external developers, as some coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. sources, like “Post Meta,” currently use private APIs to manage bindings. Testing support for additional core sources will help ensure the editor APIs are flexible enough for future needs. There is also work needed to support new features related to pattern overrides.
HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. API
Building on recent iterations, the HTML API is focused on improving support across blocks to increase confidence in markup manipulation on the server for block rendering, while ensuring seamless integration with the interactivity API. Efforts are also underway to complete the “IN BODY” insertion mode, initiated in version 6.6, to support most tags in various situations. This work is essential to prepare the HTML Processor for reliable use with any HTML document, allowing Core to build on it without concerns about failures. Feature development is currently aimed at enhancing the CSSCSSCascading Style Sheets. selector interface by adding querySelector() or a similar method to the HTML API, which is crucial for sourcing block attributes. Additionally, efforts continue on the Server Directive Processor and the replacement of block bindings to rely more on the HTML Processor instead of the Tag Processor.
Continuing to improve PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.x support
To continue improving support for PHP 8.x, code specific to prior PHP versions that are no longer supported have been removed.
Find something missing? Want to help?
If you have something you’re working on that you don’t see reflected in this post, please share a comment below so we can all be aware! If you’re reading this and want to help, a great place to start is by looking through each issue associated with each area or by diving into the Polish board where a curated set of issues are in place that anyone can jump in on.
Changelog:
September 5th: removed mention of quick edit from Data Views section.
Last week we reached over 1,000 members of our channel
WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US is coming up Sep 17-20 in Portland, Oregon – we will have a performance table at Contributor DayContributor DayContributor 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/. with Adam
WordPress 6.7BetaBetaA 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 October 1
Priority Items
WordPress performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
Performance Lab pluginPluginA 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 (and other performance plugins)
@mukesh27 for #61847 the Auto Sizes for Lazy-loaded Images PR has already been reviewed by Joe and Felix. We’re now waiting for @joemcgill feedback on whether we need a filterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to remove the auto keyword from the sizes attribute or not other then that it ready for merge.
@pbearne will work on #61103 to be ready for another review
Eventually, after ironing out remaining questions and functional quirks, we could add a version of that to the docs folder of the repository
Active Priority Projects
Investigate INP Improvements
No updates this week
Improving the calculation of image size attributes
@joemcgill I created https://github.com/WordPress/performance/issues/1511 as a stub issue to represent the next big effort related to improving image sizes improvements, and have been supporting @mukesh27 with defining a set of approaches to consider for moving that project forward, which is very close to being ready for feedback.
Enable Client Side Modern Image Generation
@swissspidy Working on GutenbergGutenbergThe 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/ PRs for media, but currently focusing on my WCUS talk
Enhance Onboarding Experience of Performance Lab Plugin
@flixos90 last week we informally chatted a bit more about asking some attendees at the WCUS booth to test using the PL plugin, to see how they experience the onboarding, where they may be confused or have questions. So that’s definitely something we’re going to incorporate in the Google booth section for performance – primarily for attendees that may not be familiar with the plugin yet, or at least haven’t used it before
Open Floor
Discussion around this Slack thread for persistent object cache
@westonruter I suppose the test for object caching should only be prominent if a site does not have page caching. A site may not use page caching due to it being highly dynamic or acquiring users to be logged in. For such a site, object caching would perhaps be the next best thing instead of page caching.
@joemcgill There are so many “it depends” scenarios when it comes to what caching strategy is best. For example, if you’re running a site like a store that needs to serve dynamic data and can’t use a full page cache, an object cache will reduce the load on the DB, which should speed up requests. However, if you run a site that can make use of a full page cache, that will usually be better because it avoids any need for the server to load data from the DB and render the page at all. For many sites, full page cache is probably a more meaningful strategy. Setting up an object cache is more complex and usually is not something folks will set up themselves—instead, relying on whatever their host has set up.
@joemcgill It’s possible that the Site Health message could be improved so most site owners aren’t confused by the nuances of all these options and focus only on the things that most people can actually affect, e.g., setting up a full-page caching solution. Hosts can also modify CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.’s default site health checks to give better guidance on their hardware. Possibly something to chat about with the #hosting team
@paaljoachim asked What can he do from the sideline? Should I mention this discussion in the hosting channel? Something else? Should I leave it up to you in this channel to followup on this?
@thelovekesh As the number of plugins in the PL mono-repo grows, CI times are increasing accordingly. To address this, we should update our workflows to:
1. Run tests only for the plugin whose files have been updated.
2. Apply the same approach for linting and static analysis.
This issue also impacts local development, particularly with PHPStan. While linting is fast with each commit(pre-commit hook), static analysis still runs across the entire codebase.
@westonruter Good idea, although there are risks for doing this when there are plugin dependencies. Like if someone changes code in Optimization Detective which Image Prioritizer depends on, then this might slip under the radar. We could specifically account for plugin dependencies
Last week we reached over 1,000 members of our channel
WordCampWordCampWordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US is coming up Sep 17-20 in Portland, Oregon – we will have a performance table at Contributor DayContributor DayContributor 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/. with Adam
WordPress 6.7BetaBetaA 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 October 1
Priority items
WordPress performance TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets
Current release milestone report. There are currently 21 tickets unresolved
Future release
Performance Lab pluginPluginA 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 (and other performance plugins) including:
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 ticketticketCreated 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
There are no announcements this week.
Forthcoming releases
Next major releasemajor releaseA 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 BetaBetaA 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.
Next maintenance release: 6.6.2
The next maintenance release will be WordPress 6.6.2. RC1 is scheduled for Sept 4, and the full release is planned for Sept 10. See the Trac milestone for the release.
Next GutenbergGutenbergThe 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.2
The next Gutenberg release will be 19.2, scheduled for September 11.
Discussions
The discussion section of the agenda is to provide a place to discuss important topics affecting the upcoming release or larger initiatives that impact the CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. Team.
Topic(s) for this week:
If you want to nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.
You can keep up to date with the major Editor features that are currently in progress by viewing these Iteration issues.
BlockBlockBlock 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. Bindings: in the latest update for 6.7, the UIUIUser interface to manage bindings was added as an experiment and a recent issue was opened to expose bindable attributes through an annotation in the block definition to make it easier to know whether a block attribute is bindable or not.
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.
Most presets are now part of the theme, and work is being done on the different templates and patterns. The repository now has priority labels to indicate the urgency of specific issues and pull requests.
Over 20 contributors have participated so far, and over 60 open issues are in the GitHubGitHubGitHub 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/ repository. Many are related to blockBlockBlock 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. patterns, and the ones with the “Need Dev” label are ready to be worked on. https://github.com/WordPress/twentytwentyfive/issues
A decision was made not to use domains or brands in graphic elements or patterns. More about that discussion and decision here. There were also conversations on how to improve the process of getting the images from the Figma file to add them to the theme, which resulted in hosting the images in a public directory.
Priorities
With the different presets already in the theme, contributors are ready to start working on the different theme styles. Next, the alternative templates for photo blogblog(versus network, site), complex blog and personal blog.
At the same time, work needs to be completed on block patterns to be used in the creation of other layouts, such as landing pages.
Open floor
@joen mentioned that there’s a good list of Gutenberg-related issues to the theme development, created by @poena, and that he’d be willing to help expedite those.
@beafialho asked how to proceed with implementing templates, when parts are still being discussed or there are independent issues to work on. The conclusion was that as long as there’s communication on why there are things that are not being fully implemented according to the design, and there are links to the other issues we can move forward to expedite things.
@beafialho also asked about creating GitHub issues vs. opening PRs directly when she finds issues with the implementation. The idea is that if the issues found are quick to fix, a PR could be the best way to expedite things. If the issues found are related to bigger changes, then creating GitHub issues would be the best way to proceed. As it can open up the game for contributors to work on those, and it’ll keep track of the progress and what happened.
#61103 (marked as an early ticketticketCreated for both bug reports and feature development on the bug tracker.) – @flixos90 had just reviewed, and @pbiron will update the PR.
@adamsilverstein shared that he had a couple of small AVIF fixes that he’s planning to move to the milestone
Next Performance Lab release
The current milestones can be found at https://github.com/WordPress/performance/milestones, and the release date is Sept 16. @joemcgill questioned whether this date will conflictconflictA conflict occurs when a patch changes code that was modified after the patch was created. These patches are considered stale, and will require a refresh of the changes before it can be applied, or the conflicts will need to be resolved. with WCUS that week.
@adamsilverstein is working on a PR for the Modern Images pluginPluginA 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 to include converting upload PNGs in addition to JPEGs that I hope will be ready for the next release.
@thelovekesh is working on Web Worker Offloading(WWO) plugin to make it ready for WPOrg. Ongoing tasks:
You must be logged in to post a comment.