WordPress Trend Report — 2026-07-11

Weekly Summary

Article Inventory

  1. What’s new for developers (July 2026) (WordPress Developer Blog) — WordPress 7.1 is set to release on August 19, 2026, with betas starting July 15.
  2. Transitioning To Rulesets In The Gutenberg Repository (Make Core) — As of 16:00 UTC on July 8, 2026, the Gutenberg repository has transitioned from branch protection rules to repository rulesets to fix a broken step in its plugin release process.
  3. Dev Chat Agenda – July 8, 2026 (Make Core) — The July 8, 2026 WordPress Developers Chat will focus on upcoming release discussions and include an open floor for general topics.
  4. Merge Proposal: Design System Theming (Make Core) — The Gutenberg Components Team proposes merging a theming system for WordPress admin UI, introducing design tokens and a ThemeProvider React component to enable consistent styling through CSS custom properties.
  5. The Classic block stays in the inserter for WordPress 7.1 (Make Core) — The Classic block will remain in the inserter for WordPress 7.1, with no changes to user or developer behavior and no migration required.
  6. WordPress 7.0.1 Maintenance Release (WordPress.org News) — WordPress 7.0.1 is a maintenance release addressing 31 bugs in Core and the Block Editor, with fixes impacting the block editor, admin UI, and media.
  7. Roadmap 7.1, Gutenberg 23.5, Responsive Styling, Migration to Block themes — Weekend Edition #368 (Gutenberg Times) — WordPress 7.1 is scheduled for August 19, 2026, with key features including responsive and interactive-state styling, new blocks like Playlist and Tabs, and a redesigned command palette.
  8. WordPress 7.0.1 Fixes Registration Spam, wp_kses() CSS Corruption, and 7.0 Admin Design Glitches (Gutenberg Times) — WordPress 7.0.1 addresses several critical issues from the 7.0 release, including stopping registration spam, fixing CSS corruption in wp_kses(), and resolving admin UI glitches.

The primary focus across multiple sources is the upcoming release of WordPress 7.1, scheduled for August 19, 2026, with betas starting on July 15 (source 1). This release includes new blocks like Playlist and Tabs, responsive styling features, a redesigned command palette, and improvements to Gutenberg 23.5 (source 7). The Gutenberg repository has also transitioned to using rulesets instead of branch protection rules, which was done to fix a broken step in its plugin release process (source 2).

Another notable trend is the proposed theming system for WordPress admin UI, which introduces design tokens and a ThemeProvider React component to allow consistent styling via CSS custom properties (source 4). Additionally, there is a focus on responsive editing in Gutenberg 23.5, including drag-to-resize and magnified crop canvas features (source 7).

The Classic block remains in the inserter for WordPress 7.1, following user feedback that suggested removing it had no clear benefits (source 5).

Developer Implications

Freelance and agency developers should monitor the WordPress 7.1 release cycle, starting with betas on July 15 and final release on August 19 (source 1). Testing opportunities for responsive styling features are now available, and developers should consider participating in these to ensure compatibility with upcoming changes (source 7).

The transition to repository rulesets in the Gutenberg project may affect plugin release workflows, so developers working with Gutenberg plugins should be aware of this change (source 2).

The proposed design system theming for WordPress admin UI, which includes a ThemeProvider and tools for generating accessible color ramps, may influence future theming practices (source 4). Developers should watch for updates on this proposal and consider how it might affect admin UI customization in future projects.

WordPress 7.0.1 includes critical fixes for registration spam, CSS corruption in wp_kses(), and admin design glitches (source 8). Developers should ensure their projects are updated to this version, especially if they rely on the block editor or admin UI components.

The retention of the Classic block in WordPress 7.1 means no immediate migration pressure, but developers should still explore alternatives and prepare for future migration tools (source 5).

Since Last Report


What I'm Watching

The merge proposal for the design system enhancements is exciting. It may feel like it is long overdue, but it is understandeable that core contributors waited patiently for a stable first release of the Design Tokens (DTCG) specification from the W3C Design Tokens Community Group before committing to a path forward for some of the key pieces. The proposal looks promising and is a step in the right direction. Figma offers native support for importing and exporting design tokens and the foundations for AI-generated tokens and systems has potential for allowing for some unique customizations.


Source Articles

WordPress Developer Blog

Make Core

WordPress.org News

Gutenberg Times


Build Notes