The Irony Nobody Discusses
WordPress 7.0 'Armstrong' shipped on May 20, 2026, with Gutenberg 23.3 and a suite of editor improvements. Within weeks, the WordPress Core team confirmed plans to migrate the admin interface to React 19 for version 7.1. The CMS that renders 43% of detected websites using PHP and server-side templates has decided its own administrative interface should be built with a modern JavaScript framework.
This is not new. WordPress's block editor (Gutenberg) has been built on React since 2018. But the 7.1 roadmap extends React further into the admin — dashboard widgets, site health panels, settings interfaces. WordPress is systematically replacing its own PHP-rendered admin with React components. The implication is clear: WordPress's own development team does not consider WordPress's rendering model sufficient for interactive applications.
What React 19 Brings That PHP Cannot
React 19 introduces server components, concurrent rendering, and automatic batching — features designed for interactive, real-time user interfaces. These are capabilities that PHP's request-response model fundamentally cannot provide. Every admin page reload in WordPress requires a full server round-trip. React components update in place, reducing perceived latency from seconds to milliseconds.
The WordPress team is making the same architectural decision that enterprises face with their own web properties: PHP server-side rendering works for content display, but interactive experiences require a modern JavaScript framework. The difference is that WordPress is making this decision for its internal tools while continuing to sell PHP rendering to its users.
PHP.wasm: The Experimental Bridge
WordPress Playground — the browser-based WordPress testing environment — is exploring PHP.wasm, running PHP directly in the browser via WebAssembly. A new guide shows how to run PHP frameworks entirely in the browser. This is technically impressive but architecturally backwards: instead of using JavaScript for interactive interfaces (as React does natively), it compiles PHP to run in a JavaScript runtime. The overhead is substantial and the developer experience is experimental.
The Signal for Organizations
When a framework's own development team migrates away from its rendering model, that is a leading indicator. WordPress is not abandoning PHP for content delivery — WordPress sites will continue to render HTML via PHP for the foreseeable future. But the team is acknowledging that PHP is insufficient for the interactive, real-time experiences that modern users expect. Organizations evaluating long-term framework commitments should note that WordPress's own roadmap is a migration story.
