WordPress 7.0 Field Guide  🔗 **Source:** [WordPress 7.0 Field Guide](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/) > [!note]+ Document Notes > tags: #wordpress #ai #blocks #editor #dashboard #api > author: Amy Kamala > source: Make WordPress Core > reference: https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/ > date created: 2024-12-19 15:30 > > # 🏷️ Title: WordPress 7.0 Field Guide > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Review AI integration capabilities and provider setup — assess WP AI Client implementation #ai #integration - [H1] Test new block registration patterns with PHP-only approach — validate backwards compatibility #blocks #development - [H2] Evaluate responsive editing features for client projects — test device visibility controls #responsive #design - [H2] Update plugin development workflow for Interactivity API changes — implement watch() functions #api #javascript - [H3] Configure new Connectors screen with preferred AI providers — setup Anthropic/OpenAI keys #ai #configuration ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [WordPress 7.0 Field Guide](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/) - [Make WordPress Core](https://make.wordpress.org/core/) ## 📝 Summary - WordPress 7.0 introduces comprehensive AI integration, modernized dashboard, and enhanced block editing capabilities - Major features include WP AI Client, Connectors API, responsive editing modes, and PHP-only block registration - Over 419 Core Trac tickets addressed with 76+ enhancements, 300+ bug fixes, and extensive editor improvements - Breaking changes include minimum PHP 7.4 requirement and enforced iframed editor for Block API v3+ - AI capabilities provide provider-agnostic architecture with preset models for Anthropic, Google, and OpenAI ## 📖 Main Content WordPress 7.0 represents a significant milestone with native AI integration and extensive modernization. The release centers on three core themes: AI building blocks, dashboard modernization, and enhanced developer tools. The AI integration introduces a provider-agnostic WP AI Client that handles request routing and model management through a centralized interface. The Connectors API manages authentication and provider relationships, while the Client-Side Abilities API extends functionality to JavaScript environments. Dashboard modernization includes a new "Modern" color scheme, view transitions between admin screens, and a command palette accessible via ⌘K/Ctrl+K. The iframed editor provides stability improvements when all blocks use Block API v3+. Enhanced editing capabilities include responsive block visibility controls, customizable navigation overlays, pattern-level editing modes, and visual revision comparisons. New blocks include Headings, Breadcrumbs, and enhanced Gallery with lightbox support. Developer improvements focus on PHP-only block registration, expanded Interactivity API with watch() functions, and DataViews/DataForms enhancements. Accessibility improvements address WCAG 2.2 compliance with screen reader optimizations and reduced motion preferences. ## 🗒️ Notes #### ⏱️ Introduction — [H1] Major release overview - Key idea: WordPress 7.0 includes 419+ Core Trac tickets with AI integration as flagship feature - Evidence: "Over 76 of which are enhancements and feature requests, and more than 300 bug fixes" #### ⏱️ AI Architecture — [H1] Provider-agnostic AI foundation - Key idea: WP AI Client provides central interface for generative AI models with request routing - Evidence: "Provider-agnostic architecture gives you full control over units and capabilities" #### ⏱️ WP AI Client — [H2] Core AI functionality - Key idea: Plugins communicate with AI models through standardized interface managed in Settings > Connectors - Evidence: "using_model_preference() function to indicate which models to use in order of preference" #### ⏱️ Client-Side Abilities API — [H2] JavaScript AI capabilities - Key idea: JavaScript counterpart to server-side abilities with UI, command palette, and filtering - Evidence: "Plugin developers can enqueue @wordpress/core-abilities to automatically fetch and register server-side abilities" #### ⏱️ Connectors Screen — [H2] AI provider management - Key idea: Centralized management interface for AI provider connections under Settings > Connectors - Evidence: "Includes three default providers: Anthropic, Google, and OpenAI" #### ⏱️ Connectors API — [H3] Provider integration framework - Key idea: Extensibility API supporting api_key and none authentication methods - Evidence: "Uses the WP AI Client's default registry to automatically discover providers" #### ⏱️ Modern Admin Theme — [H2] Dashboard redesign - Key idea: New Modern color scheme with refreshed palette, higher contrast, and upgraded typography - Evidence: "Clean and easy on the eyes, boasting a refreshed color palette, higher contrast" #### ⏱️ View Transitions — [H3] Smooth navigation - Key idea: Cross-document view transitions create sliding effects between wp-admin screens - Evidence: "Only activated if a preference is not set for reduced motion on the OS level" #### ⏱️ Command Palette — [H3] Quick access toolbar - Key idea: ⌘K/Ctrl+K shortcut in admin bar provides universal tool access - Evidence: "Speedruns editing and gives full control from anywhere in the dash" #### ⏱️ Visual Revisions — [H2] Enhanced revision comparison - Key idea: Side-by-side visual comparison of revisions with slider interface - Evidence: "Color indicators and sizes of changes can be seen for each location" #### ⏱️ Iframed Editor — [H2] Stability improvements - Key idea: Enforced iframe when all blocks use Block API v3+ with backwards compatibility - Evidence: "If not, the iframe is removed, upholding backwards compatibility for lower-versioned blocks" #### ⏱️ Responsive Editing — [H2] Device-specific visibility - Key idea: Customize block visibility by device type without affecting other viewports - Evidence: "Icons are displayed in List View next to blocks that have active visibility rules" #### ⏱️ PHP Block Registration — [H1] Server-side block creation - Key idea: Blocks and patterns created directly on server with automatic client-side exposure - Evidence: "When a block declares 'supports' => array( 'autoRegister' => true ) along with a render callback" #### ⏱️ Interactivity API Updates — [H3] Enhanced state management - Key idea: New watch() function subscribes to signal changes with automatic callback re-execution - Evidence: "data-wp-watch can be added to a DOM element's lifecycle and react to state changes" #### ⏱️ Accessibility Improvements — [H2] WCAG 2.2 compliance - Key idea: Password reset pre-population, screen reader text optimization, and motion preferences - Evidence: "wp_get_image_alttext() function imports Image Alt text metadata from image IPTC metadata" ## 📚 References - [WordPress 7.0 Field Guide](https://make.wordpress.org/core/2026/05/14/wordpress-7-0-field-guide/) - [WordPress Core Development](https://make.wordpress.org/core/) - [WordPress Block API Documentation](https://developer.wordpress.org/block-editor/) ## 🗣️ Paraphrase - WordPress 7.0 fundamentally transforms the platform by integrating AI capabilities directly into core, enabling plugins to communicate with various AI providers through a unified interface while maintaining flexibility in model selection and cost optimization - The dashboard experience receives comprehensive modernization with a sleek new visual design, smooth transitions between screens, and a command palette that provides instant access to tools from anywhere in the administration area - Block editing capabilities expand significantly with device-specific visibility controls, visual revision comparisons, and the ability to create blocks entirely through PHP server-side code, while maintaining backwards compatibility with existing implementations ## 📰 Newsletter 🚀 **WordPress 7.0 Brings Native AI Integration** WordPress 7.0 marks a revolutionary leap forward with built-in AI capabilities! The new WP AI Client provides a provider-agnostic interface for integrating generative AI models directly into your WordPress workflow. Set up connections to OpenAI, Anthropic, or Google through the streamlined Connectors screen. **Key Developer Benefits:** - **PHP-Only Block Registration**: Create blocks entirely on the server side with automatic client exposure - **Enhanced Interactivity API**: New watch() function for reactive state management - **Responsive Editing**: Device-specific block visibility controls - **Modern Dashboard**: Sleek new design with smooth view transitions **Getting Started:** Configure your AI providers in Settings > Connectors, explore the new Command Palette (⌘K/Ctrl+K), and test responsive editing features. The iframed editor activates automatically for Block API v3+ implementations. **Important Notes:** - Minimum PHP version increased to 7.4 - Backwards compatibility maintained for legacy blocks - WCAG 2.2 accessibility improvements included Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [Block Editor Handbook](https://developer.wordpress.org/block-editor/) ## ✅ Action Items #### DevRel - Developer advocacy: Create AI integration workshops and demos showcasing WP AI Client capabilities - Education: Develop curriculum for PHP-only block registration and Interactivity API updates - Developer experience: Update documentation for Connectors API and responsive editing features - Developer marketing: Campaign highlighting WordPress as AI-native CMS platform - Community management: Moderate discussions around AI provider preferences and implementation patterns #### WordPress - Core: Monitor performance impact of iframed editor and AI client integration - Core Performance: Profile AI request routing and caching strategies for optimal response times - Core AI: Establish evaluation sets for provider capabilities and cost optimization guidelines - Community: Create meetup content for WordPress 7.0 AI features and modernization - Training: Develop lesson plans for responsive editing and visual revision workflows - Documentation: Update DevHub with PHP block registration examples and API references - Accessibility: Audit new AI interfaces against WCAG 2.2 guidelines and screen reader compatibility - Plugins: Review security implications of AI provider integrations and establish review criteria #### Community - Maintainers: Provide migration guidance for Block API v3+ adoption and iframed editor compatibility - Contributors: Create first-issue programs for AI-related features and responsive editing enhancements - Sponsors: Evaluate funding priorities for AI infrastructure and provider relationship management ## 🧪 Hypotheses - AI integration will drive adoption among content creators seeking automated workflow assistance - PHP-only block registration will reduce JavaScript complexity and improve server-side rendering performance - Responsive editing features will increase mobile editing adoption rates - Modern dashboard design will improve user satisfaction and reduce admin bounce rates ### 📊 Methodology - Survey WordPress developers on AI integration adoption patterns and preferred providers - A/B test iframed editor performance against non-iframed implementations - Track responsive editing feature usage across different device types and user segments - Monitor dashboard navigation patterns with view transitions enabled vs disabled ### ❓ Questions - How will AI provider costs impact small site owners and hosting providers? - What security implications arise from centralized AI provider credential management? - How will the iframed editor affect plugin compatibility and custom block development? ### 🔮 Future Research - Long-term sustainability of AI provider relationships and pricing models - Integration patterns between WordPress AI capabilities and external automation tools - Performance optimization strategies for AI-enhanced content workflows ### 💡 Implications - Practice: Developers must upgrade PHP environments to 7.4+ and adapt to iframed editor constraints - Policy: AI provider agreements require transparent data handling and privacy compliance frameworks - Security: Centralized credential management introduces new attack vectors requiring enhanced protection - Education: Training programs need updating for AI workflow integration and responsive editing techniques - Funding: AI infrastructure costs may require new sustainability models for open source development ### 🧠 Learning Styles Assessment Reading level estimate: College Graduate (Grade 16-17) #### 👀 Visual learners - Present: Screenshots of Connectors screen, visual revision comparisons, command palette interface - Improve: Architecture diagrams showing AI client request flow, responsive breakpoint visualizations #### 🔊 Aural learners - Present: No audio content currently available - Improve: Video walkthroughs of AI setup process, responsive editing demonstrations #### 🗣️ Verbal learners - Present: Technical terminology defined, API method explanations, feature descriptions - Improve: Use-case scenarios, developer workflow narratives, implementation stories #### 🧩 Kinesthetic learners - Present: Code examples for PHP block registration, API usage patterns - Improve: Interactive tutorials for AI provider setup, hands-on responsive editing exercises #### 🧠 Logical learners - Present: Structured feature breakdown, API relationships, technical specifications - Improve: Decision trees for AI provider selection, performance comparison matrices #### 🧑‍🤝‍🧑 Social learners - Present: Community contributor acknowledgments, collaborative development mentions - Improve: Discussion forums for AI implementation patterns, peer code review processes #### 🧘‍♀️ Solitary learners - Present: Comprehensive documentation, self-contained code examples - Improve: Self-assessment checklists for feature adoption, independent migration guides #### 🌿 Naturalistic learners - Present: Minimal sustainability connections - Improve: AI energy consumption considerations, environmental impact of provider choices ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Proper heading hierarchy, descriptive link text for feature references - Improve: ARIA labels for complex AI interface elements, screen reader testing for new blocks #### Keyboard navigation - Present: Command palette keyboard shortcut, focus management considerations - Improve: Verify tab order through new AI screens, ensure keyboard access to responsive controls #### Contrast and readability - Present: Modern color scheme mentions higher contrast design - Improve: Verify 4.5:1 contrast ratios across new interface elements, test readability at 200% zoom #### Text resizing and reflow - Present: Responsive design considerations for block visibility - Improve: Test text scaling with AI interface elements, ensure content reflows properly #### Media and captions - Present: No multimedia content included - Improve: Add captions to future video demonstrations, provide transcripts for audio content #### Forms and interactions - Present: AI provider configuration forms, responsive editing controls - Improve: Ensure proper labels for Connectors screen inputs, accessible error handling for AI setup #### Standards reference - WCAG 2.2 compliance mentioned with specific improvements for password reset and screen reader text ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global community contributor acknowledgments from diverse backgrounds - Improve: Multi-language considerations for AI provider interfaces, international accessibility standards #### Inclusive language - Present: Technical documentation uses clear, professional terminology - Improve: Define AI-specific jargon, provide plain language summaries for complex concepts #### Neurodiversity support - Present: Structured content with clear headings, consistent navigation patterns - Improve: Cognitive load considerations for AI interface complexity, clear visual hierarchy #### Representation - Present: Diverse contributor names and perspectives acknowledged - Improve: Ensure AI use cases reflect varied user needs and contexts #### Psychological safety - Present: Professional, respectful tone throughout technical documentation - Improve: Clear guidance for new developers, supportive error messages in AI interfaces ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Technical specifications clearly derived from implementation details - Inductive strength: Feature benefits extrapolated from user workflow improvements - Causal reasoning: Performance implications linked to specific architectural changes - Analogical strength: AI integration compared to existing plugin architecture patterns #### Fallacies - Appeal to novelty: Some features presented as improvements primarily because they're new - False dichotomy: Limited discussion of alternatives to AI provider choices presented #### Tone of voice - Overall tone: Professional, technical, and comprehensive with appropriate enthusiasm for new features ### 🛡️ DARVO Analysis - Deny: No denial patterns present in technical documentation - Attack: No attacking language toward previous versions or competing platforms - Reverse victim/offender: Not applicable to technical release documentation - Emotional cues and rhetoric: Appropriate excitement for new features without manipulation ## 🎯 Conclusion WordPress 7.0 represents a foundational shift toward AI-native content management with comprehensive modernization of the editing experience. The provider <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/WordPress 7.0 Field Guide.md|WordPress 7.0 Field Guide by make.wordpress.org]] ## Highlights - WordPress 7.0 delivers an upgraded admin experience, with a sleek, new color scheme named “Modern”, numerous enhancements throughout the dashboard, and seamless visual transitions as you navigate from screen to screen. A new Command Palette shortcut in the upper admin bar lets you access tools from anywhere in the dashboard, while a new dedicated dashboard page for font management centralizes and simplifies managing fonts. The enhanced iframed post editor stabilizes the screen, while editors leave comments on blocks, receive notifications for notes and even visually compare two revision versions. ([View Highlight](https://read.readwise.io/read/01krnv4gq61ynhcc82sbdxhc1d)) - Tags: 👻 ai highlighted - Designing in WordPress 7.0 has become more flexible with the introduction of new blocks, new block supports and new design tools. A new Heading block, Icons block, Breadcrumbs block, and Playlist block with CSS inheritance are shipped with 7.0, with added lightbox support for the Gallery block, and dynamic URL support in the Navigation Link block. 7.0 includes text line indent support, text column support, dimensions width and height support, dimension presets, tools and controls, and aspect ratios for wide and full images. ([View Highlight](https://read.readwise.io/read/01krnv4gr5ezwbs3mzm053g10y)) - Tags: 👻 ai highlighted