WordPress 6.9 Field Guide  ## Metadata - Author: [[Make WordPress Core]] - Full Title: WordPress 6.9 Field Guide - Category: #articles - Document Note: --- tags: [WordPress 6.9, Block Editor, Developer Features] author: Make WordPress Core source: Make WordPress reference: [https://make.wordpress.org/core/2025/11/25/wordpress-6-9-field-guide/] date created: 2025-11-25 00:00 --- # 🏷️ Title: WordPress 6.9 Field Guide ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: WordPress 6.9 RC introduces major developer features, collaboration tools, performance work, and breaking changes. - Why it matters: Prepares extenders for API updates, Editor improvements, and the iframe-based editor path to 7.0. - Key stakeholders: Core and plugin/theme developers, site builders, editors, hosts. - Risks and tradeoffs: Block apiVersion migration, iframe sandboxing impacts, validation changes in Field/Data components. - Bottom line: Start testing apiVersion 3, Notes, DataViews/DataForms, and admin-wide Command Palette ahead of 7.0. ## 📖 Main Content - Scope: 400+ Core tickets (125+ enhancements, 250+ fixes) and 440+ Editor enhancements with 570+ fixes. - Collaboration: Block-level Notes enable threaded feedback with resolve/edit/delete and email notifications to authors. See “Notes” section. - Admin ergonomics: Optimized DataViews, Command Palette across wp-admin, improved modals, text actions, infinite scroll. - Field/Data components: Field API expands with 10+ field types, 11+ edit controls with validation, 16+ filter operators, user-input filters, readOnly support; DataForms gains improved panel, new card/row layouts, controlled validation; DataViews persists via @wordpress/views and supports custom child layouts with internal state/data handling. - Editing/architecture: Easier drag-and-drop, one-click hide blocks, and a new WP_Block_Processor to convert documents into block structures; continued iframe integration for page architecture. - Iframe migration: New/updated blocks must use block.json apiVersion 3; console warns on apiVersion 1/2; full editor iframe planned for 7.0—developers should test and update. - Highlights: Accessibility fixes, dark mode toolbar colors, new blocks, Command Palette everywhere in admin, Global Styles palette tweaks, and Abilities API roadmap. ### 🗒️ Notes - “This guide outlines major developer features and breaking changes in 6.9… over 125… more than 250 bug fixes… 35+ tickets focused on the Editor…” ([release scale](https://read.readwise.io/read/01kaxxxtz2bh49szv6qb0fnzj8?endLexposition=00008_00000_00000-000H&startLexposition=00000&emphasizeText=There+are+more+than+400+Core+Trac+tickets+included+in+WordPress+6.9)) - “Users can now add notes to blocks… optimized DataViews and a command palette implemented across wp-admin.” ([collaboration tools](https://read.readwise.io/read/01kaxxxtz2bh49szv6qb0fnzj8?endLexposition=0000C_00006-0001&startLexposition=0000A&emphasizeText=Users+can+now+add+notes+to+blocks)) - “Editors can write notes and reply… Notes can be resolved, edited, deleted, and email notifications are sent…” ([Notes behavior](https://read.readwise.io/read/01kaxxxtz2bh49szv6qb0fnzj8?endLexposition=0000G_00000-0051&startLexposition=0000E&emphasizeText=Notes+can+be+resolved%2C+edited%2C+deleted%2C+and+email+notifications+are+sent)) - Field/Data updates: more field types, edit controls with validation, filter operators; DataViews persistence via @wordpress/views; DataForms layouts and validation. ([Field/Data updates](https://read.readwise.io/read/01kaxxxtz2bh49szv6qb0fnzj8?endLexposition=0000M_0000K-0011&startLexposition=0000I&emphasizeText=field+type+has+been+expanded+to+include+more+than+10+new+field+types)) - Editing/architecture: drag/drop, hide blocks, WP_Block_Processor, ongoing iframe integration. ([editing tools](https://read.readwise.io/read/01kaxxxtz2bh49szv6qb0fnzj8?endLexposition=0000Q_00006-0001&startLexposition=0000O&emphasizeText=use+the+new+WP_Block_Processor+class+to+convert+documents+into+a+block+structure)) - Iframe migration: apiVersion 3 only for new/updated blocks; console warnings for v1/v2; plan to fully iframe in 7.0. ([iframe plan](https://read.readwise.io/read/01kaxxxtz2bh49szv6qb0fnzj8?endLexposition=0000p&startLexposition=0000e&emphasizeText=The+block.json+schema+now+only+allows+apiVersion+3+for+new+or+updated+blocks)) - “More than 250 bugs, 123 enhancements… highlights: Command Palette everywhere, new blocks, dark mode toolbar colors, Global Styles palette move, accessibility fixes.” ([more highlights](https://read.readwise.io/read/01kaxxxtz2bh49szv6qb0fnzj8?endLexposition=00012_00000_00000_00000-002j&startLexposition=0000u&emphasizeText=6.9+offers+so+much+more%21+More+than+250+bugs)) ## 📚 References - WordPress 6.9 Field Guide (Make/Core) (https://make.wordpress.org/core/2025/11/25/wordpress-6-9-field-guide/) - Gutenberg repo (https://github.com/WordPress/gutenberg) - Block API versions (https://developer.wordpress.org/block-editor/reference-guides/block-api/block-metadata/#api-version) - WP Block Editor Handbook (https://developer.wordpress.org/block-editor/) ## 🗣️ Paraphrase - Paragraph A: 6.9 aggregates hundreds of core and editor changes, emphasizing developer-impacting updates and performance. - Paragraph B: Collaboration improves via block-level Notes, admin-wide Command Palette, and upgraded Field/Data components. ## 📰 Newsletter WordPress 6.9 RC lands with block-level Notes for threaded feedback, admin-wide Command Palette, and big upgrades to Field API, DataViews, and DataForms. Devs should migrate blocks to apiVersion 3 as the editor moves fully into an iframe for 7.0. Plus: new blocks, dark-mode toolbar colors, and accessibility fixes. Start testing now so your plugins/themes shine on day one. More: Make/Core’s 6.9 Field Guide. ## ✅ Action Items #### DevRel - Publish migration guide for apiVersion 3; live demo Notes and Command Palette; track adoption metrics. - Run workshops on Field/DataForms validation and DataViews persistence. - Create quickstarts/templates for WP_Block_Processor transformations. #### OSPO - Update contribution guidelines for 6.9/7.0 iframe roadmap. - Refresh license/compliance scans for new Editor dependencies. - Review vulnerability intake for iframe boundary changes. #### Community - Host contributor onboarding focused on Editor/Field API changes. - Pairing sessions for block apiVersion upgrades. #### WordPress - Core: finalize iframe readiness checks; performance budgets for Editor. - Core Performance: profile drag/drop and DataViews infinite scroll. - Core AI: N/A (monitor Abilities API exploration). - Core Program Team: coordinate Editor and Docs teams for 7.0 migration. - Playground: add apiVersion upgrade labs and iframe testbeds. - Training: lessons on Notes, DataViews/DataForms, WP_Block_Processor. - Marketing: highlight collaboration features; migration timeline content. - Support: prepare KB on console warnings for apiVersion 1/2. - Documentation: update block.json schema docs; Field/Data components. - Accessibility: verify dark mode toolbar contrast, submenu Escape fix. - Meta: ensure .org plugin checks warn on apiVersion <3. - CLI: add scaffolds defaulting to apiVersion 3; lint rules. - Hosting: test iframe editor across common MU/security configs. - Tide: incorporate apiVersion signals; reduce false positives on new fields. #### The WPCC - Fund audits for iframe editor compatibility; microgrants for migration tooling. ### FAIR - Independence: attest block metadata versions; signed releases. - Policies: migration covenants and sunset timelines for old APIs. - G - Summary: This guide outlines major developer features and breaking changes in 6.9 and is published in the Release Candidate phase to help inform WordPress extending developers, Core developers, and others. … - URL: https://make.wordpress.org/core/2025/11/25/wordpress-6-9-field-guide/ This guide outlines major developer features and breaking changes in 6.9 and is published in the Release Candidate phase to help inform *WordPress extending developers, Core developers, and others*. There are more than [400 Core Trac tickets](https://core.trac.wordpress.org/query?status=closed&milestone=6.9&group=component&col=id&col=summary&col=type&col=priority&order=priority&max=500) included in WordPress 6.9, [over 125 of which are enhancements and feature requests](https://core.trac.wordpress.org/query?status=closed&type=enhancement&type=feature+request&milestone=6.9&group=component&max=200&col=id&col=summary&col=type&col=status&col=milestone&col=owner&col=priority&order=priority), and [more than 250 bug fixes](https://core.trac.wordpress.org/query?status=closed&type=defect+(bug)&milestone=6.9&group=component&max=500&col=id&col=summary&col=type&col=status&col=milestone&col=owner&col=priority&order=priority). This release includes [35+ tickets focused on the Editor](https://core.trac.wordpress.org/query?status=closed&component=Editor&milestone=6.9&col=id&col=summary&col=status&col=milestone&col=owner&col=type&col=priority&order=priority), [15 tickets focused on wp-admin](https://core.trac.wordpress.org/query?component=Administration&milestone=6.9&or&focuses=~administration&milestone=6.9&group=component&col=id&col=summary&col=milestone&col=owner&col=type&col=status&col=priority&order=priority), and [over 45 tickets focused on performance](https://core.trac.wordpress.org/query?status=closed&focuses=~performance&milestone=6.9&or&status=closed&component=Script+Loader&milestone=6.9&or&status=closed&component=Query&milestone=6.9&group=component&col=id&col=summary&col=status&col=milestone&col=owner&col=type&col=priority&order=priority). Additionally, this release includes [440 enhancements](https://github.com/WordPress/gutenberg/issues?q=(label%3A%22%5BType%5D%20Enhancement%22%20AND%20is%3Aclosed)%20AND%20(milestone%3A%22Gutenberg%2020.4%22%20OR%20milestone%3A%22Gutenberg%2020.5%22%20OR%20milestone%3A%22Gutenberg%2020.6%22%20OR%20milestone%3A%22Gutenberg%2020.7%22%20OR%20milestone%3A%22Gutenberg%2020.8%22%20OR%20milestone%3A%22Gutenberg%2020.9%22%20OR%20milestone%3A%22Gutenberg%2021.0%22%20OR%20milestone%3A%22Gutenberg%2021.1%22%20OR%20milestone%3A%22Gutenberg%2021.2%22%20OR%20milestone%3A%22Gutenberg%2021.3%22%20OR%20milestone%3A%22Gutenberg%2021.4%22%20OR%20milestone%3A%22Gutenberg%2021.5%22%20OR%20milestone%3A%22Gutenberg%2021.6%22%20OR%20milestone%3A%22Gutenberg%2021.7%22%20OR%20milestone%3A%22Gutenberg%2021.8%22%20OR%20milestone%3A%22Gutenberg%2021.9%22%20OR%20milestone%3A%22Gutenberg%2022.0%22%20OR%20milestone%3A%22Gutenberg%2022.1%22)) and [more than 570 bug fixes](https://github.com/WordPress/gutenberg/issues?q=(label%3A%22%5BType%5D%20Bug%22%20AND%20is%3Aclosed)%20AND%20(milestone%3A%22Gutenberg%2020.4%22%20OR%20milestone%3A%22Gutenberg%2020.5%22%20OR%20milestone%3A%22Gutenberg%2020.6%22%20OR%20milestone%3A%22Gutenberg%2020.7%22%20OR%20milestone%3A%22Gutenberg%2020.8%22%20OR%20milestone%3A%22Gutenberg%2020.9%22%20OR%20milestone%3A%22Gutenberg%2021.0%22%20OR%20milestone%3A%22Gutenberg%2021.1%22%20OR%20milestone%3A%22Gutenberg%2021.2%22%20OR%20milestone%3A%22Gutenberg%2021.3%22%20OR%20milestone%3A%22Gutenberg%2021.4%22%20OR%20milestone%3A%22Gutenberg%2021.5%22%20OR%20milestone%3A%22Gutenberg%2021.6%22%20OR%20milestone%3A%22Gutenberg%2021.7%22%20OR%20milestone%3A%22Gutenberg%2021.8%22%20OR%20milestone%3A%22Gutenberg%2021.9%22%20OR%20milestone%3A%22Gutenberg%2022.0%22%20OR%20milestone%3A%22Gutenberg%2022.1%22)) for the Block Editor, Site Editor, DataViews, and other related Core APIs. Below is a breakdown of the most important developer-related changes included in WordPress 6.9. **Table of contents** #### New Ways to Collaborate Creating and managing content with WordPress 6.9 is more versatile, with new tools and features that encourage collaboration and increase the ease of use. Users can now add [notes](https://github.com/WordPress/gutenberg/issues/66377) to blocks, and can take advantage of optimized DataViews and a [command palette](https://github.com/WordPress/gutenberg/issues/58218) implemented [across wp-admin](https://github.com/WordPress/gutenberg/pull/71030). ##### Notes In WordPress 6.9 editors can write notes and reply to others directly at the individual block level, allowing teams to collaborate, track changes, and provide feedback during the editing process. Notes can be resolved, edited, deleted, and email notifications are sent to the post author when a new one is left. ##### Updates to Field API, DataViews and DataForms Components This release also comes with upgrades to the Field API as well as the DataViews and DataForms components. In the [Field API](https://make.wordpress.org/core/2025/11/11/dataviews-dataform-et-al-in-wordpress-6-9/#field-api) the field `type` has been expanded to include more than 10 new field types, 11+ `edit` controls that support validation, over 16 filter operators and user-input filters in `filterBy`, `readOnly` options to disable field editing, and so much more. Updated [DataViews](https://make.wordpress.org/core/2025/11/11/dataviews-dataform-et-al-in-wordpress-6-9/#dataviews) functions include improvements to modals and text-based `actions`, infinite scroll, and the ability to build custom layouts with `children` that leverage DataViews’ internal state management and data handling logic. DataViews also now persists via [`@wordpress/views`](https://make.wordpress.org/core/2025/11/11/dataviews-dataform-et-al-in-wordpress-6-9/#dataviews-persistence) while DataForms now has an improved `panel`, new card and row layouts, and revamped controlled validation. #### Improved Editing Tools and Architecture WordPressers can now drag and drop blocks more easily, [hide](https://github.com/WordPress/gutenberg/issues/50756) blocks with a click, and use the new `WP_Block_Processor` class to convert documents into a block structure, while page architecture is improved with the continued integration of `iframes`. ##### Direct Drag and Drop [Drag and drop](https://make.wordpress.org/core/2025/10/28/gutenberg-21-9-october-22/#direct-drag-and-drop) has been improved, with the ability to [directly move blocks around](https://github.com/WordPress/gutenberg/pull/67470) within the site editor instead of a drag chip, for a faster, easier, and more intuitive editing experience. ##### Ability to Hide Blocks WordPress 6.9 allows editors to hide and reveal blocks with a simple click. ##### Iframe Integration in Post Editor As [part of an ongoing initiative](https://make.wordpress.org/core/2021/06/29/blocks-in-an-iframed-template-editor/) to move the post editor into an `iframe`, a few changes have been made to help with this transition: 1. The [block.json schema](https://github.com/WordPress/gutenberg/blob/trunk/schemas/json/block.json) now only allows`apiVersion` `3` for new or updated blocks. 2. A warning will be displayed in the browser console when a block is registered using`apiVersion` `1` or `2`. These changes aim to help developers migrate their blocks to use `apiVersion` 3 with the plan to fully place the editor within an `iframe` in WordPress 7.0. While this change has been researched and tested at length, additional testing is needed by block and plugin developers to make any necessary improvements in future releases.  #### New & Improved APIs #### AI-related Work Alongside 6.9 #### But wait, there is more! 6.9 offers so much more! More than [250](https://core.trac.wordpress.org/query?status=closed&type=defect+(bug)&milestone=6.9&group=component&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version&order=priority) bugs, [123](https://core.trac.wordpress.org/query?status=closed&type=enhancement&type=feature+request&milestone=6.9&group=component&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version&order=priority) enhancements and feature requests, and [22](https://core.trac.wordpress.org/query?status=closed&type=task+(blessed)&milestone=6.9&group=component&col=id&col=summary&col=type&col=owner&col=priority&col=component&col=version&order=priority) blessed tasks have been [marked as fixed in WordPress 6.9](https://core.trac.wordpress.org/query?status=closed&milestone=6.9&group=component&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority). Below are a few more to highlight: * Abilities API: Roadmap to WP 6.9: defining and deciding ([AI-83](https://github.com/WordPress/abilities-api/issues/83)) * Accessibility: Navigation block: fix submenu Escape key behavior ([GB-69834](https://github.com/WordPress/gutenberg/issues/69834)) * Editor: Button Block: Add HTML Element selection in Advanced settings (Accessibility) ([GB-70139](https://github.com/WordPress/gutenberg/pull/70139)) * Editor: Enable the Command Palette everywhere in admin dashboard ([GB-58218](https://github.com/WordPress/gutenberg/issues/58218)) * Editor: New block additions for the Block Library ([GB-71026](https://github.com/WordPress/gutenberg/issues/71026)) * Editor: Toolbar: Adjust colors for dark mode support ([GB-66454](https://github.com/WordPress/gutenberg/issues/66454)) * General: Replace deprecated / non-standard CSS for `speak` and `aural` (accessibility) ([GB-63603](https://github.com/WordPress/gutenberg/pull/63603)) * Global Styles: Move `Randomize colors` button to Edit Palette panel ([GB-66169](https://github.com/WordPress/gutenberg/issues/66169)) ***Thank you to everyone who contributed to this version of WordPress, whether through code, testing, or something else – your contributions matter and help Make WordPress.***, WordPress 6.9 Field Guide, Make WordPress Core, 01kaxxxtz2bh49szv6qb0fnzj8.