WordPress 7.1 Beta 4 was released this week, marking a significant milestone for the content management system. The update introduces several major changes that will affect developers, site builders, and content creators across the platform.

This release brings responsive styling capabilities directly into the block editor. Additionally, developers must prepare for breaking changes as the post editor transitions to a fully iframed canvas. The WordPress team has published comprehensive documentation to help users navigate these updates.

Key Features in WordPress 7.1

The WordPress 7.1 Source of Truth document details all major and minor changes in this release. Anne McCarthy, the release lead, discussed the update on the WPBuilds podcast series “At the Core.” The conversation covered responsive styling, the persistent admin bar, and enhanced inline notes.

McCarthy explained how the new image crop modal and customizable viewports change daily editing workflows. Furthermore, she addressed how community feedback influenced the decision to preserve the Classic Block. The team also provided updates on collaborative editing outreach and highlighted developer changes that require immediate testing.

The WP Minute+ podcast featured McCarthy demonstrating responsive styling with Eric Karkovack. She discussed features that didn’t make the 7.1 release, including collaborative editing. McCarthy also explained the paced approach to Classic Block deprecation.

Hidden Improvements and Developer Tools

McCarthy pointed out several hidden features in WordPress 7.1. These include the “On This Day” widget and custom icon registration for the Icon block. The release also introduces new block supports for minimum width and background gradients.

The WordPress team published multiple developer notes this week. These cover filtering Site Editor screens, new block supports, and design system theming. Additional developer notes and the WordPress 7.1 Field Guide will be published next week. All development notes are available on the Make Core blog.

Gutenberg 23.6 Release Highlights

Gutenberg 23.6 was released last week alongside the WordPress 7.1 development cycle. Tech co-lead Aki Hamano outlined the key improvements in his announcement post. The Playlist and Tabs blocks have now reached stable status.

The release includes enhancements to Notes functionality and a dynamic mode for the Gallery block. Developers can now use icon collections through a new custom icon registration API. These features represent significant steps forward in block editor functionality.

Faith Imokol from Uganda appeared on the Gutenberg Changelog podcast to discuss the release. She shared insights about WordPress community work in Uganda, including WordCamps, Campus Connect events, and website competitions. The conversation then covered details from the latest Gutenberg release.

Tools for No-Code Site Builders

Meta Box fields can now connect directly to core blocks through block bindings for custom fields. This eliminates the need for PHP templates, shortcodes, or custom blocks. Lua Nguyen demonstrated the setup process for Paragraph, Heading, Image, and Button blocks.

Users can select a block, open Attributes in the sidebar, and choose a Meta Box source. Sources include post, term, author, and settings-page fields. Image fields bind URL, alt, title, and caption separately. This feature requires WordPress 6.5 or higher, though the Attributes panel needs version 6.9.

Site Editor Resources for Page Builder Users

Gina Lucia created a comprehensive guide to the WordPress Site Editor for users transitioning from Elementor or Divi. The guide covers templates, template parts, patterns, global styles, navigation, and the Font Library. Each toolbar button receives detailed explanation, starting from Appearance → Editor.

A comparison table evaluates both approaches based on performance, flexibility, and portability. The guide includes Ollie-specific tips alongside core explanations. Users of other themes can easily skip theme-specific content.

Bikash Pun Magar presented a case for custom Gutenberg blocks over page builders on client sites. Typical Elementor pages ship 200–400 KB of extra frontend assets. This represents three to five times more than native block builds.

Developer Preparation for WordPress 7.1

Custom blocks that interact with the global window or document will break in WordPress 7.1. Ryan Welcher explained the forced iframed post editor canvas launching August 19th. The change includes no flag to check and no opt-out option.

Welcher provided five demonstrations covering viewport detection, click-outside handlers, and editor styles. The examples also address admin body-class CSS and unmaintained third-party libraries. His demo plugin includes both broken and fixed versions of each scenario.

Solutions involve using ownerDocument, defaultView, useRefEffect, and editorStyle in block.json. Developers can also use patch-package for unmaintained dependencies. Welcher published a detailed tutorial explaining what block developers need to know before the WordPress 7.1 release.

Theme Development Changes

The theme.json schema now resolves to more than 40MB across hundreds of nested properties. Sérgio Santos built a form-driven visual editor for theme.json as a VS Code extension. Fields come directly from the official schema rather than hand-written forms.

A weekly scan of core and Gutenberg adds experimental properties with clear labeling. Santos highlights the CSS variable name generation as the feature that changed his workflow. Every preset shows the CSS variable name it will generate as users type the slug.

A companion WordPress plugin mounts the same editor under Appearance. However, Santos flags it as experimental because it overwrites theme.json in place. The plugin offers no revisions or backup functionality.

WordPress Playground Updates

The new WordPress Playground interface addresses confusion about persistence and capabilities. Many users assumed every Playground was temporary. Persistence, multiple sites, Blueprints, and file editing were already available but easy to miss.

A customizable Dock gathers tools into one bottom toolbar. Features include New, Playgrounds, Blueprint, Site Settings, Database, Files, Logs, and Export. The design emerged from the Playground table at WordCamp Europe Contributor Day. Adam Zieliński used AI to explore more than 400 variations.

Fellyph Cintra introduced programmatic site management in WordPress Playground. From DevTools, users can list, create, save, rename, and switch sites. The system allows changes to PHP or networking settings. Users can also run PHP inside a site to check active plugins.

AI Integration Developments

Carlo Daniele created a guide to the Abilities API for plugin developers. The guide covers fundamentals including input schema, output schema, callback, and permission checks. A fresh WordPress install ships three abilities: site info, user info, and environment info.

Jonathan Bossenger demonstrated composing three abilities into an AI-powered WordPress plugin. Two abilities call the AI Client while a third orchestrates them. The system transforms an image URL into a draft post using wp_get_ability() and execute().

Ryan Welcher conducted a full WordPress site build using Studio Code with no hand-written code. He created a site for his son’s hockey team through AI direction alone. The agent created a custom post type, teams taxonomy, Advanced Query Loop roster, and division tabs. The agent reached for block bindings without prompting, though it occasionally generated unwanted PHP metaboxes.

Original Source: gutenbergtimes.com