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 API. 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 Loop block.
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 release. 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.

Follow the Twenty Twenty-Five GitHub repo and read the announcement post for more information.
Foundational experience
Refining Data Views
After an initial launch in 6.5 and advancements in 6.6, this release is focused on refining the experience with a few new features planned:
- Ability to set the density of information in the grid layout.
- Option to hide/show the filters in the user interface.
- Ability to customize the column order in table views.
- Make the Grid layout aspect ratio user configurable.
- Graduate data view options out of a menu to allow more design expression.
Ultimately, the aim is to make these views more flexible for customization and more functional to use.
Follow this tracking issue for more information.
Polishing the Query Loop
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.
Follow this iteration issue for more information.
Zoom out to compose with patterns
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 UX 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.
- Advancing contentOnly editing to aid in this new experience.

Follow this iteration issue for more information.
Media improvements
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:
- Support HEIC image uploads with automatic image conversion, HEIC support and client optimizations.
- Auto Sizes for Lazy-loaded Images.
- Allow block-level background images in global styles for all blocks with background support, allowing you to set site wide options.
- Add support for background attachment (fixed backgrounds).
- Update background image support to use a modal to better consolidate the UI.
Follow this tracking issue for more information.
View meta 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 iframe, 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 WYSIWYG 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)
- Categories: Add border support (63950)
- Column: Enable border-radius support. (63924)
- Comment Template: Add Border Block Support. (64238)
- Gallery: Add border block support. (63428)
- Group: Add block support for shadow. (63295)
- Heading: Add border support. (63539)
- Image: Adopt margin block support (63546)
- Latest comments: Add color block support (63419)
- List Item: Add color support (59892)
- Media Text: Add border support (63542)
- Paragraph: Add border support (63543)
- Post Comments Form: Add Border Block Support. (64233)
- Post Content: Add background image and padding support (62499)
- Post Date: Add border support (64023)
- Post Excerpt: Add border support (64022)
- Post Terms: Add border support (64246)
- Post Title: Add border support (64024)
- Quote: Add border support (63544), add spacing supports (63545), add background image and minimum height support (62497)
- Search: Add margin support. (63547)
- Site Tagline: Add border support (63778)
- Site Title: Add border support (63631)
- Social Links: Add border block support (63629)
- 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.
Review the PR that implements this feature.
Stabilize experimental block supports
To ensure confidence in using typography block supports for extenders, work is underway to stabilize these options by removing their _experimental status.
Follow this iteration issue for more information.
API launches and iterations
Template Registration API
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 plugin 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.
- Bringing lightbox functionality to the Gallery block.
- Query and Search blocks: support for Instant Search.
- Ensuring multiple images with lightbox enabled create a cohesive gallery experience.
Follow this iteration issue for more information.
Block Bindings
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 core 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.
Follow this iteration issue for more information.
HTML 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 CSS 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.
Follow this iteration issue for more information.
Continuing to improve PHP 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.
Leave a Reply