Block Themes, Icon Block and AI –Weekend Edition #356

Block Themes, Icon Block and AI –Weekend Edition #356 🔗 **Source:** [Block Themes, Icon Block and AI –Weekend Edition #356](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/) > [!note]+ Document Notes > tags: [WordPress, Gutenberg, AI] > author: Birgit Pauli-Haack > source: Gutenberg Times > reference: [https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/] > date created: 2026-02-09 10:00 > > # 🏷️ Title: Block Themes, Icon Block and AI –Weekend Edition #356 >  ## 🧭 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: Roundup of recent developments in WordPress core, Gutenberg, block themes, tooling, and AI integrations, with curated links and commentary. - Why it matters: WordPress 7.0 and 6.9.x ship major editor, theme.json, and AI capabilities that will shape how sites are built and maintained. - Key stakeholders: Core and Gutenberg contributors, theme/plugin developers, site builders, hosts, and educators. - Risks and tradeoffs: Complexity of new APIs, potential instability of AI features, and transition costs from classic tooling/page builders. - Bottom line: Stay current on Gutenberg, theme.json, and emerging AI tools (Abilities API, MCP, Agent Skills) to remain effective in the modern WordPress stack. ## 📖 Main Content - Core & Gutenberg: WordPress 6.9.1 fixes 49 bugs; Gutenberg 22.5 introduces refinements like block-level Custom CSS and ongoing improvements ahead of WordPress 7.0. - Admin redesign: A “coat-of-paint” visual reskin is proposed to modernize wp-admin, align it with the WordPress Design System, and reduce inconsistency with the block editor. It’s uncertain whether it will land in 7.0. - Block themes & theme.json: Resources like a theme.json “anatomy” cheat sheet and curation guides show how theme.json centralizes design control, replaces much of legacy CSS, and lets developers lock down editing options to prevent design drift. - Plugins & tools: New and updated tools for block themes (maintenance-mode, navigation/header enhancements, layout utilities, carousels, tabs) improve no-code and low-code site building. - Gutenberg vs page builders: Johanne Courtright’s case against Elementor frames it as “a CMS inside a CMS,” arguing that Gutenberg plus theme.json offers one source of truth and fewer breakages when disabling plugins. - Icon Block: Ryan Welcher’s work on an Icon Block for core showcases real-time contribution and the crunch to land new blocks in 7.0. - AI integrations: - WordPress MCP Adapter connects the Abilities API to AI clients, enabling agents and custom AI-ready APIs. - AI progress roundup highlights an LLM client proposal for core, the Abilities API, AI micro-credentialing, WP-Bench for model benchmarking, and an AI experiments plugin. - Content Guidelines experiments aim to store and apply site-specific editorial rules directly in Gutenberg. - A new Agent Skills repository gives AI coding assistants structured guidance on building with modern WordPress APIs. - A call for testing invites feedback on multiple AI experiments in WordPress Playground, from type-ahead suggestions to AI-assisted moderation. ### 🗒️ Notes - AI framing: Birgit notes “an explosion of visible AI progress in the WordPress project,” with AI speeding research, analysis, and workflow automation. - Release cadence: WordPress 7.0 Beta 1 is under two weeks away, with WordPress 6.9.1 and Gutenberg 22.5 already shipped to stabilize and extend the editor. - Admin reskin: Fabian Kägy proposes incremental tickets (colors, buttons, inputs, notices, typography, spacing, frame) and an early Playground preview, plus a shared wp-base-styles handle for admin color schemes. - Audio resource: Gutenberg Changelog #125 covers WordPress 6.9 and Gutenberg 22.1–22.2 with JC Palmes, giving conversational context for recent changes. - Block theme tooling: - Planned Outage for Block Themes adds maintenance-mode tailored for block themes, including proper 503 handling and search engine–friendly behavior. - Groundworx Core is now a suite of four focused plugins (filters, carousels, cards/sections, tabs/accordion) plus a free Foundation plugin with responsive controls and a Gravity Forms block. - Dynamic Header & Navigation for Block Themes v1.5 fixes header flicker and offers Live Preview in the plugin directory. - Theme.json education: - Mike Davey’s cheat sheet shows how $schema enables IntelliSense, settings lock down design options, and styles generate CSS variables; block-level overrides provide granular control. - Nick Diego’s “15 ways to curate the WordPress editing experience” remains a key reference for locking down blocks, styles, editors, and external integrations. - Additional Developer Blog posts (largely by Justin Tadlock) explore common theme.json challenges with practical recipes. - Gutenberg vs Elementor: - Courtright argues Elementor duplicates WordPress concepts (templates, design tokens, breakpoints), causing specificity conflicts and brittle deactivation behavior. - Gutenberg plus theme.json centralizes design; changing a single spacing or color setting propagates globally, empowering clients to self-manage content and design. - Icon Block: - Ryan Welcher’s stream “Getting the Icon Block ready for WordPress 7.0” reveals the contribution process, time pressure, and the block’s path from plugin to core. - AI & Abilities: - Jonathan Bossenger’s article introduces the WordPress MCP Adapter, mapping Abilities to MCP tools for AI clients like Claude Desktop via STDIO/HTTP. - It also walks through client configuration and security considerations for exposing abilities as AI-ready APIs. - AI ecosystem: - James LePage’s roundup captures: LLM client proposal for 7.0, Abilities API in 6.9, MCP adapter, AI Leaders micro-credential, WP-Bench benchmarks, and an AI experiments plugin approaching 1,000 commits. - Content Guidelines for Gutenberg gives site owners a canonical place for editorial rules (tone, style, compliance) that can guide both humans and AI. - Agent Skills repository: - Centralized skills for AI coding assistants cover blocks, block themes, REST, Interactivity, Abilities, and performance; contributions are Markdown-based and can be global or per-project. - AI experiments call for testing: - Experiments include type-ahead writing suggestions, AI comment moderation, Markdown feeds for agents, expanded model providers, an AI Playground, MCP integration, and logging. - Detailed instructions and PR links invite community testing and UX feedback. - Closing: Birgit invites questions via email, WordPress Slack, Twitter, or the Gutenberg Changelog inbox, underscoring an open, conversational community loop. ## 📚 References - WordPress 6.9.1 Release Post (WordPress.org) - What’s new in Gutenberg 22.5? (Make WordPress Core) - WordPress Playground (playground.wordpress.net) - “Theme.json anatomy” cheat sheet (Delicious Brains / WP Engine) - “15 ways to curate the WordPress editing experience” (WordPress Developer Blog) - Planned Outage for Block Themes (WordPress.org/plugins) - Groundworx Core / Foundation plugins (Groundworx / WordPress.org) - Dynamic Header & Navigation for Block Themes (WordPress.org/plugins) - “From Abilities to AI Agents: Introducing the WordPress MCP Adapter” (WordPress Developer Blog) - AI experiments call for testing (Make WordPress AI / Playground) - Content Guidelines: A Gutenberg Experiment (Make WordPress AI) - WordPress Agent Skills repository (GitHub, WordPress organization) - Gutenberg Changelog #125 (Gutenberg Times podcast) ## 🗣️ Paraphrase - Paragraph A: Birgit opens by reflecting on how AI is accelerating her research and workflows, and notes that AI progress within WordPress, along with block themes and theme.json, are dominant themes in the current cycle. - Paragraph B: She then surveys recent releases (WordPress 6.9.1, Gutenberg 22.5), design and theme tooling improvements, new plugins, and the rapid build-out of AI infrastructure—Abilities API, MCP Adapter, Agent Skills, and experiments—before inviting readers to explore resources and share feedback. ## 📰 Newsletter Hey friends, This week’s WordPress world is all about cohesion: block themes, a smarter wp-admin, and a rapidly maturing AI stack. On the editor side, WordPress 6.9.1 and Gutenberg 22.5 ship bug fixes plus niceties like block-level Custom CSS. A proposed admin reskin aims to finally align wp-admin with the modern block editor and the WordPress Design System—keep an eye on whether it lands in 7.0. For theme builders, a new theme.json anatomy cheat sheet and classic posts like “15 ways to curate the WordPress editing experience” show how to lock in a design system while still giving clients safe flexibility. Supporting plugins—from Planned Outage for block themes to fresh navigation and layout tools—make no-code and low-code builds less fragile. There’s a thoughtful Gutenberg vs Elementor comparison too: when your design tokens live in theme.json, you get one source of truth and fewer “site broke when I disabled the plugin” moments. The biggest wave, though, is AI. WordPress now boasts an Abilities API, a WordPress MCP Adapter to plug into tools like Claude Desktop, a fast-growing AI experiments plugin, and even an official Agent Skills repo to teach AI coding assistants how to “speak WordPress” properly. James LePage’s roundup plus new Content Guidelines experiments in Gutenberg show how quickly AI is being woven into everyday workflows. If you’re curious where to start, try the Playground AI experiments (type-ahead suggestions, AI-assisted moderation, an AI Playground) and send feedback—the teams explicitly want real-world impressions. Until next time, happy building! ## ✅ Action Items #### DevRel - Map upcoming talks and demos to WordPress 7.0 themes: block themes, theme.json, Abilities API, and MCP Adapter usage. - Create hands-on workshops showing migration from classic themes/page builders to block themes with theme.json. - Expand sample repos and templates demonstrating best practices from the Agent Skills repository. - Publish developer-focused content (blogs, streams, short videos) walking through Icon Block contributions and AI experiments in Playground. - Run community surveys on AI features’ usability (type-ahead, moderation, content guidelines) and feed results back to core teams. - Coordinate with Docs and Training teams on unified messaging around Abilities API and MCP Adapter. #### OSPO - Document contribution guidelines for AI-related WordPress components (Abilities, MCP, Agent Skills) and clarify decision rights. - Ensure license compliance around AI integrations, especially when calling external model providers from plugins. - Establish a security review path for AI-enabled plugins (moderation, generation) including prompt injection and data exfiltration risks. - Maintain an up-to-date inventory of core AI APIs and experimental plugins, with SBOMs where relevant. - Provide office hours for teams integrating WordPress with AI agents to address policy and legal questions. - Track upstream WordPress AI roadmap to align organizational OKRs and funding. #### Community - Host roadmap clinics on block themes, theme.json, and AI experiments to help maintainers plan transitions. - Offer contributor onboarding sessions centered on Gutenberg, the Icon Block, and the Agent Skills repo. - Encourage sponsors to back AI testing sprints and documentation improvements with transparent deliverables. - Facilitate cross-project incident drills around misbehaving AI features (e.g., moderation errors) and coordinated disclosures. #### WordPress - Core: Prioritize issues that affect 7.0 readiness for the Icon Block, admin reskin, and LLM client proposal; keep performance budgets visible. - Core Performance: Profile new AI endpoints, block theme rendering paths, and block-level CSS to ensure regressions are caught early. - Core AI: Define responsible AI principles, evaluation datasets, and opt-in/opt-out controls for AI assistance in core. - Core Program Team: Align release cadence and communication around AI features, ensuring experiments are clearly labeled and documented. - Mobile: Explore how Content Guidelines and AI suggestions can surface safely in mobile editors. - Playground: Harden AI experiments, add reproducible bug templates, and create teaching modules for Abilities/MCP. - Community: Provide meetup kits that explain block themes, theme.json, and the evolving AI ecosystem. - Training: Build lesson plans around the MCP Adapter, Abilities API, and Agent Skills for both devs and power users. - Marketing: Shape narratives around “modern WordPress” that highlight block themes, design systems, and responsible AI. - Support: Update playbooks and KB articles for troubleshooting AI features and block-theme-specific issues. - Design: Audit the proposed admin reskin for consistency with the WordPress Design System and accessibility. - Documentation: Fill DevHub/HelpHub gaps on theme.json, Abilities API, MCP Adapter, and AI experiments. - Photos/TV/Openverse: Consider how Content Guidelines might integrate with media discovery and curation workflows. - Polyglots: Prepare guidance for translating AI-related UI and documentation clearly. - Accessibility: Review AI-assisted features (type-ahead, moderation UIs) against WCAG 2.2 AA; ensure keyboard and screen reader support. - Meta: Ensure .org infrastructure supports Playground AI experiments and Agent Skills discoverability. - CLI: Add commands or scaffolds for registering Abilities, configuring MCP, and setting up theme.json presets. - Hosting: Coordinate with hosts on safe defaults for AI-enabled features (rate limits, logging). - Tide: Explore including AI-related signals (e.g., safe defaults, clear permissions) in plugin quality scores. - Themes: Provide review guidance specific to block themes’ use of theme.json and AI-related settings. - Plugins: Strengthen security and provenance checks for MCP-, Abilities-, and AI-output–related plugins. #### The WPOCC - Programs: Design fellowships or stipends for maintainers focused on AI, block themes, and documentation. - Projects: Sponsor governance and documentation sprints around AI experiments and the Agent Skills repo. - Funding experiments: Pilot matched grants for AI safety work within the WordPress ecosystem, with transparent reporting. ### FAIR - Technical independence: Encourage local or self-hosted options for logging and validating AI calls from WordPress. - Policies and covenants: Clarify expectations about data use and model providers in community-funded AI projects. - Productized governance artifacts: Turn AI feature policies (e.g., Content Guidelines usage) into reusable charters and scorecards. ## 🧪 Hypotheses - H1: Developers who adopt theme.json and block themes will report fewer design-drift issues than those using classic themes or page builders. - H2: AI-assisted features in Gutenberg (type-ahead, guidelines) will increase content production speed without significantly harming quality. - H3: The Agent Skills repository will reduce incorrect code suggestions from AI coding assistants for WordPress tasks. - H4: MCP Adapter availability will accelerate third-party AI integrations into WordPress plugins. - H5: Admin reskin alignment with the WordPress Design System will improve perceived usability of wp-admin for new users. ### 📊 Methodology - For H1: Survey and compare issue trackers across block-theme projects vs classic/page-builder projects; measure frequency of CSS conflicts and support requests. - For H2: Run controlled writing experiments with and without AI suggestions, measuring time-to-publish and editorial revision rates. - For H3: Benchmark AI-generated code snippets before and after applying Agent Skills prompts on standardized WordPress tasks. - For H4: Track MCP Adapter usage metrics, plugin directory growth in AI-tagged plugins, and time-to-first-implementation for new integrations. - For H5: Conduct usability tests with prototypes of the new admin design; use SUS scores and task completion metrics. ### ❓ Questions - How will WordPress balance experimental AI features with the stability expectations of a global CMS? - What safeguards are planned for AI-generated content to avoid legal, ethical, or brand risks? - How long will classic themes and page builders remain first-class citizens as block themes mature? - Can Content Guidelines be standardized enough to support both human authors and diverse AI tools? - How will Agent Skills be maintained as core APIs evolve? ### 🔮 Future Research - Longitudinal impact of block themes and theme.json on agency workflows and support costs. - Best practices for integrating LLMs directly into WordPress core without over-committing to specific vendors. - Governance models for community-maintained AI prompts and skills (Agent Skills, MCP abilities). - Empirical studies on user trust in AI suggestions in content editing and moderation contexts. ### 💡 Implications - Practice: Agencies may shift toward block themes plus theme.json as their default build stack, with AI assistants as standard tooling. - Policy: WordPress will need clearer guidelines on AI usage, data handling, and disclosure in core and plugins. - Security: New attack surfaces appear around AI prompts, moderation, and external model calls. - Education: Training materials must cover both design-system thinking (theme.json) and AI literacy for creators and developers. - Funding: Community and organizational funding may pivot toward AI infrastructure, documentation, and safety work. ### 🧠 Learning Styles Assessment - Reading level estimate: Likely around US Grade 10–11 (Flesch–Kincaid), given technical terminology and long sentences. #### 👀 Visual learners - Present: Screenshots of Gutenberg UI (e.g., Custom CSS sidebar), plugin examples (mentioned). - Improve: Add architecture diagrams for Abilities API, MCP, and Agent Skills; before/after visuals for admin reskin and theme.json changes. #### 🔊 Aural learners - Present: Gutenberg Changelog podcast episode covering related topics. - Improve: Provide short audio summaries of each newsletter section and key tutorials. #### 🗣️ Verbal learners - Present: Explanations of concepts like theme.json, Abilities API, and MCP Adapter with concrete examples. - Improve: Add more analogies (e.g., “design system as single source of truth”) and a concise glossary. #### 🧩 Kinesthetic learners - Present: Calls to try Playground experiments, plugins, and live previews. - Improve: Provide explicit step-by-step labs and checklists for setting up theme.json, Abilities, and MCP. #### 🧠 Logical learners - Present: Structured breakdown of features and APIs, links to systematic guides. - Improve: Include tables comparing classic vs block themes, Elementor vs Gutenberg, and different AI integration paths. #### 🧑‍🤝‍🧑 Social learners - Present: Invitations to engage via Slack, email, and testing calls. - Improve: Organize cohort-based learning paths (study groups, office hours) around AI and block themes. #### 🧘‍♀️ Solitary learners - Present: Article format supports individual reading and link-following at one’s own pace. - Improve: Add reflection prompts or self-check questions at the end of sections. #### 🌿 Naturalistic learners - Present: No explicit environmental framing. - Improve: Draw analogies between ecosystems (themes, plugins, AI tools) and natural systems; highlight sustainability aspects of efficient tooling. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Likely good use of headings and landmarks via modern WordPress theme; images may have alt text. - Improve: Ensure all screenshots have descriptive alt text, and language attributes are correctly set. #### Keyboard navigation - Present: Standard WordPress layouts generally support keyboard navigation. - Improve: Audit focus order and ensure no keyboard traps in embedded code or interactive demos. #### Contrast and readability - Present: Gutenberg Times typically offers readable contrast. - Improve: Validate 4.5:1 contrast, adjust link colors if needed, and ensure sufficient line spacing. #### Text resizing and reflow - Present: Responsive design likely supports zoom and reflow. - Improve: Test at 200–400% zoom, check for clipping, and honor prefers-reduced-motion settings. #### Media and captions - Present: Podcast episode may include basic show notes. - Improve: Provide full transcripts, captions for any videos, and avoid autoplay. #### Forms and interactions - Present: Basic email/feedback forms may exist. - Improve: Ensure clear labels, inline error messages, and large tap targets. #### Standards reference - Map issues to WCAG 2.2 AA, especially 1.4.x (contrast), 2.1.x (keyboard), 1.2.x (captions), and 3.3.x (input assistance). ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global WordPress community context, but examples mostly tool-centric. - Improve: Include case studies from diverse regions and non-English-speaking communities. #### Inclusive language - Present: Generally neutral, professional tone without exclusionary language. - Improve: Reduce jargon where possible; add plain-language summaries for complex AI topics. #### Neurodiversity support - Present: Structured headings and consistent newsletter format. - Improve: Shorter paragraphs, more bullet lists, and clear icon+text labels for sections. #### Representation - Present: Mentions contributors from different backgrounds; limited visuals in text. - Improve: Use inclusive imagery and alt text that respects diverse identities. #### Psychological safety - Present: Encouraging, non-judgmental invitations to participate and give feedback. - Improve: Link explicit community guidelines and provide clear escalation paths for issues. ### ✅ Logical Validity #### Strong reasoning - The comparison of Elementor vs Gutenberg is a strong causal argument: duplicating systems (templates, breakpoints) leads to specificity issues and fragile deactivation; a single design system (theme.json) reduces these problems. - The case for Agent Skills rests on an inductive argument: structured, maintained guidance should reduce incorrect AI code output; this follows from how LLM prompting works. #### Fallacies - None obvious; claims are largely descriptive, with clear caveats when speculative (e.g., admin reskin not guaranteed for 7.0). #### Tone of voice - Tone is conversational, optimistic, and community-oriented, with practical calls to action and appreciation for contributors. ### 🛡️ DARVO Analysis - Deny: No denial or minimization of problems; issues like design drift and Elementor conflicts are acknowledged directly. - Attack: No personal attacks; criticism is directed at tools and patterns, not individuals. - Reverse victim/offender: Not present; the article focuses on improvements and opportunities rather than blame. ## 🎯 Conclusion The article paints a picture of WordPress rapidly converging on a modern stack: block themes plus theme.json, a refreshed admin, and a growing lattice of AI capabilities (Abilities API, MCP Adapter, Agent Skills, Playground experiments). For practitioners, the practical next steps are to experiment with block themes, study theme.json, explore Playground AI features, and follow the evolving guidance around Abilities and Agent Skills—so you can build faster, safer, and more maintainable WordPress experiences. ## 🧱 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] [Block Themes, Icon Block and AI –Weekend Edition #356](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/) by [[Birgit Pauli-Haack]] via [[Gutenberg Times]]. Published 2026-02-06. > “Once understood, theme.json offers a level of granular control over what clients can and cannot do.” Two lines: context and use. Cite data if relevant. [view highlight](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [Block Themes, Icon Block and AI –Weekend Edition #356](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/) > “The WordPress project now has an official Agent Skills repository.” Two lines: context and use. [view highlight](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/#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] Theme.json centralizes WordPress design control - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[WordPress-Design-System]] [[Block-Themes]] #### [Z2] Agent Skills improve AI WordPress coding - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[AI-in-WordPress]] [[Developer-Tools]] --- ### ✏️ 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] Test AI experiments in WordPress Playground and record UX impressions — context/https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/ #fleeting #inbox - [F2] Prototype a client-friendly block theme using theme.json locking — context/https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/ #fleeting #inbox - [F3] Integrate MCP Adapter into a custom plugin and evaluate developer DX — context/https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/ #fleeting #inbox --- # 🏷️ Title: Block Themes, Icon Block and AI –Weekend Edition #356 ## 🧭 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: Roundup of recent developments in WordPress core, Gutenberg, block themes, tooling, and AI integrations, with curated links and commentary. - Why it matters: WordPress 7.0 and 6.9.x ship major editor, theme.json, and AI capabilities that will shape how sites are built and maintained. - Key stakeholders: Core and Gutenberg contributors, theme/plugin developers, site builders, hosts, and educators. - Risks and tradeoffs: Complexity of new APIs, potential instability of AI features, and transition costs from classic tooling/page builders. - Bottom line: Stay current on Gutenberg, theme.json, and emerging AI tools (Abilities API, MCP, Agent Skills) to remain effective in the modern WordPress stack. ## 📖 Main Content - Core & Gutenberg: WordPress 6.9.1 fixes 49 bugs; Gutenberg 22.5 introduces refinements like block-level Custom CSS and ongoing improvements ahead of WordPress 7.0. - Admin redesign: A “coat-of-paint” visual reskin is proposed to modernize wp-admin, align it with the WordPress Design System, and reduce inconsistency with the block editor. It’s uncertain whether it will land in 7.0. - Block themes & theme.json: Resources like a theme.json “anatomy” cheat sheet and curation guides show how theme.json centralizes design control, replaces much of legacy CSS, and lets developers lock down editing options to prevent design drift. - Plugins & tools: New and updated tools for block themes (maintenance-mode, navigation/header enhancements, layout utilities, carousels, tabs) improve no-code and low-code site building. - Gutenberg vs page builders: Johanne Courtright’s case against Elementor frames it as “a CMS inside a CMS,” arguing that Gutenberg plus theme.json offers one source of truth and fewer breakages when disabling plugins. - Icon Block: Ryan Welcher’s work on an Icon Block for core showcases real-time contribution and the crunch to land new blocks in 7.0. - AI integrations: - WordPress MCP Adapter connects the Abilities API to AI clients, enabling agents and custom AI-ready APIs. - AI progress roundup highlights an LLM client proposal for core, the Abilities API, AI micro-credentialing, WP-Bench for model benchmarking, and an AI experiments plugin. - Content Guidelines experiments aim to store and apply site-specific editorial rules directly in Gutenberg. - A new Agent Skills repository gives AI coding assistants structured guidance on building with modern WordPress APIs. - A call for testing invites feedback on multiple AI experiments in WordPress Playground, from type-ahead suggestions to AI-assisted moderation. ### 🗒️ Notes - AI framing: Birgit notes “an explosion of visible AI progress in the WordPress project,” with AI speeding research, analysis, and workflow automation. - Release cadence: WordPress 7.0 Beta 1 is under two weeks away, with WordPress 6.9.1 and Gutenberg 22.5 already shipped to stabilize and extend the editor. - Admin reskin: Fabian Kägy proposes incremental tickets (colors, buttons, inputs, notices, typography, spacing, frame) and an early Playground preview, plus a shared wp-base-styles handle for admin color schemes. - Audio resource: Gutenberg Changelog #125 covers WordPress 6.9 and Gutenberg 22.1–22.2 with JC Palmes, giving conversational context for recent changes. - Block theme tooling: - Planned Outage for Block Themes adds maintenance-mode tailored for block themes, including proper 503 handling and search engine–friendly behavior. - Groundworx Core is now a suite of four focused plugins (filters, carousels, cards/sections, tabs/accordion) plus a free Foundation plugin with responsive controls and a Gravity Forms block. - Dynamic Header & Navigation for Block Themes v1.5 fixes header flicker and offers Live Preview in the plugin directory. - Theme.json education: - Mike Davey’s cheat sheet shows how $schema enables IntelliSense, settings lock down design options, and styles generate CSS variables; block-level overrides provide granular control. - Nick Diego’s “15 ways to curate the WordPress editing experience” remains a key reference for locking down blocks, styles, editors, and external integrations. - Additional Developer Blog posts (largely by Justin Tadlock) explore common theme.json challenges with practical recipes. - Gutenberg vs Elementor: - Courtright argues Elementor duplicates WordPress concepts (templates, design tokens, breakpoints), causing specificity conflicts and brittle deactivation behavior. - Gutenberg plus theme.json centralizes design; changing a single spacing or color setting propagates globally, empowering clients to self-manage content and design. - Icon Block: - Ryan Welcher’s stream “Getting the Icon Block ready for WordPress 7.0” reveals the contribution process, time pressure, and the block’s path from plugin to core. - AI & Abilities: - Jonathan Bossenger’s article introduces the WordPress MCP Adapter, mapping Abilities to MCP tools for AI clients like Claude Desktop via STDIO/HTTP. - It also walks through client configuration and security considerations for exposing abilities as AI-ready APIs. - AI ecosystem: - James LePage’s roundup captures: LLM client proposal for 7.0, Abilities API in 6.9, MCP adapter, AI Leaders micro-credential, WP-Bench benchmarks, and an AI experiments plugin approaching 1,000 commits. - Content Guidelines for Gutenberg gives site owners a canonical place for editorial rules (tone, style, compliance) that can guide both humans and AI. - Agent Skills repository: - Centralized skills for AI coding assistants cover blocks, block themes, REST, Interactivity, Abilities, and performance; contributions are Markdown-based and can be global or per-project. - AI experiments call for testing: - Experiments include type-ahead writing suggestions, AI comment moderation, Markdown feeds for agents, expanded model providers, an AI Playground, MCP integration, and logging. - Detailed instructions and PR links invite community testing and UX feedback. - Closing: Birgit invites questions via email, WordPress Slack, Twitter, or the Gutenberg Changelog inbox, underscoring an open, conversational community loop. ## 📚 References - WordPress 6.9.1 Release Post (WordPress.org) - What’s new in Gutenberg 22.5? (Make WordPress Core) - WordPress Playground (playground.wordpress.net) - “Theme.json anatomy” cheat sheet (Delicious Brains / WP Engine) - “15 ways to curate the WordPress editing experience” (WordPress Developer Blog) - Planned Outage for Block Themes (WordPress.org/plugins) - Groundworx Core / Foundation plugins (Groundworx / WordPress.org) - Dynamic Header & Navigation for Block Themes (WordPress.org/plugins) - “From Abilities to AI Agents: Introducing the WordPress MCP Adapter” (WordPress Developer Blog) - AI experiments call for testing (Make WordPress AI / Playground) - Content Guidelines: A Gutenberg Experiment (Make WordPress AI) - WordPress Agent Skills repository (GitHub, WordPress organization) - Gutenberg Changelog #125 (Gutenberg Times podcast) ## 🗣️ Paraphrase - Paragraph A: Birgit opens by reflecting on how AI is accelerating her research and workflows, and notes that AI progress within WordPress, along with block themes and theme.json, are dominant themes in the current cycle. - Paragraph B: She then surveys recent releases (WordPress 6.9.1, Gutenberg 22.5), design and theme tooling improvements, new plugins, and the rapid build-out of AI infrastructure—Abilities API, MCP Adapter, Agent Skills, and experiments—before inviting readers to explore resources and share feedback. ## 📰 Newsletter Hey friends, This week’s WordPress world is all about cohesion: block themes, a smarter wp-admin, and a rapidly maturing AI stack. On the editor side, WordPress 6.9.1 and Gutenberg 22.5 ship bug fixes plus niceties like block-level Custom CSS. A proposed admin reskin aims to finally align wp-admin with the modern block editor and the WordPress Design System—keep an eye on whether it lands in 7.0. For theme builders, a new theme.json anatomy cheat sheet and classic posts like “15 ways to curate the WordPress editing experience” show how to lock in a design system while still giving clients safe flexibility. Supporting plugins—from Planned Outage for block themes to fresh navigation and layout tools—make no-code and low-code builds less fragile. There’s a thoughtful Gutenberg vs Elementor comparison too: when your design tokens live in theme.json, you get one source of truth and fewer “site broke when I disabled the plugin” moments. The biggest wave, though, is AI. WordPress now boasts an Abilities API, a WordPress MCP Adapter to plug into tools like Claude Desktop, a fast-growing AI experiments plugin, and even an official Agent Skills repo to teach AI coding assistants how to “speak WordPress” properly. James LePage’s roundup plus new Content Guidelines experiments in Gutenberg show how quickly AI is being woven into everyday workflows. If you’re curious where to start, try the Playground AI experiments (type-ahead suggestions, AI-assisted moderation, an AI Playground) and send feedback—the teams explicitly want real-world impressions. Until next time, happy building! ## ✅ Action Items #### DevRel - Map upcoming talks and demos to WordPress 7.0 themes: block themes, theme.json, Abilities API, and MCP Adapter usage. - Create hands-on workshops showing migration from classic themes/page builders to block themes with theme.json. - Expand sample repos and templates demonstrating best practices from the Agent Skills repository. - Publish developer-focused content (blogs, streams, short videos) walking through Icon Block contributions and AI experiments in Playground. - Run community surveys on AI features’ usability (type-ahead, moderation, content guidelines) and feed results back to core teams. - Coordinate with Docs and Training teams on unified messaging around Abilities API and MCP Adapter. #### OSPO - Document contribution guidelines for AI-related WordPress components (Abilities, MCP, Agent Skills) and clarify decision rights. - Ensure license compliance around AI integrations, especially when calling external model providers from plugins. - Establish a security review path for AI-enabled plugins (moderation, generation) including prompt injection and data exfiltration risks. - Maintain an up-to-date inventory of core AI APIs and experimental plugins, with SBOMs where relevant. - Provide office hours for teams integrating WordPress with AI agents to address policy and legal questions. - Track upstream WordPress AI roadmap to align organizational OKRs and funding. #### Community - Host roadmap clinics on block themes, theme.json, and AI experiments to help maintainers plan transitions. - Offer contributor onboarding sessions centered on Gutenberg, the Icon Block, and the Agent Skills repo. - Encourage sponsors to back AI testing sprints and documentation improvements with transparent deliverables. - Facilitate cross-project incident drills around misbehaving AI features (e.g., moderation errors) and coordinated disclosures. #### WordPress - Core: Prioritize issues that affect 7.0 readiness for the Icon Block, admin reskin, and LLM client proposal; keep performance budgets visible. - Core Performance: Profile new AI endpoints, block theme rendering paths, and block-level CSS to ensure regressions are caught early. - Core AI: Define responsible AI principles, evaluation datasets, and opt-in/opt-out controls for AI assistance in core. - Core Program Team: Align release cadence and communication around AI features, ensuring experiments are clearly labeled and documented. - Mobile: Explore how Content Guidelines and AI suggestions can surface safely in mobile editors. - Playground: Harden AI experiments, add reproducible bug templates, and create teaching modules for Abilities/MCP. - Community: Provide meetup kits that explain block themes, theme.json, and the evolving AI ecosystem. - Training: Build lesson plans around the MCP Adapter, Abilities API, and Agent Skills for both devs and power users. - Marketing: Shape narratives around “modern WordPress” that highlight block themes, design systems, and responsible AI. - Support: Update playbooks and KB articles for troubleshooting AI features and block-theme-specific issues. - Design: Audit the proposed admin reskin for consistency with the WordPress Design System and accessibility. - Documentation: Fill DevHub/HelpHub gaps on theme.json, Abilities API, MCP Adapter, and AI experiments. - Photos/TV/Openverse: Consider how Content Guidelines might integrate with media discovery and curation workflows. - Polyglots: Prepare guidance for translating AI-related UI and documentation clearly. - Accessibility: Review AI-assisted features (type-ahead, moderation UIs) against WCAG 2.2 AA; ensure keyboard and screen reader support. - Meta: Ensure .org infrastructure supports Playground AI experiments and Agent Skills discoverability. - CLI: Add commands or scaffolds for registering Abilities, configuring MCP, and setting up theme.json presets. - Hosting: Coordinate with hosts on safe defaults for AI-enabled features (rate limits, logging). - Tide: Explore including AI-related signals (e.g., safe defaults, clear permissions) in plugin quality scores. - Themes: Provide review guidance specific to block themes’ use of theme.json and AI-related settings. - Plugins: Strengthen security and provenance checks for MCP-, Abilities-, and AI-output–related plugins. #### The WPOCC - Programs: Design fellowships or stipends for maintainers focused on AI, block themes, and documentation. - Projects: Sponsor governance and documentation sprints around AI experiments and the Agent Skills repo. - Funding experiments: Pilot matched grants for AI safety work within the WordPress ecosystem, with transparent reporting. ### FAIR - Technical independence: Encourage local or self-hosted options for logging and validating AI calls from WordPress. - Policies and covenants: Clarify expectations about data use and model providers in community-funded AI projects. - Productized governance artifacts: Turn AI feature policies (e.g., Content Guidelines usage) into reusable charters and scorecards. ## 🧪 Hypotheses - H1: Developers who adopt theme.json and block themes will report fewer design-drift issues than those using classic themes or page builders. - H2: AI-assisted features in Gutenberg (type-ahead, guidelines) will increase content production speed without significantly harming quality. - H3: The Agent Skills repository will reduce incorrect code suggestions from AI coding assistants for WordPress tasks. - H4: MCP Adapter availability will accelerate third-party AI integrations into WordPress plugins. - H5: Admin reskin alignment with the WordPress Design System will improve perceived usability of wp-admin for new users. ### 📊 Methodology - For H1: Survey and compare issue trackers across block-theme projects vs classic/page-builder projects; measure frequency of CSS conflicts and support requests. - For H2: Run controlled writing experiments with and without AI suggestions, measuring time-to-publish and editorial revision rates. - For H3: Benchmark AI-generated code snippets before and after applying Agent Skills prompts on standardized WordPress tasks. - For H4: Track MCP Adapter usage metrics, plugin directory growth in AI-tagged plugins, and time-to-first-implementation for new integrations. - For H5: Conduct usability tests with prototypes of the new admin design; use SUS scores and task completion metrics. ### ❓ Questions - How will WordPress balance experimental AI features with the stability expectations of a global CMS? - What safeguards are planned for AI-generated content to avoid legal, ethical, or brand risks? - How long will classic themes and page builders remain first-class citizens as block themes mature? - Can Content Guidelines be standardized enough to support both human authors and diverse AI tools? - How will Agent Skills be maintained as core APIs evolve? ### 🔮 Future Research - Longitudinal impact of block themes and theme.json on agency workflows and support costs. - Best practices for integrating LLMs directly into WordPress core without over-committing to specific vendors. - Governance models for community-maintained AI prompts and skills (Agent Skills, MCP abilities). - Empirical studies on user trust in AI suggestions in content editing and moderation contexts. ### 💡 Implications - Practice: Agencies may shift toward block themes plus theme.json as their default build stack, with AI assistants as standard tooling. - Policy: WordPress will need clearer guidelines on AI usage, data handling, and disclosure in core and plugins. - Security: New attack surfaces appear around AI prompts, moderation, and external model calls. - Education: Training materials must cover both design-system thinking (theme.json) and AI literacy for creators and developers. - Funding: Community and organizational funding may pivot toward AI infrastructure, documentation, and safety work. ### 🧠 Learning Styles Assessment - Reading level estimate: Likely around US Grade 10–11 (Flesch–Kincaid), given technical terminology and long sentences. #### 👀 Visual learners - Present: Screenshots of Gutenberg UI (e.g., Custom CSS sidebar), plugin examples (mentioned). - Improve: Add architecture diagrams for Abilities API, MCP, and Agent Skills; before/after visuals for admin reskin and theme.json changes. #### 🔊 Aural learners - Present: Gutenberg Changelog podcast episode covering related topics. - Improve: Provide short audio summaries of each newsletter section and key tutorials. #### 🗣️ Verbal learners - Present: Explanations of concepts like theme.json, Abilities API, and MCP Adapter with concrete examples. - Improve: Add more analogies (e.g., “design system as single source of truth”) and a concise glossary. #### 🧩 Kinesthetic learners - Present: Calls to try Playground experiments, plugins, and live previews. - Improve: Provide explicit step-by-step labs and checklists for setting up theme.json, Abilities, and MCP. #### 🧠 Logical learners - Present: Structured breakdown of features and APIs, links to systematic guides. - Improve: Include tables comparing classic vs block themes, Elementor vs Gutenberg, and different AI integration paths. #### 🧑‍🤝‍🧑 Social learners - Present: Invitations to engage via Slack, email, and testing calls. - Improve: Organize cohort-based learning paths (study groups, office hours) around AI and block themes. #### 🧘‍♀️ Solitary learners - Present: Article format supports individual reading and link-following at one’s own pace. - Improve: Add reflection prompts or self-check questions at the end of sections. #### 🌿 Naturalistic learners - Present: No explicit environmental framing. - Improve: Draw analogies between ecosystems (themes, plugins, AI tools) and natural systems; highlight sustainability aspects of efficient tooling. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Likely good use of headings and landmarks via modern WordPress theme; images may have alt text. - Improve: Ensure all screenshots have descriptive alt text, and language attributes are correctly set. #### Keyboard navigation - Present: Standard WordPress layouts generally support keyboard navigation. - Improve: Audit focus order and ensure no keyboard traps in embedded code or interactive demos. #### Contrast and readability - Present: Gutenberg Times typically offers readable contrast. - Improve: Validate 4.5:1 contrast, adjust link colors if needed, and ensure sufficient line spacing. #### Text resizing and reflow - Present: Responsive design likely supports zoom and reflow. - Improve: Test at 200–400% zoom, check for clipping, and honor prefers-reduced-motion settings. #### Media and captions - Present: Podcast episode may include basic show notes. - Improve: Provide full transcripts, captions for any videos, and avoid autoplay. #### Forms and interactions - Present: Basic email/feedback forms may exist. - Improve: Ensure clear labels, inline error messages, and large tap targets. #### Standards reference - Map issues to WCAG 2.2 AA, especially 1.4.x (contrast), 2.1.x (keyboard), 1.2.x (captions), and 3.3.x (input assistance). ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global WordPress community context, but examples mostly tool-centric. - Improve: Include case studies from diverse regions and non-English-speaking communities. #### Inclusive language - Present: Generally neutral, professional tone without exclusionary language. - Improve: Reduce jargon where possible; add plain-language summaries for complex AI topics. #### Neurodiversity support - Present: Structured headings and consistent newsletter format. - Improve: Shorter paragraphs, more bullet lists, and clear icon+text labels for sections. #### Representation - Present: Mentions contributors from different backgrounds; limited visuals in text. - Improve: Use inclusive imagery and alt text that respects diverse identities. #### Psychological safety - Present: Encouraging, non-judgmental invitations to participate and give feedback. - Improve: Link explicit community guidelines and provide clear escalation paths for issues. ### ✅ Logical Validity #### Strong reasoning - The comparison of Elementor vs Gutenberg is a strong causal argument: duplicating systems (templates, breakpoints) leads to specificity issues and fragile deactivation; a single design system (theme.json) reduces these problems. - The case for Agent Skills rests on an inductive argument: structured, maintained guidance should reduce incorrect AI code output; this follows from how LLM prompting works. #### Fallacies - None obvious; claims are largely descriptive, with clear caveats when speculative (e.g., admin reskin not guaranteed for 7.0). #### Tone of voice - Tone is conversational, optimistic, and community-oriented, with practical calls to action and appreciation for contributors. ### 🛡️ DARVO Analysis - Deny: No denial or minimization of problems; issues like design drift and Elementor conflicts are acknowledged directly. - Attack: No personal attacks; criticism is directed at tools and patterns, not individuals. - Reverse victim/offender: Not present; the article focuses on improvements and opportunities rather than blame. ## 🎯 Conclusion The article paints a picture of WordPress rapidly converging on a modern stack: block themes plus theme.json, a refreshed admin, and a growing lattice of AI capabilities (Abilities API, MCP Adapter, Agent Skills, Playground experiments). For practitioners, the practical next steps are to experiment with block themes, study theme.json, explore Playground AI features, and follow the evolving guidance around Abilities and Agent Skills—so you can build faster, safer, and more maintainable WordPress experiences. ## 🧱 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] [Block Themes, Icon Block and AI –Weekend Edition #356](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/) by [[Birgit Pauli-Haack]] via [[Gutenberg Times]]. Published 2026-02-06. > “Once understood, theme.json offers a level of granular control over what clients can and cannot do.” Two lines: context and use. Cite data if relevant. [view highlight](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [Block Themes, Icon Block and AI –Weekend Edition #356](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/) > “The WordPress project now has an official Agent Skills repository.” Two lines: context and use. [view highlight](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/#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] Theme.json centralizes WordPress design control - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[WordPress-Design-System]] [[Block-Themes]] #### [Z2] Agent Skills improve AI WordPress coding - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[AI-in-WordPress]] [[Developer-Tools]] --- ### ✏️ 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] Test AI experiments in WordPress Playground and record UX impressions — context/https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/ #fleeting #inbox - [F2] Prototype a client-friendly block theme using theme.json locking — context/https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/ #fleeting #inbox - [F3] Integrate MCP Adapter into a custom plugin and evaluate developer DX — context/https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/ #fleeting #inbox --- # 🏷️ Title: Block Themes, Icon Block and AI –Weekend Edition #356 ## 🧭 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: Roundup of recent developments in WordPress core, Gutenberg, block themes, tooling, and AI integrations, with curated links and commentary. - Why it matters: WordPress 7.0 and 6.9.x ship major editor, theme.json, and AI capabilities that will shape how sites are built and maintained. - Key stakeholders: Core and Gutenberg contributors, theme/plugin developers, site builders, hosts, and educators. - Risks and tradeoffs: Complexity of new APIs, potential instability of AI features, and transition costs from classic tooling/page builders. - Bottom line: Stay current on Gutenberg, theme.json, and emerging AI tools (Abilities API, MCP, Agent Skills) to remain effective in the modern WordPress stack. ## 📖 Main Content - Core & Gutenberg: WordPress 6.9.1 fixes 49 bugs; Gutenberg 22.5 introduces refinements like block-level Custom CSS and ongoing improvements ahead of WordPress 7.0. - Admin redesign: A “coat-of-paint” visual reskin is proposed to modernize wp-admin, align it with the WordPress Design System, and reduce inconsistency with the block editor. It’s uncertain whether it will land in 7.0. - Block themes & theme.json: Resources like a theme.json “anatomy” cheat sheet and curation guides show how theme.json centralizes design control, replaces much of legacy CSS, and lets developers lock down editing options to prevent design drift. - Plugins & tools: New and updated tools for block themes (maintenance-mode, navigation/header enhancements, layout utilities, carousels, tabs) improve no-code and low-code site building. - Gutenberg vs page builders: Johanne Courtright’s case against Elementor frames it as “a CMS inside a CMS,” arguing that Gutenberg plus theme.json offers one source of truth and fewer breakages when disabling plugins. - Icon Block: Ryan Welcher’s work on an Icon Block for core showcases real-time contribution and the crunch to land new blocks in 7.0. - AI integrations: - WordPress MCP Adapter connects the Abilities API to AI clients, enabling agents and custom AI-ready APIs. - AI progress roundup highlights an LLM client proposal for core, the Abilities API, AI micro-credentialing, WP-Bench for model benchmarking, and an AI experiments plugin. - Content Guidelines experiments aim to store and apply site-specific editorial rules directly in Gutenberg. - A new Agent Skills repository gives AI coding assistants structured guidance on building with modern WordPress APIs. - A call for testing invites feedback on multiple AI experiments in WordPress Playground, from type-ahead suggestions to AI-assisted moderation. ### 🗒️ Notes - AI framing: Birgit notes “an explosion of visible AI progress in the WordPress project,” with AI speeding research, analysis, and workflow automation. - Release cadence: WordPress 7.0 Beta 1 is under two weeks away, with WordPress 6.9.1 and Gutenberg 22.5 already shipped to stabilize and extend the editor. - Admin reskin: Fabian Kägy proposes incremental tickets (colors, buttons, inputs, notices, typography, spacing, frame) and an early Playground preview, plus a shared wp-base-styles handle for admin color schemes. - Audio resource: Gutenberg Changelog #125 covers WordPress 6.9 and Gutenberg 22.1–22.2 with JC Palmes, giving conversational context for recent changes. - Block theme tooling: - Planned Outage for Block Themes adds maintenance-mode tailored for block themes, including proper 503 handling and search engine–friendly behavior. - Groundworx Core is now a suite of four focused plugins (filters, carousels, cards/sections, tabs/accordion) plus a free Foundation plugin with responsive controls and a Gravity Forms block. - Dynamic Header & Navigation for Block Themes v1.5 fixes header flicker and offers Live Preview in the plugin directory. - Theme.json education: - Mike Davey’s cheat sheet shows how $schema enables IntelliSense, settings lock down design options, and styles generate CSS variables; block-level overrides provide granular control. - Nick Diego’s “15 ways to curate the WordPress editing experience” remains a key reference for locking down blocks, styles, editors, and external integrations. - Additional Developer Blog posts (largely by Justin Tadlock) explore common theme.json challenges with practical recipes. - Gutenberg vs Elementor: - Courtright argues Elementor duplicates WordPress concepts (templates, design tokens, breakpoints), causing specificity conflicts and brittle deactivation behavior. - Gutenberg plus theme.json centralizes design; changing a single spacing or color setting propagates globally, empowering clients to self-manage content and design. - Icon Block: - Ryan Welcher’s stream “Getting the Icon Block ready for WordPress 7.0” reveals the contribution process, time pressure, and the block’s path from plugin to core. - AI & Abilities: - Jonathan Bossenger’s article introduces the WordPress MCP Adapter, mapping Abilities to MCP tools for AI clients like Claude Desktop via STDIO/HTTP. - It also walks through client configuration and security considerations for exposing abilities as AI-ready APIs. - AI ecosystem: - James LePage’s roundup captures: LLM client proposal for 7.0, Abilities API in 6.9, MCP adapter, AI Leaders micro-credential, WP-Bench benchmarks, and an AI experiments plugin approaching 1,000 commits. - Content Guidelines for Gutenberg gives site owners a canonical place for editorial rules (tone, style, compliance) that can guide both humans and AI. - Agent Skills repository: - Centralized skills for AI coding assistants cover blocks, block themes, REST, Interactivity, Abilities, and performance; contributions are Markdown-based and can be global or per-project. - AI experiments call for testing: - Experiments include type-ahead writing suggestions, AI comment moderation, Markdown feeds for agents, expanded model providers, an AI Playground, MCP integration, and logging. - Detailed instructions and PR links invite community testing and UX feedback. - Closing: Birgit invites questions via email, WordPress Slack, Twitter, or the Gutenberg Changelog inbox, underscoring an open, conversational community loop. ## 📚 References - WordPress 6.9.1 Release Post (WordPress.org) - What’s new in Gutenberg 22.5? (Make WordPress Core) - WordPress Playground (playground.wordpress.net) - “Theme.json anatomy” cheat sheet (Delicious Brains / WP Engine) - “15 ways to curate the WordPress editing experience” (WordPress Developer Blog) - Planned Outage for Block Themes (WordPress.org/plugins) - Groundworx Core / Foundation plugins (Groundworx / WordPress.org) - Dynamic Header & Navigation for Block Themes (WordPress.org/plugins) - “From Abilities to AI Agents: Introducing the WordPress MCP Adapter” (WordPress Developer Blog) - AI experiments call for testing (Make WordPress AI / Playground) - Content Guidelines: A Gutenberg Experiment (Make WordPress AI) - WordPress Agent Skills repository (GitHub, WordPress organization) - Gutenberg Changelog #125 (Gutenberg Times podcast) ## 🗣️ Paraphrase - Paragraph A: Birgit opens by reflecting on how AI is accelerating her research and workflows, and notes that AI progress within WordPress, along with block themes and theme.json, are dominant themes in the current cycle. - Paragraph B: She then surveys recent releases (WordPress 6.9.1, Gutenberg 22.5), design and theme tooling improvements, new plugins, and the rapid build-out of AI infrastructure—Abilities API, MCP Adapter, Agent Skills, and experiments—before inviting readers to explore resources and share feedback. ## 📰 Newsletter Hey friends, This week’s WordPress world is all about cohesion: block themes, a smarter wp-admin, and a rapidly maturing AI stack. On the editor side, WordPress 6.9.1 and Gutenberg 22.5 ship bug fixes plus niceties like block-level Custom CSS. A proposed admin reskin aims to finally align wp-admin with the modern block editor and the WordPress Design System—keep an eye on whether it lands in 7.0. For theme builders, a new theme.json anatomy cheat sheet and classic posts like “15 ways to curate the WordPress editing experience” show how to lock in a design system while still giving clients safe flexibility. Supporting plugins—from Planned Outage for block themes to fresh navigation and layout tools—make no-code and low-code builds less fragile. There’s a thoughtful Gutenberg vs Elementor comparison too: when your design tokens live in theme.json, you get one source of truth and fewer “site broke when I disabled the plugin” moments. The biggest wave, though, is AI. WordPress now boasts an Abilities API, a WordPress MCP Adapter to plug into tools like Claude Desktop, a fast-growing AI experiments plugin, and even an official Agent Skills repo to teach AI coding assistants how to “speak WordPress” properly. James LePage’s roundup plus new Content Guidelines experiments in Gutenberg show how quickly AI is being woven into everyday workflows. If you’re curious where to start, try the Playground AI experiments (type-ahead suggestions, AI-assisted moderation, an AI Playground) and send feedback—the teams explicitly want real-world impressions. Until next time, happy building! ## ✅ Action Items #### DevRel - Map upcoming talks and demos to WordPress 7.0 themes: block themes, theme.json, Abilities API, and MCP Adapter usage. - Create hands-on workshops showing migration from classic themes/page builders to block themes with theme.json. - Expand sample repos and templates demonstrating best practices from the Agent Skills repository. - Publish developer-focused content (blogs, streams, short videos) walking through Icon Block contributions and AI experiments in Playground. - Run community surveys on AI features’ usability (type-ahead, moderation, content guidelines) and feed results back to core teams. - Coordinate with Docs and Training teams on unified messaging around Abilities API and MCP Adapter. #### OSPO - Document contribution guidelines for AI-related WordPress components (Abilities, MCP, Agent Skills) and clarify decision rights. - Ensure license compliance around AI integrations, especially when calling external model providers from plugins. - Establish a security review path for AI-enabled plugins (moderation, generation) including prompt injection and data exfiltration risks. - Maintain an up-to-date inventory of core AI APIs and experimental plugins, with SBOMs where relevant. - Provide office hours for teams integrating WordPress with AI agents to address policy and legal questions. - Track upstream WordPress AI roadmap to align organizational OKRs and funding. #### Community - Host roadmap clinics on block themes, theme.json, and AI experiments to help maintainers plan transitions. - Offer contributor onboarding sessions centered on Gutenberg, the Icon Block, and the Agent Skills repo. - Encourage sponsors to back AI testing sprints and documentation improvements with transparent deliverables. - Facilitate cross-project incident drills around misbehaving AI features (e.g., moderation errors) and coordinated disclosures. #### WordPress - Core: Prioritize issues that affect 7.0 readiness for the Icon Block, admin reskin, and LLM client proposal; keep performance budgets visible. - Core Performance: Profile new AI endpoints, block theme rendering paths, and block-level CSS to ensure regressions are caught early. - Core AI: Define responsible AI principles, evaluation datasets, and opt-in/opt-out controls for AI assistance in core. - Core Program Team: Align release cadence and communication around AI features, ensuring experiments are clearly labeled and documented. - Mobile: Explore how Content Guidelines and AI suggestions can surface safely in mobile editors. - Playground: Harden AI experiments, add reproducible bug templates, and create teaching modules for Abilities/MCP. - Community: Provide meetup kits that explain block themes, theme.json, and the evolving AI ecosystem. - Training: Build lesson plans around the MCP Adapter, Abilities API, and Agent Skills for both devs and power users. - Marketing: Shape narratives around “modern WordPress” that highlight block themes, design systems, and responsible AI. - Support: Update playbooks and KB articles for troubleshooting AI features and block-theme-specific issues. - Design: Audit the proposed admin reskin for consistency with the WordPress Design System and accessibility. - Documentation: Fill DevHub/HelpHub gaps on theme.json, Abilities API, MCP Adapter, and AI experiments. - Photos/TV/Openverse: Consider how Content Guidelines might integrate with media discovery and curation workflows. - Polyglots: Prepare guidance for translating AI-related UI and documentation clearly. - Accessibility: Review AI-assisted features (type-ahead, moderation UIs) against WCAG 2.2 AA; ensure keyboard and screen reader support. - Meta: Ensure .org infrastructure supports Playground AI experiments and Agent Skills discoverability. - CLI: Add commands or scaffolds for registering Abilities, configuring MCP, and setting up theme.json presets. - Hosting: Coordinate with hosts on safe defaults for AI-enabled features (rate limits, logging). - Tide: Explore including AI-related signals (e.g., safe defaults, clear permissions) in plugin quality scores. - Themes: Provide review guidance specific to block themes’ use of theme.json and AI-related settings. - Plugins: Strengthen security and provenance checks for MCP-, Abilities-, and AI-output–related plugins. #### The WPOCC - Programs: Design fellowships or stipends for maintainers focused on AI, block themes, and documentation. - Projects: Sponsor governance and documentation sprints around AI experiments and the Agent Skills repo. - Funding experiments: Pilot matched grants for AI safety work within the WordPress ecosystem, with transparent reporting. ### FAIR - Technical independence: Encourage local or self-hosted options for logging and validating AI calls from WordPress. - Policies and covenants: Clarify expectations about data use and model providers in community-funded AI projects. - Productized governance artifacts: Turn AI feature policies (e.g., Content Guidelines usage) into reusable charters and scorecards. ## 🧪 Hypotheses - H1: Developers who adopt theme.json and block themes will report fewer design-drift issues than those using classic themes or page builders. - H2: AI-assisted features in Gutenberg (type-ahead, guidelines) will increase content production speed without significantly harming quality. - H3: The Agent Skills repository will reduce incorrect code suggestions from AI coding assistants for WordPress tasks. - H4: MCP Adapter availability will accelerate third-party AI integrations into WordPress plugins. - H5: Admin reskin alignment with the WordPress Design System will improve perceived usability of wp-admin for new users. ### 📊 Methodology - For H1: Survey and compare issue trackers across block-theme projects vs classic/page-builder projects; measure frequency of CSS conflicts and support requests. - For H2: Run controlled writing experiments with and without AI suggestions, measuring time-to-publish and editorial revision rates. - For H3: Benchmark AI-generated code snippets before and after applying Agent Skills prompts on standardized WordPress tasks. - For H4: Track MCP Adapter usage metrics, plugin directory growth in AI-tagged plugins, and time-to-first-implementation for new integrations. - For H5: Conduct usability tests with prototypes of the new admin design; use SUS scores and task completion metrics. ### ❓ Questions - How will WordPress balance experimental AI features with the stability expectations of a global CMS? - What safeguards are planned for AI-generated content to avoid legal, ethical, or brand risks? - How long will classic themes and page builders remain first-class citizens as block themes mature? - Can Content Guidelines be standardized enough to support both human authors and diverse AI tools? - How will Agent Skills be maintained as core APIs evolve? ### 🔮 Future Research - Longitudinal impact of block themes and theme.json on agency workflows and support costs. - Best practices for integrating LLMs directly into WordPress core without over-committing to specific vendors. - Governance models for community-maintained AI prompts and skills (Agent Skills, MCP abilities). - Empirical studies on user trust in AI suggestions in content editing and moderation contexts. ### 💡 Implications - Practice: Agencies may shift toward block themes plus theme.json as their default build stack, with AI assistants as standard tooling. - Policy: WordPress will need clearer guidelines on AI usage, data handling, and disclosure in core and plugins. - Security: New attack surfaces appear around AI prompts, moderation, and external model calls. - Education: Training materials must cover both design-system thinking (theme.json) and AI literacy for creators and developers. - Funding: Community and organizational funding may pivot toward AI infrastructure, documentation, and safety work. ### 🧠 Learning Styles Assessment - Reading level estimate: Likely around US Grade 10–11 (Flesch–Kincaid), given technical terminology and long sentences. #### 👀 Visual learners - Present: Screenshots of Gutenberg UI (e.g., Custom CSS sidebar), plugin examples (mentioned). - Improve: Add architecture diagrams for Abilities API, MCP, and Agent Skills; before/after visuals for admin reskin and theme.json changes. #### 🔊 Aural learners - Present: Gutenberg Changelog podcast episode covering related topics. - Improve: Provide short audio summaries of each newsletter section and key tutorials. #### 🗣️ Verbal learners - Present: Explanations of concepts like theme.json, Abilities API, and MCP Adapter with concrete examples. - Improve: Add more analogies (e.g., “design system as single source of truth”) and a concise glossary. #### 🧩 Kinesthetic learners - Present: Calls to try Playground experiments, plugins, and live previews. - Improve: Provide explicit step-by-step labs and checklists for setting up theme.json, Abilities, and MCP. #### 🧠 Logical learners - Present: Structured breakdown of features and APIs, links to systematic guides. - Improve: Include tables comparing classic vs block themes, Elementor vs Gutenberg, and different AI integration paths. #### 🧑‍🤝‍🧑 Social learners - Present: Invitations to engage via Slack, email, and testing calls. - Improve: Organize cohort-based learning paths (study groups, office hours) around AI and block themes. #### 🧘‍♀️ Solitary learners - Present: Article format supports individual reading and link-following at one’s own pace. - Improve: Add reflection prompts or self-check questions at the end of sections. #### 🌿 Naturalistic learners - Present: No explicit environmental framing. - Improve: Draw analogies between ecosystems (themes, plugins, AI tools) and natural systems; highlight sustainability aspects of efficient tooling. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Likely good use of headings and landmarks via modern WordPress theme; images may have alt text. - Improve: Ensure all screenshots have descriptive alt text, and language attributes are correctly set. #### Keyboard navigation - Present: Standard WordPress layouts generally support keyboard navigation. - Improve: Audit focus order and ensure no keyboard traps in embedded code or interactive demos. #### Contrast and readability - Present: Gutenberg Times typically offers readable contrast. - Improve: Validate 4.5:1 contrast, adjust link colors if needed, and ensure sufficient line spacing. #### Text resizing and reflow - Present: Responsive design likely supports zoom and reflow. - Improve: Test at 200–400% zoom, check for clipping, and honor prefers-reduced-motion settings. #### Media and captions - Present: Podcast episode may include basic show notes. - Improve: Provide full transcripts, captions for any videos, and avoid autoplay. #### Forms and interactions - Present: Basic email/feedback forms may exist. - Improve: Ensure clear labels, inline error messages, and large tap targets. #### Standards reference - Map issues to WCAG 2.2 AA, especially 1.4.x (contrast), 2.1.x (keyboard), 1.2.x (captions), and 3.3.x (input assistance). ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global WordPress community context, but examples mostly tool-centric. - Improve: Include case studies from diverse regions and non-English-speaking communities. #### Inclusive language - Present: Generally neutral, professional tone without exclusionary language. - Improve: Reduce jargon where possible; add plain-language summaries for complex AI topics. #### Neurodiversity support - Present: Structured headings and consistent newsletter format. - Improve: Shorter paragraphs, more bullet lists, and clear icon+text labels for sections. #### Representation - Present: Mentions contributors from different backgrounds; limited visuals in text. - Improve: Use inclusive imagery and alt text that respects diverse identities. #### Psychological safety - Present: Encouraging, non-judgmental invitations to participate and give feedback. - Improve: Link explicit community guidelines and provide clear escalation paths for issues. ### ✅ Logical Validity #### Strong reasoning - The comparison of Elementor vs Gutenberg is a strong causal argument: duplicating systems (templates, breakpoints) leads to specificity issues and fragile deactivation; a single design system (theme.json) reduces these problems. - The case for Agent Skills rests on an inductive argument: structured, maintained guidance should reduce incorrect AI code output; this follows from how LLM prompting works. #### Fallacies - None obvious; claims are largely descriptive, with clear caveats when speculative (e.g., admin reskin not guaranteed for 7.0). #### Tone of voice - Tone is conversational, optimistic, and community-oriented, with practical calls to action and appreciation for contributors. ### 🛡️ DARVO Analysis - Deny: No denial or minimization of problems; issues like design drift and Elementor conflicts are acknowledged directly. - Attack: No personal attacks; criticism is directed at tools and patterns, not individuals. - Reverse victim/offender: Not present; the article focuses on improvements and opportunities rather than blame. ## 🎯 Conclusion The article paints a picture of WordPress rapidly converging on a modern stack: block themes plus theme.json, a refreshed admin, and a growing lattice of AI capabilities (Abilities API, MCP Adapter, Agent Skills, Playground experiments). For practitioners, the practical next steps are to experiment with block themes, study theme.json, explore Playground AI features, and follow the evolving guidance around Abilities and Agent Skills—so you can build faster, safer, and more maintainable WordPress experiences. ## 🧱 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] [Block Themes, Icon Block and AI –Weekend Edition #356](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/) by [[Birgit Pauli-Haack]] via [[Gutenberg Times]]. Published 2026-02-06. > “Once understood, theme.json offers a level of granular control over what clients can and cannot do.” Two lines: context and use. Cite data if relevant. [view highlight](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [Block Themes, Icon Block and AI –Weekend Edition #356](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/) > “The WordPress project now has an official Agent Skills repository.” Two lines: context and use. [view highlight](https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/#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] Theme.json centralizes WordPress design control - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[WordPress-Design-System]] [[Block-Themes]] #### [Z2] Agent Skills improve AI WordPress coding - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[AI-in-WordPress]] [[Developer-Tools]] --- ### ✏️ 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] Test AI experiments in WordPress Playground and record UX impressions — context/https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/ #fleeting #inbox - [F2] Prototype a client-friendly block theme using theme.json locking — context/https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/ #fleeting #inbox - [F3] Integrate MCP Adapter into a custom plugin and evaluate developer DX — context/https://gutenbergtimes.com/block-themes-icon-block-and-ai-weekend-edition-356/ #fleeting #inbox ---