# WordPress Platform Design MOC ## Synthesis additions (2026-10-18 — the MCP adapter as a production surface) - [[3. Resources/Readwise/Articles/The WordPress MCP Adapter Is Ready for Production. Is Your Site Ready for It|The WordPress MCP Adapter Is Ready for Production. Is Your Site Ready for It?]] — WebDevStudios post (Brad Williams): the adapter doesn't decide what an agent can do, the site does. 'Production ready' is the agency's framing; the only adapter link is the directory listing, and the agency sells the readiness and lockdown services it recommends. - [[3. Resources/Readwise/Articles/How to Connect Claude AI to WordPress Using MCP|How to Connect Claude AI to WordPress Using MCP (live demo)]] — WebDevStudios demo from 2026-03-13 (seven months old, so details may have changed): a contributor-role user with an application password on a live site; the transcript names no other guardrails. ## Synthesis additions (2026-10-16 — core feature projects: status and contribution entry points) - [[3. Resources/Readwise/Articles/WP Feature Notifications Weekly Update 2026-10-16]] — Make WordPress Core, first in a weekly series: the 0.3.0 MVP is 16 open issues in tracker #302, 30+ Dependabot security PRs need review, and office hours restart Thursday 2026-10-22 (04:00 PDT) in #feature-notifications. Byline not in the capture; no release date given. ## Synthesis additions (2026-10-01 — agent-facing contracts: WebMCP, WebSkill, and WordPress Abilities) - [[3. Resources/Readwise/Articles/Bringing WordPress AI to the Market]] — briancoords.com opinion post proposes a WordPress AI go-to-market built on outside-in agentic site management: a Core Abilities plugin, MCP as the canonical protocol, and external agent access ranked above dashboard AI. - [[3. Resources/Readwise/Articles/Recap of the Web & AI International Standards Seminar Generative UI and WebSkill]] — W3C Shenzhen office recap of a 2026-09-06 seminar: speakers say the web is becoming an action space for AI agents, with WebMCP and WebSkill emerging in parallel, neither a W3C standard. ## Synthesis additions (2026-10-01 — WordPress runtime and platform releases) - [[3. Resources/Readwise/Articles/What's New in PHP 8.6]] — Laravel News previews PHP 8.6, due 2026-11-19: partial function application, clamp(), a Time\Duration class, a polling API, secure session defaults; the capture drops code blocks and the session-defaults list. - [WP Tavern Podcast 235 – Rob Pugh and Tony Arcangelini on Bringing Podcasting to Jetpack](https://wptavern.com/podcast/235-rob-pugh-and-tony-arcangelini-on-bringing-podcasting-to-jetpack) — WP Tavern Jukebox ep. 235: Nathan Wrigley talks with Rob Pugh (Automattic) and Tony Arcangelini about Jetpack podcasting, where a post in a designated category with audio becomes an episode; vendor-side account. - [[3. Resources/Readwise/Articles/EmDash 1.0 The Stable CMS With a Secure Plugin Registry]] — Cloudflare (a vendor) announces EmDash 1.0, an MIT-licensed Astro CMS with an AT Protocol plugin registry, and contrasts its sandboxed plugins with WordPress plugins running in the application's PHP process. ## Synthesis additions (2026-10-01 — accessibility practice and a user's exit account) - [[3. Resources/Readwise/Articles/Designing Accessibility Into WordPress Products With WP Engine]] — WP Accessibility Day sponsor livestream: Amber Hinds interviews WP Engine's Jonny Waters on building accessibility into its products before the October 7-8, 2026 conference; vendor claims, Whisper transcript. - [[3. Resources/Readwise/Articles/Goodbye WordPress]] — Nolan Lawson moves the blog from WordPress.com to self-hosting, citing recent drama, the editor drifting from Markdown toward Gutenberg, and a $110 annual charge; a personal account, byline inferred from the domain. ## Synthesis additions (2026-09-23 — Lean TDD for plugin test suites) - [[3. Resources/Permanent Notes/A Test Earns Its Place by Blocking a Ship]] — Brian Okken (Overcommitted): a test that fails on a behavior-preserving refactor is waste; write at the highest level that still makes sense so agents can refactor without rewriting the suite. ## Synthesis additions (2026-09-05 — core primitive security design) - [[3. Resources/Permanent Notes/A Signature Must Bind Its Purpose Not Only Its Data]] — wp_hash() reused across two purposes with no context prefix let a Gravity Forms attacker mint a valid upload token from an ordinary form-state hash ## Synthesis additions (2026-09-05 — local dev environment fidelity) - [[3. Resources/Permanent Notes/Environment Fidelity Not Model Quality Bounds What an Embedded Agent Can Repair]] — An agent embedded in a sandbox (WordPress Studio's SQLite) can only repair what that sandbox's data engine can express, regardless of model quality. ## Synthesis additions (2026-09-05 — the directory listing as the only product site a free plugin has) - [[3. Resources/Permanent Notes/For a Free WordPress Plugin the Readme and Demo Are the Product Site]] — For a free wp.org plugin, the readme short description and Playground blueprint are the landing page and the demo — standard product-site doctrine applies directly. ## Synthesis additions (2026-09-05 — icon-font accessibility failure as a general rendering principle) - [[3. Resources/Permanent Notes/A Rendering Technique That Infers Semantics Fails Where One That Declares Them Does Not]] — Dashicons' PUA code points require screen readers to infer meaning that was never declared; SVG with an explicit label declares it once — generalizes past icons to any inferred-vs-declared encoding. ## Synthesis additions (2026-09-05 — design-to-code handoff decomposition) - [[3. Resources/Permanent Notes/Open Design Formats Remove the Format Handoff Not the Judgment Handoff]] — Penpot's open-format claim only removes the format-translation handoff; the judgment handoff (behavior, state, a11y, component boundaries) survives -- directly testable against WordPress's own theme.json. ## Synthesis additions (2026-09-05 — tool selection serving the wrong party) - [[3. Resources/Permanent Notes/A Tool Chosen for the Builders Convenience Is Justified by the Wrong Partys Needs]] — An Elementor agency owner moved 1,000+ clients off the builder after concluding it optimized for the agency's setup convenience, not client use — the fix was a narrower editor, not a simpler CMS. ## Synthesis additions (2026-09-05 — compatibility and protocol tolerance) - [[3. Resources/Permanent Notes/The Two Halves of Postels Law Have Opposite Track Records]] — the general principle behind WordPress's own compatibility-first entrenchment risk, sourced from the Postel's-law literature ## Synthesis additions (2026-09-04 — what a clean scan does not license) - [[3. Resources/Permanent Notes/Detecting a Property Is Not Evaluating Whether It Serves Anyone]] — six accessibility failures that pass ARC Toolkit and WAVE (focus indicator, meaningless link text, DOM-vs-visual order, unassociated error, untrapped dialog, silent status message); the open platform question is which of them the block and theme layer could close by construction. ## Core Question **How does WordPress expose capability, and what does that choice cost the people building on it?** Not governance (that's [[Open Source Governance MOC]]) and not security posture (that's [[WordPress Hosting Security Stack MOC]]) — this is the architecture layer: which interface a caller should reach for, how a capability gets declared, how the platform evolves without stranding its ecosystem, and who absorbs the cost when it does. The cluster formed on its own across 2026 as the Abilities API, `theme.json`, block themes, and agent-readable surfaces all converged on the same underlying question. ## Choosing the layer - [[3. Resources/Permanent Notes/Caller Distance Determines the Right WordPress Interface]] — the decision rule: how far the caller sits from the code decides whether it's WP-CLI, REST, or an ability. - [[3. Resources/Permanent Notes/An Ability Is the Plugin's Core, Every Surface Is a Thin Wrapper]] — build the capability once and wrap it per surface, rather than reimplementing it per interface. - [[3. Resources/Permanent Notes/Core Abilities Must Be Consumer-Neutral Primitives Not One Interface's Mirror]] — an ability shaped around one consumer is a REST endpoint wearing a costume. - [[3. Resources/Permanent Notes/Agent-First Tooling Exposes Capability Through a CLI Not a New Plugin]] — contrasts on where new capability should surface when the caller is an agent. ## How capability gets declared - [[3. Resources/Permanent Notes/Declarative Configuration Lets a Platform Absorb Its Ecosystem's Migration Cost]] — because Woo extensions declare settings rather than render them, the platform can swap renderers and thousands of authors migrate by doing nothing. - [[3. Resources/Permanent Notes/File-Based Configuration Lets Governance Policy Travel With the Codebase]] — the same declarative property carrying policy rather than UI. - [[3. Resources/Permanent Notes/Canonical Sources Reduce Interface Drift]] — why a single declaration point is what makes a swap safe. - [[3. Resources/Permanent Notes/Agent-Readable Data Is Becoming the Default Plugin Integration Surface]] — the direction the declaration layer is moving as agents become primary consumers. ## Evolution and its costs - [[3. Resources/Permanent Notes/API-Layer Delivery Precedes Interface Delivery in Layered Systems]] — the `theme.json`-first cadence, and the two-tier experience it hands to non-developers. - [[3. Resources/Permanent Notes/Interface Surface Area Costs Selection Accuracy Not Just Tokens]] — the scaling limit a growing ability registry runs into. - [[3. Resources/Permanent Notes/Removing the Opt-Out Converts a Deprecation Into a Deadline]] — what changes for the ecosystem when an escape hatch closes. - [[3. Resources/Permanent Notes/Semantic Identities Outlast Structural Selectors]] — why identity-addressed things survive refactors that position-addressed things don't. - [[3. Resources/Permanent Notes/Prefer Core Integration Over Custom Systems for Maintainability]] — the maintenance argument for building on core primitives rather than beside them. - [[3. Resources/Permanent Notes/A Shared Core Primitive Prevents Per-Plugin Storage Fragmentation]] — what core absorbing a primitive saves the ecosystem. - [[3. Resources/Permanent Notes/A Feature Plugin Can Carry Migration Risk a Core Release Cannot]] — plugin space as the proving ground for migrations that cannot fit a core release window — risk relocated onto opt-in installs rather than removed. - [[3. Resources/Permanent Notes/Docs Co-Located With Source Outlast a Separate Handbook Page]] — the shared commit is the sync mechanism; proximity alone gives no guarantee. - [[3. Resources/Permanent Notes/Project Release-Lead Status Is Not a Proxy for Corporate Standing]] — project governance and corporate standing are separate tracks; reading one off the other needs the source to say so. ## Adoption reality - [[3. Resources/Permanent Notes/Block Theme Development Has Outpaced Block Theme Adoption]] — the gap between what the platform supports and what people actually run. - [[3. Resources/Permanent Notes/The CMS Decision Turns on How a Site Is Edited Not What It Contains]] — the selection criterion that actually drives platform choice. - [[3. Resources/Permanent Notes/Adoption Gaps in Standards Are Usually Documentation Gaps]] — the most common reason a well-designed surface goes unused. ## Related MOCs - [[Open Source Governance MOC]] — who decides what ships, and the WordPress saga as live case study - [[WordPress Hosting Security Stack MOC]] — the security consequences of these extensibility choices - [[AI Agent Safety MOC]] — what changes when the caller reaching these interfaces is an agent - [[Personal Knowledge Management MOC]] — adjacent on declarative, file-based, portable design ## Open questions - Does the `theme.json`-first cadence have a stated UI-follow-up expectation, or is the lag open-ended? - At what registry size does ability discovery need filtering rather than enumeration? - Which core surfaces carry implicit compatibility contracts that were never written down? (Trac #65919 — hook callback IDs changing from strings to integers — is the current worked example.) ## Synthesis additions (2026-08-28 — retirement and restraint) - [[3. Resources/Permanent Notes/A Legacy Feature Should Become Obsolete by Choice Not by Force]] — the retirement half of platform evolution. Closing the old path moves users off a feature without moving them onto anything, so the population that stays is exactly the one the replacement does not yet serve. Reverses the plan recorded in [[3. Resources/Permanent Notes/Hiding Not Removing Deprecates a Legacy Feature Safely]]. - [[3. Resources/Permanent Notes/A Release Lead's Output Is Mostly Subtraction]] — the mechanism that keeps a platform's surface area from growing every cycle, and the reason that work is invisible in the release notes. - [[3. Resources/Literature Notes/WordPress 7.1 Mary Lou (official release announcement)]] — the primary release announcement, registered this run as the anchor the cycle's 33 other 7.1 notes cite. Three structural changes (Abilities API lifecycle, browser-side media processing, full editor iframing), each framed as removing a constraint. No Permanents created from it — the claims are already held in more analytical depth elsewhere. ## Synthesis additions (2026-09-01 — federation documentation) - [[3. Resources/Readwise/Articles/Book Review ActivityPub by Evan Prodromou]] — Terence Eden's review of the O'Reilly ActivityPub book; light-touch deep-read. The one finding that matters for Post Kinds / IndieWeb federation work: the book omits RFC 9421 HTTP Message Signature verification, which is what deployed Fediverse servers now send. Documentation of a live standard goes stale newest-part-first; the claim is held on [[3. Resources/Permanent Notes/Adoption Gaps in Standards Are Usually Documentation Gaps]] rather than as its own Permanent. ## Synthesis additions (2026-10-05 — CMS design and AI site builds) - [[3. Resources/Readwise/Articles/Your Website Needs a Brain]] — Jono Alderson argues that replacing a CMS with page-by-page AI generation reproduces what pages show but loses the shared records and dependencies behind sitemaps, canonicals, hreflang and redirects, and proposes tracing ordinary edits through the current site first. - [[3. Resources/Readwise/Articles/New HTML and CSS Features You Should Be Using in Your Design System]] — Declan Chidlow on zeroheight's blog (vendor content) lists seven native features, including :has, popover, @scope and sibling-index(), that can replace script and preprocessor code in a design system; browser-support claims are the author's and unverified. - [[3. Resources/Permanent Notes/Page-by-Page AI Site Builds Copy What Pages Show but Not What Connects Them]] — Rebuilding a site by prompting an AI page by page reproduces what visitors see but loses the shared records that decide which sitemaps, canonicals, redirects and feeds change when one fact changes. ## Synthesis additions (2026-10-07 — agent access to WordPress) - [[3. Resources/Readwise/Articles/WordPress MCP]] — Chris Coyier describes enabling an MCP one-click setting on his Pressable-hosted WordPress sites so an AI coding agent can draft posts (his own experience as a customer; the post is a personal account, not a technical verification of the setting) ## Synthesis additions (2026-10-07 — registration API design) - [[3. Resources/Literature Notes/Hands-on With the WordPress 7.1 Icon Registration API]] — the WordPress.org Developer Blog's hands-on tutorial for the 7.1 icon registration API, whose notes cover the choice of backed enums over arrays and the SVG sanitization limits. - [[3. Resources/Permanent Notes/A Backed Enum Makes a Closed Registry Statically Checkable Where an Array Cannot]] — a closed set of registry types is checked by the language when it is an enum and left unchecked when it is an array. ## Synthesis additions (2026-10-14 — a personal knowledge base on WordPress) - [[3. Resources/Readwise/Articles/WordPress as Your Personal Knowledge Base]] — a first-person advocacy post for the author's own WP Apps and two plugins; the OAuth gap in the MCP adapter is the author's claim and unreviewed here. - [[3. Resources/Permanent Notes/Callee Interfaces Outlast Caller Integrations Under Provider Churn]] — already holds the post's claim that exposing data through a standard abilities layer lets the AI provider change. - [[3. Resources/Permanent Notes/Consent Is a Gate Not a Notice]] — the authorization point for a client that can read and write a personal site. ## Synthesis additions (2026-10-18 — registering previously unlisted notes) ### Permanent Notes - [[3. Resources/Permanent Notes/A Rehydrator Swaps Content Into an In-Memory Pattern Copy]] — To generate valid block markup from data, read the existing validated pattern into memory unmodified and substitute new data into only the variable slots, per Human Made's rehydrator. - [[3. Resources/Permanent Notes/Build-Time Network Calls Need Explicit Timeouts]] — Any network request made during a build needs an explicit timeout, so a dead endpoint costs seconds of build time, not minutes. Closest-fit placement. - [[3. Resources/Permanent Notes/Bulk Content Automation Needs Dry-Run Scope and Resumable Batching as Defaults]] — Safe bulk WordPress automation needs dry-run preview, explicit scope, and resumable batching as defaults on every command, not flags added after a failure. - [[3. Resources/Permanent Notes/Bulk-Propagation Editing Removes the Tedium Tax on Repetitive Content]] — An interface that propagates one style or content edit across every repeated instance removes a tedium tax, provided it keeps an exception path for instances that should diverge. Closest-fit placement. - [[3. Resources/Permanent Notes/Custom WP-CLI Commands Earn Promotion Once They're Run More Than Once]] — A one-off content-fix script earns promotion to a named, dry-run, batched WP-CLI command because active content sites keep producing the same class of error. Closest-fit placement. - [[3. Resources/Permanent Notes/Filesystem Checks Beat Declared Flags for Classification Stability]] — WordPress classifies a block theme by checking for templates/index.html, a true prerequisite, which holds up better than trusting a declared flag. - [[3. Resources/Permanent Notes/Mainstream Reviews Blur WordPress.com and Open-Source WordPress]] — High-traffic reviews often blur hosted WordPress.com with the open-source WordPress CMS, leaving buyers to sort out the difference themselves. Closest-fit placement. - [[3. Resources/Permanent Notes/Migration Order Should Sequence Low-Volume High-Complexity Content First]] — When planning a content migration, schedule low-volume, high-complexity content early, since it surfaces blocking edge cases and custom-tooling needs before the timeline runs out. Closest-fit placement. - [[3. Resources/Permanent Notes/Pair an Old Filter With a New API to Extend WordPress Without Core Changes]] — Pairing a long-standing WordPress filter with a newer registration API adds capabilities core never shipped a UI for, without patching core or building a settings screen. - [[3. Resources/Permanent Notes/Partial Function Application Removes the Wrapper-Closure Tax on Pipe-Style PHP]] — PHP 8.6 partial function application lets pipe-style call chains work without single-purpose wrapper closures, except when the open parameter is in the wrong place. Closest-fit placement. - [[3. Resources/Permanent Notes/Pick a Local WordPress Environment by Use Case Not Vendor Label]] — Pick a local WordPress dev tool by the work it must do: Playground-based tools suit fast experiments, while production parity and client work need a real pull-live-site workflow. - [[3. Resources/Permanent Notes/Registration Success Does Not Guarantee Render Success Under Lazy Loading]] — When a resource's location resolves lazily at render time, a broken reference can pass registration silently, so registration-time tests alone aren't enough. - [[3. Resources/Permanent Notes/Release Notes Define Scope Not Runtime Compatibility]] — A release guide states intended changes; only an executed test on a pinned build shows what changed for your code, as with the WordPress 7.1 Field Guide. - [[3. Resources/Permanent Notes/Rendering Pattern Choice Is an SEO Decision Not Just a DX One]] — Choosing a hydration approach that ships less JavaScript shrinks the room for server-browser HTML mismatches, so rendering pattern belongs in SEO review too. Closest-fit placement. - [[3. Resources/Permanent Notes/Ship Primitives Not Defaults for High-Legal-Risk Features]] — When a feature carries irreversible legal or trust risk, WordPress should ship primitives and let hosts and plugins own the default, as with collaborative editing. - [[3. Resources/Permanent Notes/Ship a Mechanism Once and Hand the Surface to Content Owners]] — When a feature splits into a one-time developer mechanism and content-owner control through an existing editor surface, that split is usually the right default for Site Editor work. - [[3. Resources/Permanent Notes/WordPress Workflow Defaults]] — Lists the default order of tools on WordPress sites, with wp-cli first for config, plugins, options, search-replace, and cache flushes, then other tools. - [[3. Resources/Permanent Notes/Zet · Align with Core design tokens]] — A short pointer to align WordPress products with Core design tokens, sourced from Matt Cromwell's talk on preparing products for a changing market and AI. - [[3. Resources/Permanent Notes/Zet · Progressive disclosure reduces interface complexity for]] — Progressive disclosure reduces interface complexity; the note is a stub tied to the pattern editing and content-only interactivity call for testing in WordPress 7.0. Closest-fit placement. - [[3. Resources/Permanent Notes/Zet · Technical constraints shape feature implementation paths]] — Notes that technical constraints shape which implementation path a feature takes, pointing to a discussion of sidebar resizing limits in WordPress notes. Closest-fit placement. ### Literature Notes - [[3. Resources/Literature Notes/Agents, Agents Everywhere - Designing for AI Buyers vs AI Coworkers]] — Automattic Design argues AI buyers need machine-readable trust infrastructure while AI coworkers need a reviewable, reversible command center, so the two agent cases need opposite design postures. - [[3. Resources/Literature Notes/Behind the scenes of a punted feature of 7.1]] — A WordPress core contributor explains why a Site Editor style-hierarchy feature was punted from 7.1: no solid design approach, too little user exposure, and no team agreement. - [[3. Resources/Literature Notes/Building WP-CLI Automation for Large WordPress Content Sites Lukasz Wilczak]] — Lukasz Wilczak's talk covers WP-CLI automation for large content sites, including a discover, prototype, promote, schedule path and a post_status inherit bug. - [[3. Resources/Literature Notes/Carousel Designer - Create Beautiful Carousels Faster in WordPress]] — A vendor demo of Carousel Designer, a block-editor carousel where each slide accepts any block, with Smart Sync as the one demonstrated mechanism; performance claims are unverified. - [[3. Resources/Literature Notes/Custom Domains and HTTPS Support in WordPress Studio]] — WordPress Studio can assign a custom .local domain and HTTPS to a local site, so local work catches secure-cookie and mixed-content issues before deploy. Closest-fit placement. - [[3. Resources/Literature Notes/Custom product templates for block themes (Brian Coords)]] — Brian Coords shows custom WooCommerce product templates can be built by pairing register_block_template() with the single_template_hierarchy filter. - [[3. Resources/Literature Notes/Editable Blocks Inside the Custom HTML Block]] — WordPress 7.1 lets a Custom HTML block mix static markup with editable but structurally locked inner blocks, creating a middle layer between HTML, patterns, and custom blocks. - [[3. Resources/Literature Notes/Editor Components Updates in WordPress 7.1]] — WordPress 7.1 finishes staged component migrations, making 40px controls unconditional and removing Navigation, while View keeps accepting a css prop it no longer honors. - [[3. Resources/Literature Notes/How Agencies Can Streamline Client Work with WordPress Studio]] — WordPress Studio's Sync and live preview speed agency client work but need a WordPress.com login; custom Blueprints and automatic backups add repeatability and a safety net. Closest-fit placement. - [[3. Resources/Literature Notes/How WordPress decides a theme is a block theme]] — WordPress decides a theme is a block theme only by whether templates/index.html exists up the parent chain, a check WordPress 7.1 may use to gate the editor iframe. - [[3. Resources/Literature Notes/Hydration and SEO How It Works and Why It Matters]] — A Search Engine Land explainer says hydration is usually SEO-neutral and becomes a problem only when server and browser HTML disagree. Closest-fit placement. - [[3. Resources/Literature Notes/Lit · AI tools accelerate WordPress feature development]] — A short note that AI assistance speeds WordPress core feature work when user-experience validation stays in the loop. Closest-fit placement. - [[3. Resources/Literature Notes/Lit · Automating FSE theme boilerplates accelerates delivery]] — A short note used to justify investing in standardized, automated full-site-editing theme boilerplates. - [[3. Resources/Literature Notes/Lit · Beta releases require extensive community testing]] — Community beta testing catches edge cases internal QA misses, which the note calls essential to WordPress's distributed development model. - [[3. Resources/Literature Notes/Meta Just Quietly Undid the Change That Broke Instagram Embeds in WordPress]] — Meta removed the token requirement for Instagram, Facebook, and Threads oEmbed, ending much of the workaround-plugin friction while GDPR concerns about its script remain. - [[3. Resources/Literature Notes/New in the Yoast SEO Bulk Editor]] — Yoast expanded its SEO Bulk Editor with keyphrase visibility, filters, and AI-drafted metadata that site owners approve row by row before saving. Closest-fit placement. - [[3. Resources/Literature Notes/On-brand maintenance mode for WordPress Block Themes]] — Describes a block theme pattern where a template titled Maintenance serves an on-brand maintenance page, with a comment suggesting a filterable template path. - [[3. Resources/Literature Notes/PHP 8.6 First Look - What's Coming and What's Leaving]] — Previews PHP 8.6, including partial function application and secure-by-default session settings like strict mode, HttpOnly, and SameSite=Lax. Closest-fit placement. - [[3. Resources/Literature Notes/Registering and Rendering SVG Icons in WordPress 7.1]] — Explains registering SVG icons in WordPress 7.1, rendering through a wp_kses allowlist, and a lazy-loading gotcha where a registered icon renders empty. - [[3. Resources/Literature Notes/Text Shadow Support in Global Styles]] — WordPress 7.1 adds textShadow to theme.json at global, block, and element levels, shipping the data model first and deferring inspector controls and presets. - [[3. Resources/Literature Notes/Why WordPress 7.1 Will Improve Your Workflow (WP Minute)]] — WordPress 7.1 release lead Ann McCarthy walks through responsive styling, a new media cropper, and Notes, and explains why classic-block removal and real-time collaboration didn't ship. - [[3. Resources/Literature Notes/WordPress + Claude — a new look for cate.blog]] — AI design and coding tools speed up a redesign, but WordPress's database-backed configuration and split CSS ownership absorb most of the gain. - [[3. Resources/Literature Notes/WordPress 7.0.1 Maintenance Release]] — WordPress 7.0.1 is a maintenance release fixing 31 bugs, with a note pointing to ticket-level coverage elsewhere. - [[3. Resources/Literature Notes/WordPress 7.1 Field Guide]] — The WordPress 7.1 Field Guide lists client-side media processing, accessible tooltips, and an expanded Abilities API, and extenders should test against a pinned build. - [[3. Resources/Literature Notes/WordPress 7.1 is coming. Are your custom blocks ready]] — Ryan Welcher says every WordPress 7.1 iframe failure traces to editor JS loading in the admin document while block markup renders in a separate iframe. - [[3. Resources/Literature Notes/WordPress Playground Team Calls for Testers as New Dock-Based UI Aims to Fix Feature Discoverability]] — The WordPress Playground team asks testers to try a new dock-based UI meant to fix feature discoverability. - [[3. Resources/Literature Notes/WordPress Studio Review]] — An independent review of WordPress Studio notes it is built to create fresh sites and push them up, not pull live sites down, with Playground feature gaps. - [[3. Resources/Literature Notes/WordPress Studio_ What Is It, Is It Worth It]] — A reviewer nearly switched from Lando to WordPress Studio but calls its lack of real database access a dealbreaker, since need is unpredictable. - [[3. Resources/Literature Notes/WordPress just released a brand-new Apple TV app with thousands of free videos]] — WordPress shipped a tvOS app that mirrors the WordPress.tv catalog; the note says the coverage rewrites the App Store listing and gives no accessibility detail. Closest-fit placement. ## Synthesis additions (2026-10-19 — WordPress as a choice for agents) - [[3. Resources/Readwise/Articles/This Is Why WordPress Belongs on an AI Agent’s Website Shortlist]] — Argues WordPress's role permissions and its shell and WP-CLI access are central to whether an agent can build and hand off a site. ## Synthesis additions (2026-10-19 — Permanents from the GameDev Day, agent-site and religious-history batch) - [[3. Resources/Permanent Notes/A Role-Limited CMS Account Does Not Limit an Agent That Also Has Shell Access]] — Limiting an agent's CMS role limits what it can do through authenticated API calls. - [[3. Resources/Permanent Notes/An Agent-Built Site Is Done When a Marketing Teammate Publishes With Their Own Account]] — A site an agent builds isn't finished when the homepage looks right.