Content changes shape at five boundaries between save and render, and four of them report nothing. A map of what each one removes, plus a four-command diff harness that identifies the responsible boundary in a minute.
Core annotates the hook registry's keys as strings and PHP hands you integers. Reproduce it in thirty seconds, then the four-question test for telling a contract from an internal.
WordPress suppresses activation hooks on every update, deliberately. The class of plugin bug that produces, why every test environment hides it, and where to put the work instead.
Edge is moving to Manifest V3 and Firefox is the only major browser left supporting uBlock Origin. The technical change, the strongest case for it, the case against, and the adjacency with Chrome's agent APIs.
Chrome opened a WebMCP origin trial and shipped Lighthouse agentic audits. Safari shipped an MCP server. The line buried in Chrome's docs that matters most: agents use the accessibility tree as their primary data model.
WordPress 7.1 adds a unified public exposure flag and a shared filtering pipeline to wp_get_abilities(). The resolution order, the two callbacks, the two global filters, the REST metadata trap, and why filtering is discovery and not authorisation.
Pro copies a Free class, forks a query, adds a near-duplicate table, and the next update breaks it. The three seams that avoid all of that: container rebind, inheritance, filters. Plus the boot order, the rebind risk, and the test that stops your architecture doc becoming fiction.
WordPress 7.1 adds wp_prepare_json_schema_for_client(), turning internal schemas into portable draft-04 output. What it strips, the two profiles, and the Abilities API changes that ship alongside it.
WordPress 7.1 adds four filters around the Abilities API execution pipeline, so you can short-circuit a call, enrich its input, override the permission result, or transform what comes back. What each one is, where it fires, and the patterns that matter once an AI agent is the caller.
WordPress 7.0 'Armstrong' shipped the client-side Abilities API. Here is what @wordpress/abilities and @wordpress/core-abilities let you build - registering, executing, and querying AI-ready abilities in JavaScript, with real code.
webMCP proposes turning websites into structured tool surfaces for AI agents instead of DOM-scraping targets. Here is what it means for WordPress: the opportunity, the attack surface, and a practical readiness checklist for developers.
Choosing between Contentful and WordPress in 2026 depends on your architecture needs, team size, and budget. This comparison covers API-first vs monolithic CMS design, content modeling, editor UX, real pricing, multi-channel delivery, and a clear breakdown of when each platform wins for enterprise content teams.
Complete comparison of WordPress REST API authentication methods in 2026: Cookie and nonce, Application Passwords, JWT, OAuth 1.0a, and OAuth 2.0. Includes a decision matrix, PHP and cURL examples, and guidance on media upload authentication.
Guide to wordpress application passwords for REST API authentication without exposing your main password. Covers wp_is_application_passwords_available, the edit_posts capability gate, cURL, JS Fetch, PHP examples, revocation, and security best practices for 2026.
<p>The WordPress stories that mattered in March 2026, AI agents writing posts on WordPress.com, WP 7.0 Connectors API and Pattern Overrides, WordCamp Asia fallout, and the plugin ecosystem shifts nobody is talking about.</p>
<p>How React actually works inside WordPress, building Gutenberg blocks with @wordpress/scripts, creating admin screens with @wordpress/components, state management with data stores, and when to reach for the Interactivity API instead.</p>
A practical CI/CD pipeline for WordPress with GitHub Actions, covering PHPCS linting, PHPUnit tests, SSH-based deployment, WP-CLI remote commands, staging to production promotion, and secrets management.
A deep dive into the WordPress 7.0 Connectors API — what it is, how to register connectors, permission design, schema best practices, and a concrete checklist to get your plugin ready before 7.0 ships.
A complete comparison of headless CMS vs WordPress in 2026 - covering performance, SEO, developer experience, cost, and when to use each approach.
WordPress vs Payload CMS compared side by side. Architecture, performance benchmarks, content modeling, developer experience, plugin ecosystem, hosting costs, and use cases to help you pick the right CMS in 2026.