What’s new for developers? (November 2025) 🔗 **Source:** [What’s new for developers? (November 2025)](https://developer.wordpress.org/news/2025/11/whats-new-for-developers-november-2025/) > [!note]+ Document Notes > tags: [WordPress 6.9, Gutenberg, Plugins Security] > author: WordPress Developer Blog > source: developer.wordpress.org > reference: [https://developer.wordpress.org/news/2025/11/whats-new-for-developers-november-2025/] > date created: 2025-11-11 00:00 > > # 🏷️ Title: What’s new for developers? (November 2025) > <!-- 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 nears RC1 with new blocks (Accordion, Time to Read, Term Query, Math, Comments Link/Count), a Block Processor, real-time post meta sync, admin design tokens, Playground/Studio upgrades, and Plugin Check expansion; some features punted to 7.0. State of the Word coincides with 6.9 release on Dec 2, 2025. - Why it matters: Core gains collaboration groundwork, performance and safety improvements, faster local-free dev via Playground/Studio, and stronger plugin security screening. - Key stakeholders: Core contributors, plugin/theme authors, site builders, educators, hosts. - Risks and tradeoffs: Punted features delay workflows; increased plugin scrutiny may add friction; experimental features need testing. - Bottom line: 6.9 focuses on collaboration foundations, performance, security, and dev ergonomics; plan for 7.0 for some UI/editor enhancements. ## 📖 Main Content - Core updates: - 6.9 schedule: RC1 Nov 11; final Dec 2; Dev Notes via Field Guide. - New blocks: Accordion, Time to Read (and Word Count), Term Query (+ Term Template/Name/Count), Math, Comments Link/Count. - Punted to 7.0: Enhanced Template Management, Content-only editing, updated Block Binding UI. - Block Processor: lazy, streaming parsing/manipulation to improve performance and avoid OOM. - Gutenberg: - Real-time sync for post meta in collaborative editing (enable experiment). - Admin design foundation: new theme package with design tokens; prerequisite for new Admin UI components. - PHP-only blocks (experimental) to lower JS requirements. - UX polish: Latest Comments “Display content” options; Gallery aspect ratios via theme.json; allowed blocks UI in Advanced; Heading block CSS specificity fix; experimental Breadcrumbs block (target 7.0). - Security & ecosystem: - Plugin Check Plugin expanded to screen new and updated plugins for security/compatibility/compliance; automated reports planned. - Playground & Studio: - Playground: file browser, import, panel toggles, in-instance refresh, named saved sites. - Studio: lightweight Blueprints to scaffold sites; Blueprint Gallery adds eight starter site types for teaching. - Core AI: - Abilities API server-side implementation slated for 6.9; package releases; AI Experiments plugin underway. ### 🗒️ Notes - “Release Candidate 1 will happen on November 11, 2025… final release… December 2, 2025.” - New blocks in 6.9: Accordion; Time to Read; Term Query (+ associated term blocks); Math; Comments Link/Count. - Punted to 7.0: Template Management enhancements; Content-only editing; Block Binding UI updates. - Block Processor: efficient, streaming traversal; cases include counting blocks, targeted modifications, wrapper class insertion, section extraction. - Plugin Check expansion: will screen new and updated plugins; automated security reports after update; addresses high plugin-originated vuln rate. - Real-time post meta sync (Gutenberg 22.0) for collaborative editing; includes custom blocks using post meta. - Admin design tokens land via new theme package; foundation for Admin UI components. - PHP-only blocks: pure-PHP registration lowers barrier for non-JS developers. - UX tweaks: Latest Comments content dropdown; Gallery aspect ratio control via theme.json; Advanced UI to restrict allowed blocks; Heading block CSS specificity fix. - New Math block supports LaTeX and inline math. - “Time to Read” block stabilized; supports range output and word count variant. - Experimental Breadcrumbs block (configurable home/last item/separator, styling) aimed at 7.0. - Playground: in-browser file ops, UI polish, preserved state refresh, named sites. - Studio: Blueprints for standard setups; plus eight classroom-ready Playground blueprints. - Core AI: Abilities API in 6.9; AI packages released; AI Experiments plugin to unify features. - State of the Word livestream on Dec 2, 2025, same day as 6.9 release. ## 📚 References - WordPress 6.9 Field Guide (when published): https://make.wordpress.org/core/ - Update on Phase 3 collaboration (Nov 2025): https://make.wordpress.org/core/ - Plugin Check Plugin announcement: https://make.wordpress.org/plugins/ - Gutenberg 22.0 release highlights: https://make.wordpress.org/core/tag/gutenberg/ - PHP‑only blocks discussion: https://github.com/WordPress/gutenberg/issues - WordPress Playground updates: https://make.wordpress.org/playground/ - WordPress Studio & Blueprints: https://github.com/wordpress/wordpress-playground ## 🗣️ Paraphrase - Paragraph A: The 6.9 cycle is wrapping toward RC1 and final release, with Dev Notes and a Field Guide to brief developers on changes. - Paragraph B: Beyond core, Gutenberg brings collaboration and admin foundations; Playground/Studio streamline development; security tightens via automated plugin checks. ## 📰 Newsletter - WordPress 6.9 ships Dec 2 alongside State of the Word. Expect new blocks (Accordion, Math, Time to Read), a high‑performance Block Processor, and collaboration groundwork. Gutenberg 22.0 adds real‑time post meta sync and admin design tokens. Plugin Check now scans new and updated plugins to curb security issues. Playground’s new file browser and WordPress Studio Blueprints make zero‑install dev and teaching smoother. Explore PHP‑only blocks to lower the entry barrier. Keep an eye on the Abilities API and the upcoming AI Experiments plugin. ## ✅ Action Items #### DevRel - Publish 6.9‑ready demos for new blocks and Block Processor use cases; run office hours on PHP‑only blocks. - Update code samples for admin design tokens; record a Playground file browser quickstart. - Author migration notes for features punted to 7.0; set expectations. #### OSPO - Align internal plugin release checks with Plugin Check outputs; define remediation SLAs. - Add SBOM and vulnerability triage steps for Composer AI packages. #### Community - Host contributor sessions on collaboration features; run “first issue” on Block Processor bugs. - Create teaching kits using Playground starter Blueprints. #### WordPress - Core: prioritize collaboration stability; triage Block Processor edge cases. - Performance: benchmark Block Processor vs legacy parsing; set perf budgets. - Core AI: draft Abilities API Dev Note + examples; evaluate AI Experiments plugin scope. - Playground: build reproducible bug labs; add education modules. - Documentation: expand DevHub for new blocks, theme.json aspect ratios, allowed‑blocks UI. - Accessibility: audit new admin tokens/components early. - Plugins: integrate Plugin Check pre‑submit; document compliance fixes. #### The WPOCC - Fund maintainer time for Plugin Check rules and Playground education. ### FAIR - Require provenance for AI/Playground artifacts; publish funding transparency and sunset clauses for experiments. ## 🧪 Hypotheses - Expanding Plugin Check will reduce plugin‑origin vulnerabilities quarter‑over‑quarter. - The Block Processor lowers server memory spikes on large posts by ≥30%. - PHP‑only blocks increase first‑time block authors by ≥20% within two releases. - Real‑time post meta sync reduces collaborative editing conflicts by ≥40%. ### 📊 Methodology - Compare vuln reports pre/post rollout; segment by plugin age/version. - Load-test parsing on large content sets; measure memory/time deltas. - Track npm/PHP package downloads, tutorial completions, and block submissions. - Instrument collaboration logs for conflict frequency and resolution time. ### ❓ Questions - Which plugin checks will be blocking vs advisory? - What is the deprecation path for legacy parsing once Block Processor stabilizes? - How will Abilities API permissions map to roles/capabilities? ### 🔮 Future Research - Formal evaluation of collaboration latency and conflict resolution UX. - Cross‑host telemetry for Plugin Check false positives. - Blueprint standardization for enterprise scaffolds. ### 💡 Implications - Practice: safer plugin updates; faster in‑browser dev loops. - Policy: clearer submission criteria and automated compliance. - Security: earlier detection of high‑risk patterns in plugins. - Education: turnkey curricula via Playground Blueprints. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch–Kincaid ≈ Grade 10–11. #### 👀 Visual learners - Present: screenshots, code examples. - Improve: architecture and data flow diagrams for collaboration and Block Processor. #### 🔊 Aural learners - Present: State of the Word livestream. - Improve: 3–5 minute audio briefs for Dev Notes. #### 🗣️ Verbal learners - Present: glossary‑like block/feature summaries. - Improve: analogies for Block Processor and Abilities API. #### 🧩 Kinesthetic learners - Present: Playground labs, Studio Blueprints. - Improve: step‑by‑step checklists and reproducible tasks. #### 🧠 Logical learners - Present: feature lists and issue links. - Improve: decision trees for when to use each API. #### 🧑‍🤝‍🧑 Social learners - Present: contributor discussions. - Improve: cohort study groups and mentored sprints. #### 🧘‍♀️ Solitary learners - Present: posts and Dev Notes. - Improve: self‑check quizzes and reflection prompts. #### 🌿 Naturalistic learners - Improve: lifecycle/impact framing for tooling and hosting efficiency. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: headings; landmarks implied. - Improve: consistent alt text for screenshots; explicit lang attributes. #### Keyboard navigation - Present: logical reading order. - Improve: verify focus states and skip links in demo pages. #### Contrast and readability - Present: generally adequate. - Improve: confirm 4.5:1 contrast in new admin tokens. #### Text resizing and reflow - Present: responsive layouts. - Improve: motion preferences and 200% zoom checks in new UI. #### Media and captions - Present: livestream captions expected. - Improve: downloadable transcripts, audio descriptions. #### Forms and interactions - Present: standard components. - Improve: inline validation patterns for new Admin UI components. #### Standards reference - Map gaps to WCAG 2.2 AA: 1.4.3, 1.2.x, 2.4.7, 3.3.x. ### 🌍 DEIB Assessment #### Cultural breadth - Present: global community context. - Improve: link to multilingual resources and non‑US case studies. #### Inclusive language - Present: neutral tone; defined terms. - Improve: plain‑language summaries for advanced features. #### Neurodiversity support - Present: consistent structure. - Improve: chunking, icon+text patterns, predictable navigation. #### Representation - Improve: diverse imagery and examples. #### Psychological safety - Present: respectful framing. - Improve: clear community guidelines and moderated Q&A links. ### ✅ Logical Validity #### Strong reasoning - Inductive: plugin vulnerabilities → increase checks; plausible causal path with expected ecosystem benefit. - Causal: streaming Block Processor → less memory usage; aligns with known parsing costs. #### Fallacies - Potential hasty generalization: “96%” stat implies tool will “make the web a better place.” Suggest quantifying expected reduction and timelines. #### Tone of voice - Informative, optimistic, and action‑oriented. ### 🛡️ DARVO Analysis - No denial, attack, or role reversal patterns detected; content is technical and updates‑focused. ## 🎯 Conclusion - Bottom line: 6.9 prioritizes collaboration groundwork, safer plugins, performance, and smoother dev workflows; some UI features move to 7.0. - Next steps: Test RC1, adopt Plugin Check in pipelines, try PHP‑only blocks, pilot Playground/Studio Blueprints, and review Dev Notes/Field Guide before Dec 2. ## 🧱 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] {Title or entity} ({ARTICLE_URL}) by [{Author or [MISSING]}] via [{Site or [MISSING]}]. Published {DATE_OR_[MISSING]}. Accessed . > “Short quote, verbatim, ≤25 words.” Two lines: context and use. Cite data if relevant. [view highlight]({ARTICLE_URL}#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] {Title or entity} ({ARTICLE_URL}) > “Short quote, verbatim, ≤25 words.” Two lines: context and use. [view highlight]({ARTICLE_URL}#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: H4. - Each item: one idea, present tense, specific, testable. #### [Z1] 5–10-word present-tense claim - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Parent-Concept]] [[Related-Idea]] #### [Z2] 5–10-word present-tense claim - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Parent-Concept]] [[Related-Idea]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: Select one line → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Short action — context/{ARTICLE_URL} #fleeting #inbox - [F2] Short action — context/{ARTICLE_URL} #fleeting #inbox - [F3] Short action — context/{ARTICLE_URL} #fleeting #inbox --- <!-- deep-read:sections end -->