What's New for Developers (July 2026) - CourtneyR.dev's 2nd Brain

What's New for Developers (July 2026) 🔗 **Source:** [What's New for Developers (July 2026)](https://developer.wordpress.org/news/2026/07/whats-new-for-developers-july-2026/) > [!note]+ Document Notes > tags: [wordpress-development, gutenberg, wordpress-core, block-editor, wordpress-playground, developer-tools] > author: Ryan Welcher > source: WordPress Developer Blog > reference: https://developer.wordpress.org/news/2026/07/whats-new-for-developers-july-2026/ > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: What's New for Developers (July 2026) >  ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ## 📝 Summary - WordPress.org's monthly developer roundup for July 2026 (by Ryan Welcher) covers the run-up to WordPress 7.1, due August 19, 2026 at WordCamp US, and rounds up a month of Gutenberg, Playground, theme, and plugin-ecosystem changes. - Headline items: the 7.1 beta schedule, a Call for Testing on the reworked "Responsive Styling" device-preview system, two merge proposals (expanded read-only Core Abilities, and a `wp_knowledge` custom post type), an experimental React 19 flag in Gutenberg, a breaking icon-color change across all 330 `@wordpress/icons`, a Unicode email-address proposal merged to trunk, and a reversal of the plan to hide the Classic block from the inserter. - Why it matters: several items are breaking or semi-breaking changes landing in 7.1 (icon `fill` behavior, the hard deprecation of `__next40pxDefaultSize` across ~20 components, `@wordpress/reusable-blocks` deprecation) that plugin and theme authors need to test against now, during the beta window, not after release. - Key stakeholders: WordPress core and Gutenberg contributors, plugin/theme developers who depend on `@wordpress/components` and `@wordpress/icons`, AI Client (`wp/ai-client`) integrators, WordPress Playground/Blueprint authors, and WordPress.com Studio users. - Risks and tradeoffs: the piece flags multiple compatibility risks (React 19 experimental flag surfacing console warnings for plugins touching removed React 18 internals; icon `fill="currentColor"` breaking any CSS that styled icons via `fill`; deprecated components warning in the console ahead of the 40px default becoming permanent) alongside one visible instance of core walking back a forced UX change (Classic block) after community pushback. - Bottom line: 7.1 is entering its beta cycle with a large, mostly additive feature set (Abilities API expansion, AI Client streaming/embeddings, Playground MCP support, layout/grid improvements) bundled with a handful of real breaking changes developers should test for during the July beta window before the August 19 release. ## 📖 Main Content - The article is a categorized monthly digest (Highlights, Plugins & Tools, Themes, Playground, Resources) rather than a single argument; it aggregates dozens of make.wordpress.org posts, Trac tickets, and GitHub PRs into short, factual blurbs with links to primary sources. - **WordPress 7.1 release cycle**: Beta 1 (July 15), Beta 2 (July 22), Beta 3 (July 29), RC1 (August 5), and final release (August 19, 2026, timed to WordCamp US). The linked [Roadmap to 7.1](https://make.wordpress.org/core/2026/06/19/roadmap-to-7-1/) adds pseudo-state styling, new Playlist, Table of Contents, and Tabs blocks, an enforced iframed editor for block themes, and changed speculative-loading defaults. - **Responsive Styling**: Gutenberg 23.5 replaced fixed device-preview toggles with a freely resizable canvas. `useResizeCanvas()` is deprecated in favor of `getDeviceType()`/`setDeviceType()`, and a new `@` prefix syntax for responsive style states is meant to unlock aspect-ratio and flex-alignment controls scoped to a viewport state. An official Call for Testing opened July 3. - **Two merge proposals**: (1) expands Core Abilities with three read-only abilities (`core/read-settings`, `core/read-content`, `core/read-users`) built on existing capability checks — notably scoped to read-only to reduce risk; (2) introduces a `wp_knowledge` custom post type with permissions, revisions, three built-in knowledge types, and REST routes at `/wp/v2/knowledge` for storing site knowledge (likely aimed at AI/agent consumption). - **React 19 testing**: Gutenberg 23.4 ships an experimental `gutenberg-react-19` flag developers can enable to run React 19 instead of React 18 at runtime; compatibility polyfills log console warnings when plugin code touches removed legacy React internals — an explicit signal this is a "test now, before it's forced" moment. - **40px control size becomes permanent**: roughly 20 `@wordpress/components` — TextControl, BoxControl, BorderControl, FontSizePicker, RangeControl, ComboboxControl, ToggleGroupControl, UnitControl, FormTokenField, CustomSelectControl, and others — hard-deprecate the `__next40pxDefaultSize` opt-in prop for 7.1, since 40px becomes the unconditional default. - **Icon color inheritance (breaking)**: all 330 icons in `@wordpress/icons` v15 now declare `fill="currentColor"` instead of a hardcoded fill, meaning any CSS that previously targeted `fill` directly to recolor an icon will stop working; the fix is to use CSS `color`. This ships alongside a new `wp/v2/icon-collections` REST endpoint, label-based search in `WP_Icons_Registry`, stricter slug validation, and a roadmap commitment to `register_icon()`/`unregister_icon()` PHP functions in 7.1. - **Unicode email addresses**: closes a WordPress Trac ticket opened in 2015. Sites with `utf8mb4` database support can now accept UTF-8 local parts in email addresses, with internationalized domains handled via Punycode conversion, backed by a new `WP_Email_Address` class. A Call for Testing is live. - **Classic block reversal**: the original 7.1 plan to hide the Classic block from the block inserter was reverted after (implied, not stated explicitly in the source) community feedback; the block stays visible, and the team's stated focus shifts to building better alternatives rather than forcing removal. - **AI Client roadmap**: the WordPress AI team previewed streaming support for generation responses and embeddings support for semantic/vector search coming to the AI Client in 7.1, explicitly framed as primitives for plugin developers rather than end-user features. - **Package-level changes**: `@wordpress/reusable-blocks` is deprecated (all actions/selectors now log warnings); a dependency-surface cleanup fixed published dependencies across roughly 30 packages and made `@types/react` an optional peer dependency; the experimental Tabs block removed its public `core/tabs` store during pre-stabilization cleanup (a reminder that experimental block APIs are not stable contracts). - **WordPress Studio**: version 1.10 added Linux support; 1.11.0 added "Studio Code," described as WordPress.com's agentic development tool, to the desktop app — extending Studio from a local-environment tool toward an AI-assisted dev tool. - **Media pipeline**: GIF uploads now also generate video companion files; HEIC/HEIF uploads are accepted even without server-side editor support; the REST attachment endpoint gained output-format, progressive-rendering, and quality fields; infinite scrolling is returning to the Media Library with an opt-out. - **Plugin Directory**: screenshot galleries were rebuilt on core Gallery and Image blocks with lightbox support and adaptive layout — an example of wordpress.org itself dogfooding block-based UI over bespoke front-end code. - **Performance roadmap for 7.1**: frontend View Transitions and Enhanced Responsive Images move forward as feature plugins; groundwork begins for a libvips-based image editor in Core; the speculative-loading default moves from "conservative" to "moderate" when caching is detected on a site. - **Themes — admin bar returns**: the admin bar now shows by default in both the post and site editors heading into 7.1, with the W-logo corner replaced by a back button; the standalone Gutenberg Experiments screen moved under Settings and the top-level Gutenberg admin menu was removed — consolidating admin surface area. - **Layout changes**: flex children set to "fixed" width are now truly fixed via `flex-shrink: 0` (the old squishable behavior is renamed "Max width," preserving the old option under a clearer label rather than removing it); Grid layouts gained a "fill available space" toggle that flips `auto-fill` to `auto-fit` via a new `autoFit` layout property. - **Block Bindings**: gained List Item block support in Core, and bound rich text now preserves nested inner blocks instead of flattening them on bind — closing a known content-fidelity gap. - **Block variation extensibility**: custom HTML block variations can now ship `innerContent`, and block transforms can target specific variations (e.g., transforming Columns or Gallery directly into a Grid variation) rather than only the base block type. - **More theme-facing updates**: Global Styles gained `textShadow` support (Gutenberg 23.5); block `visibility: false` metadata is now honored in excerpts (previously excerpts could leak hidden-block content); the Verse block supports background gradients; the Icon block gained flip/rotate controls and `block.json`-declared default icons; a `wp-elements-*` CSS class collision was fixed; `calc()` expressions now accept unitless zeros. An experimental Dynamic Gallery block variation auto-renders media attached to a post but is explicitly flagged not production-ready. - **Playground — Blueprints**: `installPlugin` step gained `activationOptions` and an `onError: "skip-plugin"` mode for optional installs that shouldn't fail the whole Blueprint; WXR import steps gained controls for preserving source URLs, skipping attachments, skipping comments, and setting a default author; rewrite rules now flush automatically after `setSiteOptions` changes permalinks (removing a manual step Blueprint authors previously had to remember). - **Playground — MCP + Abilities API**: Personal Playground added MCP support via a single `playground_ability` meta-tool that lets an agent list, inspect, and execute WordPress Abilities — a direct bridge between the Model Context Protocol and WordPress's Abilities API. - **Playground — WebRTC remote access**: Personal Playground can now be opened from another device over WebRTC, with traffic flowing browser-to-browser instead of through relay servers (implying lower latency and no server-side traffic costs for this feature). - **Playground — Blueprint v2**: roughly 30 merged PRs built out a v2 compiler including PHP/WordPress version-constraint resolution; explicitly flagged as in-progress infrastructure — v2 syntax is not yet usable. CLI fixes addressed SQLite crashes on shutdown and mount preservation for long-running sessions; SQLite journal mode now defaults to DELETE. - **Playground — other user-facing changes**: the Site Editor now respects admin color schemes; real-time collaboration can be disabled per post type; new-user notification emails no longer include the username (a modest security/privacy hardening); oEmbed provider URLs are now validated before use (a defensive fix against malformed or malicious oEmbed provider registrations). - **Resources**: one Developer Blog tutorial in the past month ("Dynamically loading template parts in block themes"), plus links to the Gutenberg 23.4 and 23.5 "What's new" posts, the WordPress 7.0 release retrospective, the 7.0.1 release schedule, new guidelines for syncing code from Gutenberg into wordpress-develop, a recap on restoring removed version history, and notes from the Core Committers meeting at WordCamp Europe 2026. ## 🗒️ Notes - This is not a transcript and contains no timestamps, so notes are dense prose without timestamp subheadings. - Structural note: the article groups items by audience (Highlights → broad/core, Plugins & Tools → component/API authors, Themes → theme/block authors, Playground → environment/tooling, Resources → further reading) rather than by chronology, which makes it a reference document more than a narrative. - Recurring pattern across the piece: several changes ship first as opt-in/experimental flags (`gutenberg-react-19`, Dynamic Gallery variation, Blueprint v2) before becoming defaults — a consistent "flag, then default" rollout discipline visible across React 19, the 40px control size, and speculative loading. - Recurring pattern #2: multiple items are explicit "test now" calls to action — the 7.1 beta schedule itself, the Responsive Styling Call for Testing, the Unicode email Call for Testing, and the React 19 flag — signaling the article is timed deliberately to the pre-beta window to maximize developer testing coverage before code freeze. - The Classic block item is the one clear example in this roundup of core reversing a previously announced decision in response to (unstated but implied) community feedback, worth flagging distinctly from the rest of the roundup's forward-only feature announcements. - The article does not disclose engagement metrics, contributor counts, or vote tallies for the merge proposals — readers must follow the linked make.wordpress.org posts for that detail; the roundup itself is a pointer document, not a primary source. ## 📚 References - [Roadmap to 7.1](https://make.wordpress.org/core/2026/06/19/roadmap-to-7-1/) - [Call for Testing: Responsive Styling](https://make.wordpress.org/test/2026/07/03/call-for-testing-responsive-styling/) - [Merge proposal: Expanding WordPress Core Abilities](https://make.wordpress.org/core/2026/07/02/merge-proposal-expanding-wordpress-core-abilities/) - [Merge proposal: Guidelines Built on Knowledge](https://make.wordpress.org/core/2026/06/22/merge-proposal-guidelines-built-on-knowledge/) - [Call for Testing: Unicode Email Addresses](https://make.wordpress.org/core/2026/06/10/call-for-testing-unicode-email-addresses/) - [The Classic block stays in the inserter for WordPress 7.1](https://make.wordpress.org/core/2026/07/07/the-classic-block-stays-in-the-inserter-for-wordpress-7-1/) - [What's coming to the AI Client in WP 7.1](https://make.wordpress.org/ai/2026/06/19/whats-coming-to-the-ai-client-in-wp-7-1/) - [WordPress Studio](https://developer.wordpress.com/studio/) - [Plugin Directory screenshot gallery update](https://make.wordpress.org/meta/2026/06/10/plugin-directory-screenshots-gallery-update/) - [Admin bar returns to editors — Gutenberg PR #79197](https://github.com/WordPress/gutenberg/pull/79197) - [Block Bindings: List Item block support — Trac #65406](https://core.trac.wordpress.org/ticket/65406) - [Personal Playground remote access over WebRTC — PR #3758](https://github.com/WordPress/wordpress-playground/pull/3758) - [Dynamically loading template parts in block themes](https://developer.wordpress.org/news/2026/06/dynamically-loading-template-parts-in-block-themes/) - [What's new in Gutenberg 23.4](https://make.wordpress.org/core/2026/06/17/whats-new-in-gutenberg-23-3-03-jun-2/) - [What's new in Gutenberg 23.5](https://make.wordpress.org/core/2026/07/01/whats-new-in-gutenberg-23-5-july-1-2026/) - [WordPress 7.0 release retrospective](https://make.wordpress.org/core/2026/06/22/wordpress-7-0-release-retrospective/) - [WordPress 7.0.1 release schedule](https://make.wordpress.org/core/2026/06/18/wordpress-7-0-1-release-schedule/) - [Guidelines for syncing code from Gutenberg into wordpress-develop](https://make.wordpress.org/core/2026/06/30/guidelines-for-syncing-code-from-gutenberg-into-wordpress-develop/) - [Recap: restoring removed version history](https://make.wordpress.org/core/2026/06/17/recap-restoring-removed-version-history/) - [Core Committers meeting at WordCamp Europe 2026](https://make.wordpress.org/core/2026/06/15/core-committers-meeting-wordcamp-europe-2026/) ## 🗣️ Paraphrase - Paragraph A: WordPress 7.1 has its beta schedule locked in, running from July 15 betas through an August 19 final release timed to WordCamp US, and this window is the last real chance for plugin and theme developers to catch breaking changes before they ship — most notably icons switching to `currentColor`-based fills, the 40px control size losing its opt-in flag, and an experimental React 19 mode that surfaces console warnings wherever plugin code depends on removed React 18 internals. - Paragraph B: Beyond the breaking-change list, 7.1 is accumulating a fair amount of new capability — read-only Core Abilities, a knowledge-storage post type, AI Client streaming and embeddings, MCP support inside Playground, and layout/grid refinements — while also showing one visible instance of the project reversing course (keeping the Classic block visible) after an announced plan met resistance, a small but notable data point about how forced UX changes get walked back in this project. ## 📰 Newsletter - WordPress 7.1 beta 1 lands July 15, with final release pegged for August 19 at WordCamp US — mark the calendar and start testing plugins now, especially anything that touches `@wordpress/icons`, `@wordpress/components`, or React internals. - Breaking change to flag for your team: all 330 core icons now inherit color via `fill="currentColor"`. If your plugin or theme recolors icons with CSS `fill`, switch to `color` before 7.1 ships. - The `__next40pxDefaultSize` opt-in prop is going away across ~20 `@wordpress/components` — 40px becomes the unconditional default. Audit any custom UI still relying on the smaller legacy size. - Good news for AI-curious developers: the AI Client is getting streaming generation and embeddings support in 7.1, plus a new `wp_knowledge` CPT and three read-only Core Abilities (`core/read-settings`, `core/read-content`, `core/read-users`) via open merge proposals — worth a comment if you have implementation opinions. - Playground keeps expanding its developer-tooling footprint: MCP support via a new `playground_ability` meta-tool, WebRTC-based remote access to Personal Playground, and quality-of-life Blueprint fixes (auto-flushed rewrite rules, better WXR import controls). - Small but real relief: the plan to hide the Classic block from the inserter for 7.1 got reverted — it's staying put while the team focuses on building better alternatives instead of forcing the change. - One tutorial published this cycle: "Dynamically loading template parts in block themes" on the Developer Blog — useful if you're building block themes that need conditional or dynamic template-part loading. ## ✅ Action Items #### DevRel - Developer advocacy: publicize the 7.1 beta schedule and the three open Calls for Testing (Responsive Styling, Unicode email addresses) with clear "here's exactly what to test" guidance for plugin/theme authors. - Education: run or commission a short workshop/office-hours session on the `gutenberg-react-19` flag and what "removed legacy internals" actually means in practice for common plugin patterns. - Developer experience: publish a migration checklist for the icon `fill`→`color` breaking change and the `__next40pxDefaultSize` removal, since both hit a large surface area of existing plugins/themes. - Developer marketing: no specific campaign called for in this source beyond the roundup itself. - Community management: no moderation or CoC item surfaced in this source. - Internal/external/cross-project: coordinate messaging between the AI team's AI Client roadmap post and the Core Abilities / `wp_knowledge` merge proposals, since all three touch the same "AI primitives in core" surface area. #### OSPO - Policy & Governance: track the `wp_knowledge` merge proposal's permissions model as a policy question — who can write site knowledge and how revisions are governed. - License Compliance: not addressed in this source. - Security Management: note the oEmbed provider URL validation fix and the removal of username from new-user notification emails as small security/privacy hardening items worth a changelog mention. - Software Inventory: track the ~30-package dependency-surface cleanup (including `@types/react` becoming an optional peer dependency) for SBOM/inventory freshness. - Developer Support: not addressed in this source. - Community Engagement: not addressed in this source. - Strategic Alignment: flag the 7.1 date (August 19, WordCamp US) as a milestone for any OKR tied to core release cadence. #### Community - Maintainers: plugin/theme maintainers should run their test suites against the `gutenberg-react-19` flag and the 40px-default components ahead of beta 1 on July 15. - Contributors: the two open merge proposals (Core Abilities expansion, `wp_knowledge` CPT) are live discussion opportunities for contributors wanting review/feedback cycles. - Sponsors: not addressed in this source. - Ecosystem: the Classic block reversal is a useful case study for ecosystem communication — worth a short retrospective on how the decision got walked back. #### WordPress - Core: prioritize triage of the icon-color and 40px-default breaking changes in the 7.1 field guide/dev notes. - Core Performance: track the speculative-loading default shift (conservative → moderate when caching is detected) and the libvips image-editor groundwork for performance-budget implications. - Core AI: pilot the AI Client's new streaming/embeddings primitives against a real plugin use case before 7.1 ships. - **Core Program Team:** coordinate the beta1→RC1→final timeline (July 15 – August 19) across dependent teams (performance, AI, Playground). - Mobile: not addressed in this source. - Playground: prioritize documentation for the new `playground_ability` MCP meta-tool and the WebRTC remote-access feature, both net-new capabilities this cycle. - Community: not addressed in this source beyond the WordCamp Europe 2026 Core Committers meeting recap link. - Training: consider a lesson/module on Blueprint v2 once its syntax stabilizes (explicitly not ready yet per this source). - Marketing: use the WordCamp US-timed 7.1 release date as a narrative hook. - Support: prep support/knowledge-base content for the Classic block reversal, since users may have seen the original "hidden" announcement. - Design: review the returned admin bar default (post + site editors) and the back-button replacement for the W-logo corner for consistency across surfaces. - Documentation: DevHub needs updates for `register_icon()`/`unregister_icon()` (planned for 7.1), the `wp/v2/icon-collections` REST endpoint, and the `/wp/v2/knowledge` REST routes once merged. - Photos: not addressed in this source. - TV: not addressed in this source. - Polyglots: the Unicode email address work (UTF-8 local parts, Punycode domains) has direct locale/i18n relevance — loop in Polyglots for testing feedback. - Accessibility: audit the admin-bar-back-button change and the new Grid "fill available space" / flex "Max width" relabeling against WCAG 2.2 AA before 7.1 final. - Meta: the Plugin Directory screenshot gallery rebuild (core Gallery/Image blocks with lightbox) is a Meta-team item worth a dedicated case-study write-up. - CLI: track the Playground CLI fixes (SQLite shutdown crashes, mount preservation, journal mode default to DELETE) for release notes. - Hosting: flag the `utf8mb4` database requirement for full Unicode email support as a hosting-compatibility checklist item. - Tide: not addressed in this source. - Openverse: not addressed in this source. - Themes: theme authors should test the flex "Max width" rename, the new Grid `autoFit` property, Block Bindings' new List Item support, and the `wp-elements-*` class-collision fix against existing theme.json configs. - Plugins: plugin authors should test against the `@wordpress/reusable-blocks` deprecation and the removed experimental `core/tabs` store if they touched either API. #### The WPCC - Programs: not addressed in this source. - Projects: not addressed in this source. - Funding experiments: not addressed in this source. ### FAIR - Technical independence: not addressed in this source. - Policies and covenants: not addressed in this source. - Productized governance artifacts: not addressed in this source. ## 🧪 Hypotheses - H1: Plugins that style `@wordpress/icons` via CSS `fill` will show visibly broken (uncolored or wrong-colored) icons once `@wordpress/icons` v15 ships in 7.1, at a rate proportional to how many popular plugins use raw `fill` selectors today. - H2: The `gutenberg-react-19` experimental flag will surface a measurable number of console-warning reports from plugin authors before beta 1 closes, concentrated in plugins using legacy React 18 internals (e.g., `ReactDOM.render`, deprecated lifecycle patterns). - H3: The Classic block reversal will correlate with a spike in forum/support-channel mentions of "Classic block" in the days immediately following the original hide-from-inserter announcement, suggesting the reversal was reactive to measurable user pushback rather than proactive. - H4: Sites without `utf8mb4` database support will silently fail to benefit from the Unicode email address feature, producing a support-ticket pattern distinguishable by hosting environment (older MySQL/MariaDB configs on budget hosts). - H5: The speculative-loading default shift from "conservative" to "moderate" (when caching is detected) will measurably improve Core Web Vitals (particularly LCP/INP) on a representative sample of cached WordPress sites post-7.1, with no significant regression on uncached sites (since the default only shifts when caching is detected). ### 📊 Methodology - H1: Static-analysis scan of the top N WordPress.org plugin repos for `fill:` CSS rules targeting `.dashicon`, icon SVG classes, or `@wordpress/icons` component output; cross-reference against actual rendering in a 7.1-beta test environment. - H2: Instrument the Gutenberg 23.4+ `gutenberg-react-19` flag to log anonymized warning counts (already logging warnings per the article) and aggregate via Gutenberg's existing telemetry/issue-tracker intake during the beta window. - H3: Time-series analysis of WordPress.org support-forum and Make Core comment volume mentioning "Classic block" around the original announcement date versus the July 7 reversal date. - H4: Segment WordPress.org site-health telemetry (if available) or hosting-provider self-reported `utf8mb4` adoption rates, then correlate with support-ticket tags referencing email/Unicode issues post-7.1. - H5: A/B or before/after Core Web Vitals field data (via CrUX or a similar real-user-monitoring dataset) comparing cached WordPress sites pre- and post-7.1 default change, controlling for traffic and hosting tier. ### ❓ Questions - What specific community feedback (forum threads, Trac comments, X/Bluesky posts) drove the Classic block reversal, and was it primarily from theme/plugin authors or end users? - How many currently-published plugins in the .org directory would fail automated tests under the `gutenberg-react-19` flag, and does the Gutenberg team plan a compatibility-scan tool ahead of forcing React 19 by default? - Will `register_icon()`/`unregister_icon()` (planned for 7.1) support third-party icon sets, or only extend the core icon library? - What's the adoption timeline for Blueprint v2 given it's still "in progress" with ~30 merged PRs — is there a target release version, or is it open-ended? - Does the `wp_knowledge` CPT's REST API (`/wp/v2/knowledge`) include any built-in rate limiting or access scoping beyond standard capability checks, given its likely use by AI agents? ### 🔮 Future Research - A follow-up compatibility audit of the WordPress.org plugin directory against the 7.1 breaking-change list (icons, 40px controls, reusable-blocks deprecation) once 7.1 ships, to quantify real-world breakage versus the article's forward-looking warnings. - A case study on the Classic block decision-reversal process as a model for how WordPress core handles forced-change pushback, useful for future deprecation planning. - Longitudinal tracking of Playground's MCP/Abilities API integration adoption among third-party AI agent tooling, since this is one of the more novel items in the roundup. ### 💡 Implications - Practice: plugin/theme developers have a roughly 5-week beta window (July 15 – August 19) to catch and fix breakage from icon color, 40px defaults, and React 19 compatibility before 7.1 ships to production sites. - Policy: the Core Abilities and `wp_knowledge` merge proposals, if accepted, would formalize read-only "AI-safe" data access patterns in core — a governance decision with downstream security implications for any AI agent granted API access. - Security: the new-user notification email no longer including username, and oEmbed provider URL validation, are both small but concrete security-hardening wins worth noting in a security changelog. - Education: the React 19 flag and Blueprint v2 work both represent teachable moments — DevRel content explaining "how to test your plugin against React 19" and "what Blueprint v2 will change" would have a ready audience per this roundup's framing. - Funding models: not directly addressed in this source; the WPCC/FAIR/funding sections of the roundup structure have no corresponding content in this article. ### 🧠 Learning Styles Assessment - Reading level estimate: approximately college/professional technical level (Flesch-Kincaid Grade ≈ 12–14), given dense use of WordPress-specific jargon (Trac tickets, REST routes, hook/API names, PR numbers) without glossary support; assumes existing familiarity with Gutenberg/block-editor terminology. #### 👀 Visual learners - Present: none — the fetched article content is text-only (headings, bullet lists, inline links); no screenshots, diagrams, or labeled code blocks were present in the extracted content. - Improve: add before/after screenshots for visual changes (admin bar return, Grid auto-fit toggle, Icon block flip/rotate), and a simple timeline graphic for the 7.1 beta schedule. #### 🔊 Aural learners - Present: none — no audio, podcast, or narration version referenced. - Improve: a 2–3 minute audio summary of the "Highlights" section alone would serve time-pressed readers well, since that section carries the most release-critical information. #### 🗣️ Verbal learners - Present: mostly plain-language blurbs with linked primary sources for deeper reading; minimal but present. - Improve: define acronyms/jargon inline on first use (MCP, WXR, SBOM-equivalent for WP, CPT) rather than assuming reader familiarity. #### 🧩 Kinesthetic learners - Present: implicit "go test this" calls to action (Calls for Testing, beta schedule) that invite hands-on engagement. - Improve: a step-by-step "how to enable `gutenberg-react-19` and file a compatibility report" checklist would convert the passive mention into an actionable lab exercise. #### 🧠 Logical learners - Present: the categorized structure (Highlights/Plugins & Tools/Themes/Playground/Resources) functions as an implicit taxonomy; the 7.1 date list is a clean mini-timeline. - Improve: a single consolidated table of "breaking changes in 7.1" (change, affected API, action required, deadline) would serve logical learners better than the current prose-bullet scatter across sections. #### 🧑‍🤝‍🧑 Social learners - Present: links out to Make WordPress team posts and merge proposals, which are themselves open discussion threads. - Improve: explicitly invite readers to comment on the two open merge proposals within the roundup text (currently just linked, not framed as an invitation to participate). #### 🧘‍♀️ Solitary learners - Present: the article is structured for self-paced, skimmable reading (headers, short bullets) well suited to independent review. - Improve: a short self-check ("which of these 6 breaking changes affect my plugin?") would help solitary readers self-assess relevance without needing to read every section. #### 🌿 Naturalistic learners - Present: none — no sustainability, environment, or lifecycle framing in this source. - Improve: not a natural fit for this content type; skip rather than force an artificial tie-in. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: clear heading hierarchy (H2 section headers, H3/H4 subsection headers) as rendered on the source page, which supports landmark navigation. - Improve: ensure all linked PR/ticket references include descriptive link text (several already do, e.g., "Roadmap to 7.1") rather than bare URLs, for screen-reader link-list navigation. #### Keyboard navigation - Present: not directly assessable from fetched text content; standard WordPress.org blog theme navigation presumed. - Improve: not applicable to this fetched-text analysis — would require live page inspection, out of scope for a content-level deep read. #### Contrast and readability - Present: not directly assessable from fetched text content. - Improve: not applicable to this fetched-text analysis — would require live page inspection. #### Text resizing and reflow - Present: not directly assessable from fetched text content. - Improve: not applicable to this fetched-text analysis. #### Media and captions - Present: no embedded audio/video in this article; not applicable. - Improve: not applicable — no media present to caption. #### Forms and interactions - Present: no forms in this article; not applicable. - Improve: not applicable — no interactive forms present. #### Standards reference - The article itself covers an accessibility-adjacent item worth flagging: the admin bar default reversal and Grid/flex layout relabeling should be checked against WCAG 2.2 AA (particularly 2.4.6 Headings and Labels, given the "Max width" relabel, and 1.4.10 Reflow for the new resizable device-preview canvas) before 7.1 ships — this is a recommendation for the WordPress project, not an assessment of the article page itself. ### 🌍 DEIB Assessment #### Cultural breadth - Present: the Unicode email address feature directly serves cultural/linguistic breadth by supporting non-Latin email local parts and internationalized domains — a concrete DEIB-relevant technical improvement. - Improve: the roundup doesn't localize or contextualize this feature for non-English-speaking readers (e.g., no example addresses in non-Latin scripts); a worked example would strengthen the case for why this matters. #### Inclusive language - Present: the article uses neutral, technical language throughout with no gendered or exclusionary phrasing observed. - Improve: minor — expand acronyms on first use (MCP, WXR, CPT) so non-native-English-speaking developers aren't forced to context-guess. #### Neurodiversity support - Present: consistent bullet-point chunking and predictable section structure (Highlights/Plugins & Tools/Themes/Playground/Resources) support scanning and reduce cognitive load. - Improve: a top-of-article TL;DR table of the 4–5 highest-impact breaking changes would reduce the working-memory burden of scanning ~30 bullet items to find what's relevant. #### Representation - Present: byline credits a single named author (Ryan Welcher); no other named contributors are highlighted in the body text, though many linked posts credit other Make WordPress team members implicitly via their source URLs. - Improve: crediting specific contributors/teams inline (e.g., "the AI team," "the Performance team") is already partially done; extending this to name individual proposal authors where public would improve representation of the broader contributor base. #### Psychological safety - Present: the Classic block section is handled respectfully, framing the reversal as a shift in team focus rather than assigning blame. - Improve: not applicable beyond current framing — the tone is already even-handed and non-alarmist throughout. ### ✅ Logical Validity #### Strong reasoning - The article is fundamentally a factual aggregation/reporting piece, not an argumentative essay, so most content is inductive-by-citation: each claim is backed by a direct link to a primary source (make.wordpress.org post, GitHub PR, or Trac ticket), which is a strong evidentiary pattern for a news-roundup genre — e.g., the Icons section cites the specific breaking change (`fill="currentColor"`) alongside the concrete remediation (use CSS `color`), which is a valid, actionable causal claim (do X or Y breaks). - The 7.1 release-date claim is well-supported by a direct link to the official Roadmap to 7.1 post, giving it the strongest evidentiary grounding in the piece. #### Fallacies - No fallacious reasoning identified — the source doesn't construct arguments or make persuasive claims requiring logical scrutiny; it reports scheduled dates, shipped features, and linked primary sources. This assessment is more suited to persuasive or argumentative content than a technical status roundup. #### Tone of voice - Neutral, informational, and terse throughout, consistent with WordPress.org developer-blog house style — short declarative sentences, minimal editorializing, occasional light framing ("Mark Your Calendars," "Test Your Plugins Now") used as section-header calls to action rather than persuasive rhetoric. ### 🛡️ DARVO Analysis - Not applicable to this source — DARVO (Deny, Attack, Reverse Victim/Offender) analysis applies to accusation/defense dynamics in interpersonal or reputational conflict narratives. This article is a factual technical status roundup with no accusations, denials, or victim/offender framing present. ## 🎯 Conclusion - WordPress 7.1 enters its beta cycle July 15 with a final release targeted for August 19, 2026 at WordCamp US, carrying a mix of net-new capability (Core Abilities expansion, AI Client streaming/embeddings, Playground MCP support, layout/grid improvements) and several breaking or semi-breaking changes (icon color inheritance, hard-deprecated 40px opt-in prop, experimental React 19 mode, `@wordpress/reusable-blocks` deprecation) that plugin and theme authors need to test against during the beta window. - Practical next steps for readers: (1) enable and test against the `gutenberg-react-19` flag now; (2) audit CSS for `fill`-based icon styling and switch to `color`; (3) remove any lingering `__next40pxDefaultSize` dependency in custom UI; (4) participate in the two open Calls for Testing (Responsive Styling, Unicode email addresses) and the two open merge proposals (Core Abilities, `wp_knowledge`) if you have implementation feedback; (5) read the linked Roadmap to 7.1 post for the full feature list beyond what this roundup summarizes. ## 🔄 Refactor Appendix — What's New for Developers (July 2026) > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't > articulate in one line why a claim matters, drop it. > > Konik claim-header rules: present tense, declarative, ≤10 words when > possible, searchable, unique, mirrors annotation focus if present. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Atoms (H3) #### [H1] WordPress 7.1 final release lands August 19, 2026 > [!quote] ID:rw_wpdev202607_01 > "Final release: August 19, 2026 (WordCamp US)" **Context & use**: - Highlights section, "WordPress 7.1: Mark Your Calendars" - Sets the hard deadline for all plugin/theme compatibility testing described in this roundup **Tags**: #xref **Highlight**: [view highlight](readwise://wpdev202607_01)  #### [H2] Icons v15 makes fill a breaking change > [!quote] ID:rw_wpdev202607_02 > "All 330 icons in @wordpress/icons v15 declare fill=\"currentColor\", a breaking change." **Context & use**: - Plugins & Tools section, "Icons Now Inherit Color" - Any plugin/theme CSS targeting icon `fill` directly will silently stop recoloring icons once this ships **Tags**: #xref **Highlight**: [view highlight](readwise://wpdev202607_02)  #### [H3] Classic block stays after plan reversal > [!quote] ID:rw_wpdev202607_03 > "The original plan to hide the Classic block from the inserter for 7.1 was reverted." **Context & use**: - Plugins & Tools section, "Classic Block Status in WordPress 7.1" - Concrete example of core reversing an announced forced-UX-change decision **Tags**: #xref **Highlight**: [view highlight](readwise://wpdev202607_03)  #### [H4] Unicode email support closes an 11-year-old ticket > [!quote] ID:rw_wpdev202607_04 > "The Unicode email proposal merged into trunk, closing a ticket opened in 2015." **Context & use**: - Highlights section area / Plugins & Tools, "Unicode Email Addresses: Call for Testing" - Illustrates how long some core proposals take from ticket-open to merge — relevant context for setting expectations on other open merge proposals in this same roundup **Tags**: #xref **Highlight**: [view highlight](readwise://wpdev202607_04)  ### 🧠 Permanent Candidates (H4) #### [P1] Forced UX changes get reverted under visible pushback **Claim** (one sentence, Courtney's voice): When a project announces a forced-removal UX change (like hiding a widely-used legacy feature) without first shipping a preferred alternative, expect the plan to get walked back once the change becomes visible to users. **Evidence pointer**: [[#H3]] **Scope & conditions**: Holds when the removed feature has an active, non-trivial user base and no ready substitute exists yet; breaks down when a genuine replacement ships alongside the removal (deprecation-with-migration-path is less likely to reverse). **Links** (≥1 with annotation): - [[Deprecation strategy]] — because applies-in software product decisions generally, not just WordPress - [[Classic block]] — because evidence-for this specific instance  ### ✏️ Fleeting Queue - [F1] Check whether the `wp_knowledge` CPT's REST API has any access scoping beyond standard capability checks — relevant given likely AI-agent consumption — https://make.wordpress.org/core/2026/06/22/merge-proposal-guidelines-built-on-knowledge/ #xref - [F2] Revisit this roundup after WordPress 7.1 ships (Aug 19, 2026) to compare predicted breaking-change impact (icons, 40px, React 19) against actual plugin-directory breakage reports — #articleseed ### → Things 3 (max 2 actions) - [ ] Audit any owned WordPress plugins/themes for CSS `fill`-based icon styling and `__next40pxDefaultSize` usage before 7.1 beta 1 (July 15) — courtneyr.dev / Outpost / PKIW plugin portfolio #things