What Is New in WordPress 6.2
WordPress 6.2, "Dolphy," is a significant release focused on refining the full-site editing experience and enhancing developer tools. It introduces a more intuitive navigation interface, new design tools, and substantial performance improvements under the hood. This version makes building and customizing sites with blocks more powerful and accessible.
| Category | Key Changes |
|---|---|
| New Features | New Navigation block, Style Book, Distraction Free mode, Open type font features |
| Editor Improvements | Redesigned interface, Block inspector tabs, Image previews in List View, Block locking UI |
| Developer Experience | New HTML API, wp_get_global_stylesheet() function, Block binding API phase 1 |
| Performance | Improved lazy-loading iframes, Script loading strategy changes, Optimized autosaves |
| Accessibility | Improved List View, More screen reader announcements, Better keyboard navigation |
How is the Site Editing Experience Better?
The cornerstone of 6.2 is a completely rebuilt Navigation block. It replaces the older, more cumbersome experience with a direct, visual editing interface. You can now create and manage menus directly on the canvas, dragging and dropping items just like any other block.
The new Style Book provides a global overview of every block's appearance within your active theme's style system. This is a game-changer for designers because you can see how styling changes affect all blocks at once, ensuring visual consistency without jumping between pages.
Distraction Free mode hides all the UI chrome, letting you focus purely on content creation and layout. Combined with the more organized block inspector tabs (Separating Settings and Styles), the editor feels cleaner and more intentional.
What New Tools Do Developers Get?
For developers, the new HTML API is a major utility. It provides a proper mechanism for parsing and modifying HTML content, which is far more reliable than using regex or manual string replacement. In practice, this is huge for building reliable blocks and processing content programmatically.
The introduction of wp_get_global_stylesheet() allows themes to fetch the core CSS generated from theme.json without enqueuing it. This gives theme authors finer control over how and when these styles are output, enabling more advanced performance optimizations.
Phase 1 of the Block binding API lands, setting the foundation for connecting block attributes to dynamic data sources beyond the post content. While this initial phase is limited, it's the first step towards a more extensible and dynamic block system.
Where are the Performance Wins?
Performance improvements are mostly focused on the editor experience. Lazy-loading for iframes is now more intelligent, preventing layout shifts. The strategy for loading scripts in the classic editor was adjusted to reduce unnecessary requests, which matters for pages with multiple classic editing instances.
Autosaves have been optimized to be less intrusive. The system now waits for a pause in typing before saving, reducing server load and preventing potential conflicts when typing quickly. These are small changes that add up to a noticeably smoother editing feel.
How is Accessibility Improved?
Accessibility gets meaningful attention. The List View now displays image previews and better describes locked blocks, making the content structure clearer for everyone. Screen reader announcements are more frequent and descriptive, particularly when inserting or moving blocks.
Keyboard navigation flows have been refined throughout the editor. The focus on accessibility isn't just a checklist item; it fundamentally improves the usability of the editor for all users, regardless of how they navigate.
FAQ
What's the deal with the new Navigation block? Is it backwards compatible?
The new Navigation block is a complete rewrite and replaces the old one. While it's designed to be backwards compatible by converting existing Navigation blocks on the fly, you should test any complex menus. The underlying HTML structure and CSS classes have likely changed.
When should I use the new HTML API?
Use it anytime you need to programmatically parse or modify HTML strings in a reliable way. It's a much safer alternative to regular expressions for tasks like adding a class to specific tags or extracting elements from a content string.
What is the Block binding API for?
This API is the foundation for connecting block attributes to dynamic data sources (e.g., custom fields, site data, external APIs). The first phase is limited, but it allows core blocks like the Image block to source their URL from a post meta field.
Are there any changes to how themes handle styles?
Yes. The wp_get_global_stylesheet() function allows you to decouple the theme.json styles from the enqueue system. This is useful for inlining critical CSS or conditionally loading styles, giving theme developers more control over performance.
I use the classic editor. Does 6.2 affect me?
Yes, but mostly positively. The script loading strategy for the classic editor was optimized to prevent duplicate loads on pages with multiple editors, which can improve performance. The core accessibility and performance tweaks also benefit the classic editing experience.