The release of “Mary Lou” brings a suite of powerful WordPress 7.1 features designed to streamline site building, enhance collaboration, and modernize developer workflows.
Named after the legendary jazz pianist, arranger, and composer Mary Lou Williams, this release mirrors her spirit of continuous reinvention and collaboration. Users will immediately notice a more cohesive editing environment where the admin bar persists across all editors, bridging the gap between writing content and designing layouts. Below, we dive deep into the technical details, implementation strategies, and architectural changes introduced in this major release. WordPress 7.1 features should be evaluated in the context of the site’s current configuration and business-critical workflows.
Built-In Responsive Styling and Breakpoint Customization
Previously, designers relied on custom CSS media queries or third-party page builders to adjust layouts for mobile and tablet views. WordPress 7.1 introduces native responsive styling controls directly inside the Site Editor and Global Styles. Users can now adjust block properties—such as spacing, typography, and layout options—specifically for different viewports, previewing changes in real time. When assessing WordPress 7.1 features, test representative pages and integrations rather than relying on a single isolated check.
For theme developers, the control goes even deeper. Rather than relying on hardcoded core breakpoints, theme authors can now define custom mobile and tablet breakpoints directly in their theme.json file. This allows for highly tailored responsive designs that match the unique layout requirements of custom themes.
Here is an example of how to define custom breakpoints in theme.json:
{
"$schema": "https://schemas.wp.org/trunk/theme.json",
"version": 3,
"settings": {
"layout": {
"breakpoints": {
"mobile": "480px",
"tablet": "768px",
"desktop": "1024px"
}
}
}
}
By defining these values, the editor automatically updates its responsive preview controls and applies the corresponding media queries to block styles, eliminating layout discrepancies between the editor canvas and the front-end rendering.
A Redesigned Media Editor with Client-Side Processing
One of the most significant performance and workflow upgrades in WordPress 7.1 is the overhauled media editor. The legacy inline cropping tool has been replaced with a dedicated modal interface that brings freeform and aspect-ratio cropping, horizontal and vertical flipping, precise rotation control, and metadata editing into a single, unified workflow.
Under the hood, WordPress 7.1 shifts the heavy lifting of image processing away from the server. Image compression, resizing, and thumbnail generation now run directly in the user’s browser using a WebAssembly (Wasm) build of libvips. This architectural shift offers several major benefits:
- Reduced Server Load: Hosting environments no longer need to allocate massive PHP memory limits to handle large image uploads.
- Elimination of Timeouts: Because processing happens client-side, users will not encounter HTTP upload timeouts or memory exhaustion errors when uploading high-resolution photos.
- Modern Format Support: The media engine includes native support for AVIF, HEIC, and HDR gain maps, aligning WordPress with the output formats of modern smartphones and professional cameras.
- GIF-to-Video Conversion: To optimize page speed, WordPress 7.1 introduces an opt-in feature that automatically converts uploaded animated GIFs into highly compressed, web-friendly video formats.
Collaborative Content Creation with Inline Notes
Editorial workflows receive a substantial boost with the introduction of rich text support and inline targeting in the Notes system. In previous versions, feedback was limited to the block level, making precise editorial critique difficult. WordPress 7.1 allows users to highlight specific strings of text within a block and leave targeted inline notes.
The collaboration toolset now supports:
- Rich Text Formatting: Reviewers can format their feedback with bold, italic, inline code, and hyperlinks to reference external resources.
- User Mentions: By typing
@followed by a username, collaborators can mention specific team members, triggering automatic email or admin notifications. - Thread Management: To keep the editing canvas clean, long discussion threads can be collapsed, and multiple independent conversations can run simultaneously on different parts of the same block.
New Blocks: Organizing Content with Tabs and Playlists
WordPress 7.1 expands the core block library with two highly requested additions, reducing the reliance on third-party block plugins for common layout patterns.
The Tabs Block
The Tabs block allows content creators to organize information into tabbed panels. This is highly useful for technical documentation, product specifications, or pricing tables where displaying all information at once would clutter the page. Users can nest any core or custom block inside individual tab panels, maintaining full design flexibility.
The Playlist Block
Building on WordPress’s media capabilities, the Playlist block allows users to group multiple audio tracks into a single, cohesive player. The block features an optional visual waveform that animates dynamically as the audio plays, providing a modern, polished aesthetic for podcasters, musicians, and educators.
How Developers Can Leverage WordPress 7.1 Features
For developers, the release of “Mary Lou” opens up several new APIs and refines existing developer tooling to make extending the editor more predictable.
The Public SVG Icon API
The SVG Icon API is now fully public, allowing developers to register custom icon collections that integrate seamlessly with the core Icon block. This eliminates the need to enqueue custom icon fonts or write complex wrapper blocks.
To register a custom icon collection, developers can use the following PHP functions in their plugins or themes:
function my_custom_register_icons() {
wp_register_icon_collection( 'brand-icons', [
'label' => __( 'Brand Icons', 'textdomain' )
] );
wp_register_icon( 'brand-icons', 'custom-star', '<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M12 17.27L18.18 21l-1.64-7.03L22 9.24l-7.19-.61L12 2 9.19 8.63 2 9.24l5.46 4.73L5.82 21z"/></svg>' );
}
add_action( 'init', 'my_custom_register_icons' );
The Abilities API
First introduced in version 6.9, the Abilities API is expanded in 7.1 with a filterable execution lifecycle, custom validation, and shared discovery. This API is critical for developers building automated integrations, editorial checkpoints, or AI-powered content generation tools within the WordPress dashboard.
The Core Design System
WordPress 7.1 introduces a foundational Design System aimed at standardizing custom admin interfaces. By utilizing semantic design tokens and the ThemeProvider React component, developers can build custom plugin settings screens and dashboard widgets that inherit core styles (such as color palettes, border-radius, and cursor states), ensuring a native look and feel.
Theme Architecture and the Fully Iframed Post Editor
To ensure design consistency, the post editor is now fully iframed for all themes, matching the architecture of the Site Editor. Previously, non-block themes or hybrid configurations suffered from style leakage, where admin dashboard CSS would conflict with theme styles.
By running the editing canvas inside an isolated iframe, viewport-relative units (such as vw and vh) and CSS media queries target the canvas directly. This ensures that responsive layouts behave exactly as they would on the front end of the website.
Additionally, theme authors can now define interactive pseudo-states (hover, focus, focus-visible, and active) for Button blocks directly within theme.json:
{
"styles": {
"blocks": {
"core/button": {
"css": ":hover { background-color: var(--wp--preset--color--primary-dark); } :focus { outline: 2px solid var(--wp--preset--color--secondary); }"
}
}
}
}
Accessibility and Performance Enhancements in WordPress 7.1 Features
Accessibility and performance remain core pillars of the WordPress development lifecycle, and version 7.1 introduces several key improvements in these areas.
Standardized Tooltips
New helper functions, wp_get_tooltip() and wp_get_toggletip(), have been introduced to standardize accessible tooltips across the admin dashboard, post meta boxes, and the login screen. This ensures screen readers and keyboard-only users can easily access helper text without encountering focus traps.
Speculative Loading Configuration
Speculative loading, which prefetches pages in the background to make transitions feel instantaneous, can now be configured globally via environment variables or PHP constants. This allows hosting providers and site administrators to fine-tune prefetching behavior without relying on third-party optimization plugins:
define( 'WP_SPECULATIVE_LOADING', 'moderate' );
Media Library Optimization
The Media Library now utilizes infinite scrolling by default, significantly reducing initial page load times for sites with thousands of media assets. For users who prefer traditional navigation, a per-user setting is available to revert to standard pagination.
Frequently asked questions
How does browser-side image processing in WordPress 7.1 improve performance?
By compiling the libvips image processing library into WebAssembly (Wasm), WordPress 7.1 handles image compression, resizing, and thumbnail generation directly in the user's browser. This offloads resource-intensive tasks from the web server, preventing PHP memory limit exhaustion and upload timeouts.
Can I customize the responsive breakpoints in WordPress 7.1?
Yes. Theme developers can define custom mobile, tablet, and desktop breakpoints within the theme.json file. The Site Editor will automatically adapt its responsive preview tools and block visibility settings to match these custom values.
What is the benefit of the fully iframed post editor?
Iframing the post editor isolates the content canvas from the WordPress admin dashboard CSS. This prevents admin styles from leaking into your content, ensures viewport-relative units (like vw and vh) render accurately, and guarantees that media queries behave exactly as they do on the live site.
How do developers register custom icon collections in WordPress 7.1?
Developers can use the newly public SVG Icon API. By calling wp_register_icon_collection() and wp_register_icon() during the 'init' action, custom SVG icons can be made available natively inside the core Icon block.
Primary reference: Review the original announcement for exact release details. This article is an independent explanation and does not reproduce the source text.