WordPress 6.6 “Dorsey” shipped on July 16, 2024, named after big-band trombonist and bandleader Tommy Dorsey. Release lead Matt Mullenweg and 630+ contributors (including 150+ first-time contributors) landed 1,900+ enhancements and fixes across Core and Gutenberg.
The headline shifts in 6.6: color and font sets gave one theme multiple design moods, the Site Editor got a side-by-side page preview layout, and plugin auto-updates finally got a safety net via automatic rollbacks when an update fails. It’s a polish-and-finesse release more than a flashy-new-features one.
Color and Font Sets
The most distinctive new feature in 6.6 is the ability to define multiple color sets and font sets inside a single theme. Previously, a Block theme exposed one palette and one typography pairing. With 6.6, theme authors and site builders can ship a handful of paired sets so a single theme can carry several distinct design moods, all within the theme’s broader styling guidelines.
For client work especially, this dramatically reduces the “one theme per brand variant” overhead: same theme, multiple looks, switchable through Styles.
Side-by-Side Pages Layout in the Site Editor
The Pages screen in the Site Editor got a new side-by-side layout: page list on the left, live preview of the selected page on the right. It makes scanning a site’s pages and jumping into one to edit dramatically faster than the prior table-only view, especially for sites with dozens of pages.
Automatic Plugin Update Rollbacks
Plugin auto-updates have been around since 5.5, but if an update went wrong, you woke up to a broken site. 6.6 added automatic rollback: if a plugin update triggers a fatal error during activation, WordPress reverts to the previous version automatically.
This is the kind of feature you only notice when it saves you, but it meaningfully lowered the risk of leaving auto-updates on. If you’d been doing the “wait a week before updating” dance because of bad-update fears, 6.6 made that less necessary.
Synced Pattern Overrides
Synced patterns are reusable blocks that stay in sync across every instance. The catch was that everything stayed synced, so you couldn’t have a pattern with a shared layout but different copy per instance. 6.6 fixed that with overrides: developers can mark Heading, Paragraph, Button, and Image attributes as overridable, so each pattern instance can customize those specific values while everything else stays in sync.
For agencies and publishers, this is the feature that made synced patterns actually useful for things like author cards, product callouts, or recurring promotional blocks that share design but vary content.
Performance and Accessibility
Performance highlights in 6.6:
- Templates in the editor load approximately 35% faster overall
- Lazy-loading for post embeds, reducing initial page weight
- Removed redundant WP_Theme_JSON calls
- Disabled autoload for large options that didn’t need it
- Eliminated unnecessary polyfill dependencies
- New
data-wp-on-asyncdirective in the Interactivity API for non-blocking event handlers
Accessibility-wise, 6.6 shipped 58 fixes and enhancements, with particular focus on the Data Views component and the Inserter, the two interfaces most users spend the most editing time in.
Wrapping Up
WordPress 6.6 “Dorsey” wasn’t the splashiest release on paper, but it shipped some of the most practically useful improvements in the 6.x series: multiple design moods per theme, side-by-side page editing, the safety net of rollback for failed plugin updates, and the synced pattern overrides that finally made reusable patterns work the way users always assumed they did.
For the broader release history, see the WordPress version history. The previous major was WordPress 6.5 “Regina”; the next was WordPress 6.7 “Rollins”. The current major release is WordPress 7.0 “Armstrong”.
Official references: the WordPress 6.6 announcement, the 6.6 Field Guide for developers, and the 6.6 release notes.
