WordPress 6.9: What’s New for Developers 🔗 **Source:** [WordPress 6.9: What’s New for Developers](https://wordpress.com/blog/2025/12/03/wordpress-6-9-new-for-developers/) > [!note]+ Document Notes > tags: [wordpress, development, ai] > author: Joe Fylan > source: WordPress.com > reference: [https://wordpress.com/blog/2025/12/03/wordpress-6-9-new-for-developers/] > date created: 2025-12-08 12:00 > > # 🏷️ Title: WordPress 6.9: What’s New for Developers > <!-- deep-read:sections start --> ## 🧭 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) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: WordPress 6.9 introduces the Abilities API, deeper Model Context Protocol (MCP) integration, upgrades to DataViews/DataForm/Fields, Interactivity and Block Bindings APIs, and new theme.json styling options. - Why it matters: It turns WordPress into a more AI-ready, data-driven, and customizable application platform, not just a CMS. - Key stakeholders: Core and plugin/theme developers, hosts, AI tool vendors, and site builders relying on advanced admin UX. - Risks and tradeoffs: Added complexity in APIs, potential AI overreach or misconfiguration, learning curve for new patterns, coordination with evolving MCP ecosystem. - Bottom line: 6.9 is an infrastructure-heavy release that lays groundwork for AI agents and richer admin experiences while giving theme and plugin authors more consistent control over UI and data. ## 📖 Main Content - Core arguments: - The **Abilities API** exposes site capabilities (from core, plugins, themes) in a machine-readable way so AI agents and automation tools can understand and act within a WordPress instance. - Paired with **Model Context Protocol (MCP)** and an MCP Adapter plugin, WordPress can participate in a broader ecosystem of AI tools that can create content, audit SEO, and generate reports from within the site. - **AI Building Blocks** in 6.9 are primarily foundational; most changes don’t yet appear as UI features but make WordPress intelligible to AI. - **Data infrastructure** (DataViews, DataForm, DataViewsPicker, Fields API) gets more powerful, making it easier to build consistent, filterable admin interfaces and robust forms with async validation. - **Block Bindings API** and **Interactivity API** updates enable more dynamic content binding, better performance, and richer client-side navigation and overlays. - Theme developers gain **theme.json form styling**, **border-radius presets**, and **button typography inheritance**, streamlining visual consistency. - Key terms: - Abilities API: registry of what a WordPress site can do, expressed as standardized “abilities” available to external tools. - MCP: open protocol for connecting AI assistants to tools and data sources. - DataViews/DataForm: React-based admin components for listing and editing data with opinionated UX and powerful APIs. - Block Bindings: mechanism to bind block attributes to external or dynamic data sources. - Interactivity API: framework for building interactive, client-side enhanced blocks with shared routing and state. - Uncertainties: - How quickly AI tooling around MCP and Abilities API will mature. - Best practices for securing AI agents acting inside WordPress. - Ecosystem readiness (plugins, hosts) to adopt these patterns at scale. ### 🗒️ Notes - 6.9 is framed as a **“pivotal release”** that strengthens WordPress’s foundation for an AI-assisted future. - **Abilities API** - Exposes capabilities of plugins, themes, and core in a standardized format. - Enables AI systems (Claude, ChatGPT, Gemini, etc.) to understand “what this site can do.” - Example use cases: - Create posts and schedule content based on site capabilities. - Audit content using SEO plugins and suggest revisions. - Generate sales reports from commerce data. - **Model Context Protocol (MCP)** - Open standard so AI assistants and tools can interoperate with WordPress. - MCP Adapter plugin bridges a site’s Abilities registry with AI providers. - Vision: intelligent agents performing real actions in WordPress via standardized APIs. - **AI Building Blocks initiative** - Abilities API + MCP Adapter are early infrastructure steps. - AI features are mostly not visible in UI yet; focus is on making WordPress **intelligible to AI**. - Future potential: content generation, workflow automation, dynamic external data connections, and protocol agility as AI systems evolve. - **Data and admin UX** - DataViews: - New features: infinite scroll, locked filters, typed operators (e.g., `<`, `contains`), pinned alignment and action columns. - Supports multiple layouts (table, grid, list) with filtering/search/pagination. - Ideal for plugin dashboards (e.g., orders listing). - DataForm: - New layouts: cards, side-by-side rows. - Modal/dropdown panels for secondary panels. - Async + sync validation with rule-based checks. - Goal: cleaner, intuitive complex forms with robust validation. - DataViewsPicker: - Selection management and action buttons built on DataViews. - Good for media pickers or multi-item selection flows. - Fields API: - Field types expanded from 3 to 13 (arrays, booleans, colors, dates, email, media, numbers, passwords, tel, URLs, etc.). - Rule-based validation, sync and async. - Less boilerplate, better data quality. - **Dynamic binding and interactivity** - Block Bindings API: - Developers can control which block attributes can be bound (filter: `block_bindings_supported_attributes_{$block_type}`). - Custom binding sources in the editor via `getFieldsList()`. - More core blocks support binding (e.g., Date block, Image caption). - Simplified editor UI for switching/unbinding sources. - Interactivity API: - Reuses shared stylesheets across client-side navigation for speed. - Dynamically loads script modules and manages dependencies. - Supports nested router regions and dynamic overlays for modals, popups, dropdowns. - Improved `getServerState` / `getServerContext` resets between page transitions. - New TS helpers (`AsyncAction`, `TypeYield`) for async patterns. - **Theme and design** - theme.json: - Now styles form elements (`styles.elements`) for inputs/selects (colors, borders, typography). - Styles apply site-wide, including third-party plugin forms. - Border-radius presets: - Human-readable size presets (Small/Medium/Large). - Selectable in the block editor to keep designs consistent. - Button typography inheritance: - Buttons inherit parent typography defined in theme.json. - `wp-element-button` responds automatically to Global Styles updates. - **Getting started** - Use **WordPress Playground** for zero-setup browser sandboxes. - Use **WordPress Studio** + WordPress.com managed hosting (with staging, SFTP/SSH, WP-CLI, GitHub Deployments) to experiment with 6.9 features. ## 📚 References - WordPress 6.9: What’s New for Developers (primary article) — https://wordpress.com/blog/2025/12/03/wordpress-6-9-new-for-developers/ - Model Context Protocol — https://modelcontextprotocol.io - WordPress Developer Blog: Abilities API in WordPress 6.9 — (linked from article) - WordPress Developer Blog: DataViews and DataForm guides — (linked from article) - WordPress Developer Blog: Border radius size presets in WordPress 6.9 — (linked from article) - WordPress Developer Blog: Forms theme.json makeover in WordPress 6.9 — (linked from article) - WordPress Playground — https://developer.wordpress.org/playground/ - WordPress Studio — https://wordpress.com/studio/ ## 🗣️ Paraphrase - Paragraph A: WordPress 6.9 focuses on underlying infrastructure—especially Abilities API, Interactivity API, and data components—to prepare WordPress for richer customizations and an AI-assisted future. - Paragraph B: By combining Abilities API with MCP and enhanced data/admin components, developers can build AI-aware sites, better dashboards and forms, and more interactive themes while keeping UI patterns consistent and performant. ## 📰 Newsletter WordPress 6.9 is here, and it’s a big deal for developers. Under the hood, this release adds the Abilities API plus MCP integration, turning your site into something AI tools can understand and act on. DataViews, DataForm, and the Fields API all level up, making it much easier to build polished dashboards and forms. On the front end, theme.json gets form styling, border-radius presets, and better button typography inheritance. If you’re curious where WordPress is heading with AI, start with the Abilities API docs and experiment in WordPress Playground. Plugin authors should look closely at DataViewsPicker and the expanded Fields API to modernize their admin UIs. Theme authors can standardize border radius and form styling directly in theme.json. Together, these tools make WordPress a more coherent application platform—and a friendlier target for AI assistants. ## ✅ Action Items #### DevRel - Promote Abilities API and MCP through example repos, live demos, and conference talks focused on AI agents acting inside WordPress. - Build short workshops and tutorials showing how to use DataViews/DataForm and the Fields API in real plugins. - Improve developer docs and code samples for Interactivity API patterns, including router regions and overlays. - Run targeted campaigns (blog series, streams, social) explaining how 6.9 changes the developer story and how to migrate existing plugins. - Collect structured feedback from plugin/theme developers on pain points with Abilities and data components; feed into roadmap. #### OSPO - Document contribution guidelines around AI-related components (Abilities API, MCP adapter) and clarify decision-making for protocol changes. - Ensure MCP Adapter and related tooling have clear licensing and compliance checks. - Establish vulnerability handling for AI-linked capabilities (e.g., permissions on abilities exposed to agents). - Track where MCP-enabled plugins are deployed and maintain an SBOM that flags AI integration points. - Offer internal consultation hours for teams adopting Abilities API or Interactivity API in extensions. #### Community - Support maintainers adding DataViews/DataForm to their plugins with clinics and office hours. - Provide “first issue” paths around enhancing Abilities API coverage in core and popular plugins. - Encourage sponsors to fund upgrades of key plugins to the new data components and Interactivity API patterns. - Coordinate incident drills for AI misconfiguration or over-permissioned abilities across major plugins. #### WordPress - Core: Prioritize hardening Abilities API and Interactivity API, and refine their developer ergonomics based on real-world feedback. - Core Performance: Benchmark client-side navigation and Interactivity API overlays; set budgets for script and stylesheet reuse. - Core AI: Define secure defaults and guardrails for which abilities can be exposed to external agents; prepare evaluation sets for AI actions. - **Core Program Team:** Align release messaging so AI Building Blocks, data components, and theme.json updates are presented as a coherent story. - Mobile: Explore exposing Abilities and interactive features consistently through mobile apps. - Playground: Ship example sandboxes featuring Abilities + MCP, DataViews dashboards, and binding demos. - Community: Prepare meetup/WordCamp kits focused on “Modern admin UIs with DataViews and DataForm” and “AI-ready WordPress with Abilities API.” - Training: Create lesson plans on Abilities API, Interactivity API, and 6.9 theme.json features; consider certification modules. - Marketing: Highlight real plugins using 6.9 capabilities in case studies. - Support: Update KBs and troubleshooting guides for common Interactivity/DataViews issues. - Design: Provide recommended UX patterns for form layouts, pickers, and overlays using the new components. - Documentation: Fill DevHub gaps for Abilities, Fields, DataViewsPicker, and new Interactivity helpers. - Photos: N/A for this release beyond normal content guidelines. - TV: Record short screencasts walking through DataViews/DataForm/Bindings usage. - Polyglots: Ensure new developer-facing strings in admin components are localizable and well-described. - Accessibility: Audit Interactivity API-based components and new form styling for WCAG conformance. - Meta: Update .org developer resources and plugin submission guidelines to reference 6.9 APIs. - CLI: Consider commands or scaffolds for registering abilities and data views. - Hosting: Coordinate with hosts to ensure 6.9-ready environments for Playground/Studio and Interactivity features. - Tide: Evaluate whether Abilities/Interactivity patterns should influence plugin scoring (e.g., avoid anti-patterns). - Openverse: Potentially explore Abilities for media ingestion or curation workflows. - Themes: Provide best-practice templates using border-radius presets, form styling, and typography inheritance. - Plugins: Encourage migration from custom admin tables/forms to DataViews/DataForm where appropriate. #### The WPOCC - Programs: Offer fellowships for maintainers modernizing key plugins with Abilities, DataViews, and Interactivity API. - Projects: Run documentation sprints specifically for 6.9 APIs and components. - Funding experiments: Pilot microgrants for plugins that expose robust, well-scoped abilities to AI agents. ### FAIR - Technical independence: Encourage local evaluation of AI interactions (logging abilities used, provenance info for actions taken). - Policies and covenants: Advocate for transparent AI funding and clear sunset clauses on experimental MCP adapters. - Productized governance artifacts: Create sample charters and operator agreements for AI-powered WordPress services using Abilities API. ## 🧪 Hypotheses - H1: Plugins adopting DataViews and DataForm will reduce custom admin UI maintenance time by at least 30%. - H2: Sites exposing well-scoped Abilities to AI via MCP will see higher content production throughput without proportional support tickets. - H3: Theme.json-based form styling and border-radius presets will reduce design inconsistencies reported by site builders. - H4: Interactivity API-based navigation will measurably decrease page transition times compared to classic full-page reloads. ### 📊 Methodology - For H1: Compare development/maintenance hours logged pre- and post-migration to DataViews/DataForm across a sample of plugins. - For H2: Instrument AI-assisted tasks on MCP-enabled sites, tracking completed tasks vs. AI-related incidents or rollbacks. - For H3: Survey designers and builders and analyze design QA issues before/after adopting 6.9 theme.json features. - For H4: Use synthetic and RUM performance data to compare navigation timings and resource loads for Interactivity API routes vs. classic links. ### ❓ Questions - How should abilities be scoped and permissioned to avoid overpowered AI agents? - What patterns emerge as best practice for mapping plugin features into Abilities? - Will DataViews/DataForm become the de facto standard for admin UIs? - How does MCP adoption in WordPress influence other ecosystems and vice versa? ### 🔮 Future Research - Standardized capability taxonomies for Abilities across plugin categories (e-commerce, LMS, membership, etc.). - UX research on user trust in AI agents performing actions within WordPress. - Tooling to simulate or test AI usage of abilities in staging before going live. - Patterns for multi-tenant or headless setups with Abilities and Interactivity API. ### 💡 Implications - Practice: Developers gain a clearer path to build AI-integrated sites and modern admin dashboards. - Policy: Governance around AI actions in WordPress becomes more urgent (logs, approvals, rollbacks). - Security: Attack surface shifts toward ability exposure and AI misbehavior; threat models must update. - Education: Training curricula should add Abilities, MCP, DataViews/DataForm, and Interactivity API. - Funding: Foundations and sponsors may prioritize projects that make WordPress a first-class AI platform. ### 🧠 Learning Styles Assessment - Reading level estimate: Likely ~11th–12th grade (Flesch-Kincaid), due to technical vocabulary and long sentences. #### 👀 Visual learners - Present: Screenshots of DataViews, DataViewsPicker, border-radius presets, button typography. - Improve: Add labeled architecture diagrams showing Abilities + MCP + AI agent flows and Interactivity routing paths. #### 🔊 Aural learners - Present: No explicit audio or podcast version linked. - Improve: Provide a short audio summary and spoken walkthrough of code examples or flows. #### 🗣️ Verbal learners - Present: Clear explanations, examples, and descriptions of each API and component. - Improve: Add more analogies (e.g., “Abilities as capability menus for AI”) and brief glossary callouts. #### 🧩 Kinesthetic learners - Present: Suggested experiments (e.g., bind a custom field to an Image caption; try Interactivity API for comments). - Improve: Step-by-step lab-style tasks with checklists and expected outcomes. #### 🧠 Logical learners - Present: Structured feature lists, cause-effect framing for performance improvements. - Improve: Simple tables comparing “before vs. after” for data/components and interactivity. #### 🧑‍🤝‍🧑 Social learners - Present: Implicit encouragement to share feedback and experiment. - Improve: Include discussion prompts for meetups and links to forums or Slack channels. #### 🧘‍♀️ Solitary learners - Present: Article can be read and re-read independently, with links to deeper resources. - Improve: Add self-check questions at the end of sections. #### 🌿 Naturalistic learners - Present: No explicit environmental framing. - Improve: Optional discussion of hosting efficiency or performance’s indirect environmental impact. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Standard WordPress.com blog structure with headings and images (likely alt text). - Improve: Ensure all code and images (DataViews screenshots) have descriptive alt text and heading hierarchy is strictly logical. #### Keyboard navigation - Present: Standard keyboard navigation via browser defaults and theme. - Improve: Verify visible focus states on interactive demos and ensure any modal examples have focus trapping and escape mechanisms. #### Contrast and readability - Present: WordPress.com themes usually meet baseline contrast. - Improve: Confirm 4.5:1 for text in screenshots and diagrams; ensure comfortable line height and spacing for code or UI lists. #### Text resizing and reflow - Present: Responsive layout generally works at 200% zoom. - Improve: Verify no clipping in tables or screenshots; honor prefers-reduced-motion for any animated examples. #### Media and captions - Present: Static images only, no video. - Improve: Provide text descriptions for complex UI screenshots and optional video with captions. #### Forms and interactions - Present: Article content mostly informational; form guidance is conceptual. - Improve: When linking to demos, ensure labels, error messages, and input targets meet accessibility best practices. #### Standards reference - Map gaps and checks to WCAG 2.2 AA, especially 1.4.x (contrast), 2.1.x (keyboard), 2.4.x (navigable), and 3.3.x (input assistance). ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global relevance (WordPress is worldwide), but examples are generic. - Improve: Add examples from different regions and hosting contexts; link to localized docs. #### Inclusive language - Present: Neutral and professional language; minimal idioms. - Improve: Provide more plain-language summaries for complex concepts, and clarify jargon on first use. #### Neurodiversity support - Present: Clear structure with headings and bullet lists for features. - Improve: Further chunk long paragraphs, add icon+text labels for key patterns, and keep consistent section layouts. #### Representation - Present: Limited to product screenshots and generic copy. - Improve: If adding imagery, include diverse people and roles with thoughtful alt text. #### Psychological safety - Present: Neutral technical topic with low risk of triggering content. - Improve: Provide clear community guidelines/CoC links when directing readers to feedback channels. ### ✅ Logical Validity #### Strong reasoning - Causal: “Using MCP future-proofs WordPress for an AI-driven world” is supported by the argument that protocol flexibility avoids core restructuring. - Inductive: Claims that data components make admin UIs more consistent follow from described capabilities and examples (e-commerce orders, pickers). - Clarification: Could be strengthened by empirical data (e.g., performance metrics, developer adoption stats). #### Fallacies - Mild possibility of **appeal to novelty**: framing 6.9 as redefining what the platform can become without comparative evidence. Could be softened by referencing concrete use cases or early adopters instead of broad claims. #### Tone of voice - Tone: Optimistic, forward-looking, and product-focused. - Uses phrases like “start of something meaningful” and “pivotal release” to emphasize strategic importance while staying technical. ### 🛡️ DARVO Analysis - Deny: No denial of problems; the article is promotional and doesn’t address potential downsides in depth. - Attack: No attacks on critics or alternative approaches. - Reverse victim/offender: Not present; the piece doesn’t frame WordPress or its developers as victims. - Overall, DARVO patterns do not apply; this is a straightforward product/feature announcement. ## 🎯 Conclusion WordPress 6.9 invests heavily in developer infrastructure: AI-oriented Abilities + MCP, richer data/admin components, more flexible interactivity, and opinionated theme.json styling. For developers, the practical next steps are to experiment in Playground or Studio, migrate custom admin interfaces to DataViews/DataForm, define well-scoped abilities for key plugins, and adopt the Interactivity API and theme.json features for more consistent, performant sites. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] 5–10-word present-tense claim > [!quote] [WordPress 6.9: What’s New for Developers](https://wordpress.com/blog/2025/12/03/wordpress-6-9-new-for-developers/) by [[Joe Fylan]] via [[WordPress.com]]. Published 2025-12-03. > “WordPress 6.9 is a pivotal release that strengthens the foundation for where WordPress is heading next.” Two lines: context and use. Cite data if relevant. [view highlight](https://wordpress.com/blog/2025/12/03/wordpress-6-9-new-for-developers/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [WordPress 6.9: What’s New for Developers](https://wordpress.com/blog/2025/12/03/wordpress-6-9-new-for-developers/) > “The Abilities API makes it possible to expose the capabilities of plugins, themes, and WordPress core to AI agents and automation tools in a standardized, machine-readable format.” Two lines: context and use. [view highlight](https://wordpress.com/blog/2025/12/03/wordpress-6-9-new-for-developers/#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] 5–10-word present-tense claim - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Parent-Concept]] [[Related-Idea]] #### [Z2] 5–10-word present-tense claim - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Parent-Concept]] [[Related-Idea]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Prototype a plugin exposing well-scoped Abilities via Abilities API — context/https://wordpress.com/blog/2025/12/03/wordpress-6-9-new-for-developers/ #fleeting #inbox - [F2] Migrate an existing plugin’s custom admin tables to DataViews/DataViewsPicker — context/https://wordpress.com/blog/2025/12/03/wordpress-6-9-new-for-developers/ #fleeting #inbox - [F3] Implement theme.json-based form styling and border-radius presets in a production theme — context/https://wordpress.com/blog/2025/12/03/wordpress-6-9-new-for-developers/ #fleeting #inbox --- <!-- deep-read:sections end -->