WordPress 6.9 Field Guide 🔗 **Source:** [WordPress 6.9 Field Guide](https://make.wordpress.org/core/2025/11/25/wordpress-6-9-field-guide/) > [!note]+ Document Notes > 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 > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: WordPress 6.9 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 WPOCC - 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. - Governance artifacts: apiVersion scorecards; iframe-readiness checklists. ## 🧪 Hypotheses - Mandating apiVersion 3 reduces editor breakages by ≥20% in 6.9–7.0. - Block-level Notes increase multi-user editorial throughput by ≥15%. - DataViews persistence lowers admin navigation time by ≥10%. - WP_Block_Processor simplifies legacy-to-block conversions with fewer errors. ### 📊 Methodology - A/B test editorial teams with/without Notes and Command Palette. - Telemetry on editor errors pre/post apiVersion 3 migration. - Task-timed studies for DataViews navigation and drag/drop flows. ### ❓ Questions - What edge cases break under iframe sandboxing? - How will Abilities API intersect with capability checks? - What is the deprecation window for apiVersion 1/2 in 7.0? ### 🔮 Future Research - Programmatic conversion pipelines using WP_Block_Processor at scale. - Validation patterns for complex Field/DataForms schemas. ### 💡 Implications - Practice: update scaffolds and CI to enforce apiVersion 3. - Policy: communicate 7.0 iframe deadlines early. - Security: audit postMessage/iframe boundaries. - Education: create migration labs and checklists. ### 🧠 Learning Styles Assessment - Reading level: Flesch-Kincaid Grade ≈ 10–11. #### 👀 Visual learners - Present: none prominent. - Improve: diagrams of iframe architecture, DataViews flows. #### 🔊 Aural learners - Present: none. - Improve: 3–5 min audio summary. #### 🗣️ Verbal learners - Present: concise feature lists. - Improve: glossary for Field/Data terms. #### 🧩 Kinesthetic learners - Present: N/A. - Improve: hands-on migration exercises. #### 🧠 Logical learners - Present: structured sections. - Improve: decision trees for apiVersion upgrades. #### 🧑‍🤝‍🧑 Social learners - Present: community thanks. - Improve: guided cohort testing. #### 🧘‍♀️ Solitary learners - Present: scannable bullets. - Improve: self-check quizzes. #### 🌿 Naturalistic learners - Improve: lifecycle/deprecation timeline visuals. ### 📊 Accessibility Assessment #### Screen reader semantics - Improve: ensure headings/landmarks in docs pages. #### Keyboard navigation - Improve: focus states and skip links in examples. #### Contrast and readability - Present: dark mode toolbar color adjustments (noted). #### Text resizing and reflow - Improve: confirm 200% zoom behavior in editor panels. #### Media and captions - Improve: add captions to demo videos if any. #### Forms and interactions - Improve: accessible validation messaging in DataForms examples. #### Standards reference - Map to WCAG 2.2 AA for editor/admin patterns. ### 🌍 DEIB Assessment - Cultural breadth: Improve multilingual examples for Notes and DataViews. - Inclusive language: Mostly neutral; add plain-language summaries. - Neurodiversity: Improve consistent icon+text labels in UI examples. - Representation: Include diverse use cases and screenshots. - Psychological safety: Clear community guidelines for collaboration features. ### ✅ Logical Validity #### Strong reasoning - Causal: apiVersion 3 + iframe path → improved isolation and predictability; supported by migration warnings. #### Fallacies - None apparent; claims framed as plans and highlights. #### Tone of voice - Informative, appreciative, and action-oriented. ### 🛡️ DARVO Analysis - Not applicable; no adversarial framing. ## 🎯 Conclusion - Bottom line: 6.9 advances collaboration, data tooling, and sets the stage for a fully iframed editor in 7.0; migrate to apiVersion 3 and test now. - Next steps: Audit blocks for apiVersion, test Notes/DataViews/DataForms, validate admin Command Palette usage, and profile performance. ## 🧱 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] Iframe editor requires apiVersion 3 > [!quote] [WordPress 6.9 Field Guide](https://make.wordpress.org/core/2025/11/25/wordpress-6-9-field-guide/) by [[Make WordPress Core]] via [[Make WordPress]]. Published 2025-11-25. Accessed 2025-11-25. > “The block.json schema now only allows apiVersion 3 for new or updated blocks.” Two lines: migration necessity; test ahead of 7.0 full iframe. [view highlight](https://read.readwise.io/read/01kaxxxtz2bh49szv6qb0fnzj8?endLexposition=0000p&startLexposition=0000e#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] Block-level Notes enable collaboration > [!quote] [WordPress 6.9 Field Guide](https://make.wordpress.org/core/2025/11/25/wordpress-6-9-field-guide/) > “Editors can write notes and reply to others directly at the individual block level.” Two lines: editorial throughput; feedback workflows. [view highlight](https://read.readwise.io/read/01kaxxxtz2bh49szv6qb0fnzj8?endLexposition=0000G_00000-0051&startLexposition=0000E#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] apiVersion 3 reduces editor breakage - Applies during 6.9–7.0 migration window. - Pointer: Field Guide iframe section. - Links: [[Block-API]] [[Editor-Iframe]] #### [Z2] Notes increase multi-user editorial speed - Applies to teams using block-level Notes. - Pointer: Notes section. - Links: [[Collaboration]] [[Editorial-Workflow]] --- ### ✏️ Fleeting Queue (Extract by Selection) - [F1] Audit all blocks for apiVersion 3—https://make.wordpress.org/core/2025/11/25/wordpress-6-9-field-guide/ #fleeting #inbox - [F2] Prototype WP_Block_Processor conversion on legacy content—https://make.wordpress.org/core/2025/11/25/wordpress-6-9-field-guide/ #fleeting #inbox - [F3] Test DataViews persistence and infinite scroll in large sites—https://make.wordpress.org/core/2025/11/25/wordpress-6-9-field-guide/ #fleeting #inbox --- <!-- deep-read:sections end -->