WordPress Playground: 2025 Year in Review  ## Metadata - Author: [[Adam's Perspective]] - Full Title: WordPress Playground: 2025 Year in Review - Category: #articles - Document Note: ```yaml tags: [WordPress, Playground, Developer-tools] author: [MISSING] source: Adam's Perspective reference: [https://adamadam.blog/2025/12/04/wordpress-playground-2025-year-in-review/] date created: 2025-12-08 10:00 --- # 🏷️ Title: WordPress Playground: 2025 Year in Review ## 🧭 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 Playground gained near-complete plugin compatibility, major performance boosts, richer PHP/MySQL tooling, improved Blueprints, and broader community adoption in 2025. - Why it matters. - Makes WordPress development, testing, and teaching far easier by running realistic WordPress (and broader PHP) stacks entirely in the browser or via CLI. - Key stakeholders. - Plugin/theme developers, educators, contributors, hosts, and tool vendors building on Playground. - Risks and tradeoffs. - Complexity of maintaining MySQL emulation, PHP extensions, and performance optimizations; potential gaps with edge-case plugins and hosts. - Bottom line. - Playground is maturing into a fast, extensible, and widely used browser-based WordPress lab powering education, demos, and automated workflows. ## 📖 Main Content - Explain the core arguments in plain language. - The article argues that 2025 transformed Playground from a neat demo into a serious development and teaching platform. It highlights: - 99% compatibility with the top 1,000 WordPress.org plugins, plus support for broader PHP tools via Composer and PHP extensions. - Large performance gains from OpCache, multi-worker CLI, smarter prefetching, streaming, and better caching. - New PHP extensions (Xdebug, ImageMagick, Intl, etc.), WebP/AVIF, and default networking, making Playground behave more like production hosting. - A state-of-the-art MySQL-on-SQLite driver that now powers PHPMyAdmin/Adminer and passes >99% of core tests and plugins. - Local CLI workflows, Blueprint v2 specs, visual Blueprint browser, Git support, and “Try in Playground” GitHub integrations. - Rapid community adoption in meetups/WordCamps, translations, plugins enabling live previews, and third-party tools like Studio, Telex, and TYPO3 playground. - Add sourced context and define terms. - Blueprints are JSON/PHP configurations that describe starter WordPress environments (plugins, themes, content) that launch instantly in Playground. - The new MySQL driver, built in the `sqlite-database-integration` plugin, parses and translates complex MySQL queries to SQLite while preserving behavior. - Xdebug integration enables step debugging in IDEs, and experiments aim to use it via browser DevTools. - Note uncertainties or contested claims. - “99+% of WordPress plugins” and “most comprehensive” MySQL-on-SQLite driver are strong claims that depend on evolving plugin ecosystems and unlisted test suites. - Binary MySQL protocol support and some Xdebug-in-browser features are still “work in progress,” so timelines and stability remain to be seen. ### 🗒️ Notes - The article is a re-publication of the official “WordPress Playground 2025 Year in Review” from make.wordpress.org. - Playground now supports 99% of the top 1,000 plugins; remaining failures are either broken outside Playground or await platform improvements. ([plugin compatibility section](https://read.readwise.io/read/01kbmqb1xn7eqggg0abjazwkzp?endLexposition=0000C_00002-000F&startLexposition=00004&emphasizeText=99+install+and+activate+successfully)) - Playground can run broader PHP apps via Composer and other tools, not just WordPress. - Performance: - Enabling OpCache alone reduced average response time by 42%, from 185ms to 108ms. ([performance stats](https://read.readwise.io/read/01kbmqb1xn7eqggg0abjazwkzp?endLexposition=0000K_00002-0008&startLexposition=0000E&emphasizeText=from+185ms+down+to+108ms)) - CLI now supports multi-worker concurrency via `--experimental-multi-worker`. - Pre-fetches update checks, streams network responses immediately, lazy-loads parts of the UI, and uses caching more aggressively. - PHP extensions & formats: - Newly supported: Xdebug (with IDE integration), SOAP, OpCache, ImageMagick, GD 2.3.3, Intl, Exif, and WebP/AVIF. - Networking is enabled by default on playground.wordpress.net for outgoing HTTP requests. ([PHP extensions list](https://read.readwise.io/read/01kbmqb1xn7eqggg0abjazwkzp?endLexposition=0000S_00002-003d&startLexposition=0000M&emphasizeText=SOAP%2C+OPCache%2C+ImageMagick%2C+GD+2.3.3%2C+Intl%2C+and+Exif)) - Dynamic extension loading (starting with Xdebug and Intl) will enable toggling extensions to simulate different host environments. - MySQL emulation: - New MySQL-on-SQLite driver is described as state-of-the-art and likely the most comprehensive open source of its kind. - Supports PHPMyAdmin and Adminer directly in Playground and passes >99% of plugin directory tests and WordPress core tests. ([MySQL emulation capabilities](https://read.readwise.io/read/01kbmqb1xn7eqggg0abjazwkzp?endLexposition=0000c_00002-003j&startLexposition=0000U&emphasizeText=It%E2%80%99s+likely+the+most+comprehensive+open-source+library+of+its+kind)) - Future: MySQL binary protocol support to allow mysql CLI, database apps, PDO connections, and MySQL tool ecosystems to work against Playground’s SQLite backend. - Developer tooling: - playground.wordpress.net now includes: - Blueprints editor (create and test Blueprints, bundle media). - Standalone PHP Playground (PHP snippets with/without WordPress). - Gutenberg branch preview via `?gutenberg-branch=branch-name`. ([developer toolbox overview](https://read.readwise.io/read/01kbmqb1xn7eqggg0abjazwkzp?endLexposition=0000k_00002-003I&startLexposition=0000e&emphasizeText=playground.wordpress.net+now+provides+plenty+of+developer+tools)) - “Try in Playground” GitHub Action automatically attaches preview links to PRs, letting reviewers run changes in Playground without local setup. - CLI workflows: - Playground CLI reached stable with: - Auto mode: `npx @wp-playground/cli server --auto-mount` to spin up WordPress with your plugin/theme directory. - Xdebug integration via a simple flag for IDE debugging. - Multi-worker concurrency for parallel PHP/network processing. - `runCLI()` to embed Playground inside Node.js/JS apps for automated testing or desktop apps like Studio. ([CLI features](https://read.readwise.io/read/01kbmqb1xn7eqggg0abjazwkzp?endLexposition=0000q_00007_00005-000N&startLexposition=0000m&emphasizeText=Playground+CLI+hit+a+stable+release)) - Blueprints: - New built-in Blueprints editor on playground.wordpress.net. - Visual Blueprints browser: gallery of ready-made starter sites (blogs, news, organizations) that launch with one click. - `.git` directory support for repositories cloned via Blueprints, enabling normal git workflows. - Blueprints v2 “living specification” is published to standardize content, post types, translations, fonts, and media definitions, with more concise notation. - An all-PHP Blueprints runner is being developed (`php-toolkit`); Playground CLI can use it via `--experimental-blueprints-v2-runner`. ([Blueprints upgrades](https://read.readwise.io/read/01kbmqb1xn7eqggg0abjazwkzp?endLexposition=0000w_00007_00005-000E&startLexposition=0000s&emphasizeText=Blueprints+%28WordPress+starter+configurations%29+received+many+major+upgrades)) - Other improvements: - Error screen redesigned to be larger, clearer, and more informative. - - Summary: Explore the 2025 advancements in WordPress Playground, including plugin compatibility, performance boosts, and new PHP support features. - URL: https://adamadam.blog/2025/12/04/wordpress-playground-2025-year-in-review/ This post is re-published post from <https://make.wordpress.org/playground/2025/12/03/wordpress-playground-2025-year-in-review/> A lot happened for Playground this year! Let’s review what changed and why it matters for your work: ##### **99+% of WordPress Plugins Supported in Playground** Nearly every plugin from the WordPress plugin directory works in Playground. In [testing with the top 1,000 plugins](https://github.com/bgrgicak/playground-tester/blob/d48c1a6f7d53d5e4851646c2151dc4ccf0a3b296/test-comparison.md), 99% install and activate successfully. The handful that don’t work yet either crash even outside of Playground or need a few more Playground platform improvements the team is actively working on. Speaking about compatibility, Playground is now powerful enough to run PHP applications beyond WordPress: * [Composer](https://github.com/WordPress/wordpress-playground/pull/2679) for managing PHP dependencies – available for developers via Blueprints …and a lot more! Try bringing your favorite PHP tools into Playground – they may just work. And please share your experience with others in the comments or at the [#playground](https://wordpress.slack.com/archives/playground) Slack channel! ##### **Playground Got Faster—A Lot Faster** Playground performance got a major boost in 2025. Enabling OpCache alone [cut the average response time by 42%](https://make.wordpress.org/playground/2025/10/23/things-you-might-have-missed-about-the-playground-project-over-the-past-few-months/)—from 185ms down to 108ms. On top of that, the Playground CLI uses multiple workers (with the `--experimental-multi-worker` flag) and processes concurrent requests in parallel instead of making them wait in line. There’s a lot more! Playground now [pre-fetches update checks](https://github.com/WordPress/wordpress-playground/pull/2295) before you even open wp-admin. Network responses [start streaming](https://github.com/WordPress/wordpress-playground/pull/2266) right away instead of waiting for complete downloads. WordPress loads before the optional parts of the Playground app. More Playground assets are cached, and the cache is utilized more. All these improvements compound. Playground feels faster because it *is* faster. ##### **New PHP Extensions Support Modern Development Workflows** In 2024, Playground established a solid foundation with core PHP extensions such as bcmath, xml, curl, and mbstring. In 2025, the support extended to: * [**XDebug**](https://make.wordpress.org/playground/2025/11/24/debugging-with-xdebug-is-now-available-in-wordpress-playground/) – available in CLI with [IDE integration](https://wordpress.github.io/wordpress-playground/developers/xdebug/getting-started/#starting-with-ide-integration). * **SOAP, OPCache, ImageMagick, GD 2.3.3, Intl, and Exif** PHP extensions. * **WebP and AVIF image formats**. * Networking is now enabled by default on playground.wordpress.net, allowing PHP to request any URL. * There’s also an ongoing exploration to [use XDebug through browser devtools and without an IDE](https://wordpress.github.io/wordpress-playground/developers/xdebug/getting-started#early-access-devtools-debugger). In addition, Playground now supports **dynamic extensions** under the hood, with Xdebug and Intl being the first two dynamic extensions. This unlocks a future on/off switch for loading specific extensions so that you can test how your plugin behaves in different hosting environments. ##### **State of the Art MySQL Emulation** In 2025, Playground upgraded its MySQL support with [a brand-new, state of the art MySQL-on-SQLite database driver](https://make.wordpress.org/playground/2025/06/13/introducing-a-new-sqlite-driver-for-wordpress/). It’s likely [the most comprehensive open-source library of its kind in any language](https://github.com/WordPress/sqlite-database-integration/issues/106#issuecomment-2276082489). Developed in the [sqlite-database-integration](https://github.com/wordpress/sqlite-database-integration) plugin, it leverages a custom-made MySQL query parser and translation logic to support even those highly nuanced MySQL queries. In 2025, it became powerful enough to support: * [**PHPMyAdmin and Adminer**](https://make.wordpress.org/playground/2025/12/03/adminer-and-phpmyadmin-in-wordpress-playground/) – available with a click directly on playground.wordpress.net. * 99+% of WordPress directory plugins. * 99+% of WordPress core unit tests. Looking forward, the Playground team is [working on MySQL binary protocol support](https://github.com/WordPress/sqlite-database-integration/pull/272). Once that lands, you’ll be able to use the mysql CLI, connect with database management apps, establish PDO connections, and tap into the full ecosystem of MySQL developer tools—all running against Playground’s CLI SQLite backend. ##### **A Developer Toolbox, One Click Away** [playground.wordpress.net](http://playground.wordpress.net) now provides plenty of developer tools right in your browser: * [New Blueprints editor](https://github.com/WordPress/wordpress-playground/pull/2815) helps you write and test Blueprints, and even bundle additional media files. * [Standalone PHP Playground](https://playground.wordpress.net/php-playground.html) provides a space to test PHP code snippets on the fly, with or without WordPress running. * [Gutenberg branch preview](https://make.wordpress.org/playground/2025/11/26/preview-gutenberg-development-branches-in-your-browser/) – Use the [?gutenberg-branch=add/new-feature](https://playground.wordpress.net/?gutenberg-branch=add/new-feature) query parameter to load any Gutenberg branch. This feature complements the existing [support for previewing WordPress and Gutenberg PRs](https://wordpress.github.io/wordpress-playground/developers/build-your-first-app/#preview-wordpress-core-and-gutenberg-branches-or-prs). And if you’d like to preview Pull Requests in your project using Playground, see the [“Try in Playground” GitHub action](https://github.com/WordPress/action-wp-playground-pr-preview/). It automatically adds a preview link to every pull request in your repository. Reviewers just click the link and see your changes running in WordPress—no need to pull code or configure anything locally. ##### **Local CLI Workflows** [Playground CLI](https://wordpress.github.io/wordpress-playground/developers/local-development/wp-playground-cli/) hit a stable release with several powerful new features to streamline your development workflow: * **Auto mode to start a local WordPress server with your plugin or theme installed**. Run npx @wp-playground/cli server –auto-mount in your local plugin or theme directory. That’s it! * **Debug with XDebug**. [Add a single CLI flag and immediately connect via VS Code or PhpStorm](https://wordpress.github.io/wordpress-playground/developers/xdebug/getting-started/). Set breakpoints, watch variables change as code executes, and step through your functions line by line. The Playground team is also exploring [connecting XDebug to Chrome DevTools](https://wordpress.github.io/wordpress-playground/developers/xdebug/getting-started#early-access-devtools-debugger) (unreleased, work in progress). * **Multi-worker support:** Use –experimental-multi-worker to enable concurrent operations. While one worker waits for a network response, another processes PHP. No more slowdowns. * **[runCLI()](https://wordpress.github.io/wordpress-playground/developers/local-development/wp-playground-cli/#using-runcli)** lets developers embed WordPress Playground instances directly in JavaScript/Node.js applications. It’s useful for [automated testing](https://make.wordpress.org/playground/2025/10/23/things-you-might-have-missed-about-the-playground-project-over-the-past-few-months/) workflows and building desktop apps, such as [Studio](https://developer.wordpress.com/studio/), on top of Playground. ##### **Blueprints** [Blueprints](https://wordpress.github.io/wordpress-playground/blueprints/) (WordPress starter configurations) received many major upgrades this year: * [Blueprints editor](https://github.com/WordPress/wordpress-playground/pull/2815) – Create your Blueprints directly on playground.wordpress.net with the new, built-in editor. * [Visual Blueprints browser](https://wordpress.github.io/blueprints/) – Explore ready-made starter sites for blogs, news sites, and organizations from the [Blueprints gallery](https://github.com/WordPress/blueprints/). Launch them in Playground with a click. * [.git directory support](https://github.com/WordPress/wordpress-playground/pull/2787) – Create a `.git` directory for any repositories cloned via Blueprints to use with your everyday git tools. * [Blueprints v2 living specification](https://github.com/Automattic/WordPress-extension-proposals/blob/trunk/wep-1-blueprint-v2-schema/proposal.md) was published to make Blueprints more accessible to humans and AI tools. The new format standardizes how post types, content, translations, fonts, and media files are defined, while making the notation more succinct. An all-PHP Blueprints runner is being developed in the [php-toolkit repository](https://github.com/WordPress/php-toolkit/), and Playground CLI runs it when the `--experimental-blueprints-v2-runner` flag is used. ##### **Other highlights** * [The error screen](https://github.com/WordPress/wordpress-playground/pull/2874) is larger, clearer, and gives you *a lot* more useful information. * [WordPress Importer URL migration](https://make.wordpress.org/core/2025/11/27/wordpress-importer-can-now-migrate-urls-in-your-content/). Playground’s need for reliable site imports drove support for [intelligent URL rewriting](https://make.wordpress.org/core/2025/11/27/wordpress-importer-can-now-migrate-urls-in-your-content/) in the WordPress Importer plugin. Content URLs now get accurately rewritten during import using dedicated parsers, such as [CSSURLProcessor](https://github.com/WordPress/php-toolkit/blob/5303dfbb02d5e347fd03fa8ea207b653f18dbdbf/components/DataLiberation/URL/class-cssurlprocessor.php) or [URLInTextProcessor](https://github.com/WordPress/php-toolkit/blob/5303dfbb02d5e347fd03fa8ea207b653f18dbdbf/components/DataLiberation/URL/class-urlintextprocessor.php), eliminating broken images and post-processing queries for every WordPress user. * There’s a new [Ask AI button in the documentation](https://wordpress.github.io/wordpress-playground/). It’s useful for all sorts of simple and complex Playground-related questions, but it particularly shines for creating and debugging Blueprints. ##### **Community Impact** Playground was used 1.4 million times in 227 countries this year to showcase plugins, test code changes, and teach others. The community stepped up in ways that went far beyond code. Community contributors translated the documentation into French, Spanish, Portuguese, Japanese, Gujarati, and Tagalog, with Bengali translations now underway. Over 1,000 plugins from the directory enabled the Playground-powered “Preview” button. 48 developers earned [the Playground contribution badge](https://profiles.wordpress.org/associations/playground-contributor/members/) for their work on code, documentation, and community support. From the flagship events down, Playground was everywhere: at WordCamp Europe 2025 @berislavgrgicak showed [how to build automated tests with Playground](https://europe.wordcamp.org/2025/session/building-automated-tests-with-wordpress-playground/?utm_source=chatgpt.com), and @bph walked through [creating one-click demos](https://asia.wordcamp.org/2025/session/create-a-demo-with-playground/?utm_source=chatgpt.com) at WordCamp Asia 2025. @danieldudzic demoed [testing WooCommerce faster than a Formula 1 pit stop](https://wordpress.tv/2024/09/30/testing-faster-than-a-red-bull-pit-stop-wordpress-playground-and-woocommerce-blueprints/) at WordCamp Gdynia. @nilovelez called Playground [“the best tool ever invented for teaching WordPress”](https://wordpress.tv/2025/10/05/playground-la-mejor-herramienta-jamas-inventada-para-ensenar-wordpress/) at WordCamp Galicia. @muryam brought Playground to WordCamp Islamabad, showcasing how to build, test, and explore WordPress. And even beyond that, @mrfoxtalbot, @wpaurorautasic, @fellyph, @sakaruk, and @magdalenapaciorek took Playground to Madrid, Lisboa, Wrocław, Nepal, and Rio de Janeiro, turning Playground into a recurring theme in talks on testing, education, and release workflows. Playground also enabled the community to build great tools and workflows. @smrubenstein [integrated Playground CLI with GitHub Copilot](https://sethrubenstein.info/2025/09/12/boosting-wordpress-development-with-github-copilot/) and shipped four features in one week—work that would otherwise take months. @bacoords built [dynamic Blueprints running on Cloudflare Workers](https://github.com/WordPress/wordpress-playground/pull/2679) for runtime-configurable WooCommerce demos. [Studio](https://developer.wordpress.com/studio/), a local development environment, added support for Blueprints. [Telex](https://telex.automattic.ai/) lets you generate Gutenberg blocks from text prompts and instantly test them in Playground. There’s more! @akirk added many new steps to his Blueprint development tool [Playground Step Library](https://akirk.github.io/playground-step-library/), a versatile paste handler for Markdown, HTML, JSON, and more. @jamesmarsland launched [PootlePlayground.com](http://PootlePlayground.com), an AI-aided Blueprint generator. And TYPO3—a different CMS—[built a TYPO3 playground](https://typo3.org/article/budget-idea-report-one-click-typo3-playground) with WordPress Playground as a foundation, proving the impact reaches beyond the WordPress ecosystem. Kudos to all contributors: @ajitbohra, @akirk, @aksyonov, @andraganescu, @amieiro, @ashfame, @aslamdoctor, @bacoords, @berislavgrgicak, @beryldlg, @bph, @brandonpayton, @dd32, @devmuhib, @dhruval04, @dhruvang21, @dilip2615, @fellyph, @getdave, @hmbashar, @huzaifaalmesbah, @ingeniumed, @ivanottinger, @janjakes, @janwoostendorp, @jdahir0789, @jeffpaul, @jhimross, @jonsurrell, @josevarghese, [jswhisperer](https://github.com/jswhisperer), @juanmaguitar, @justinnealey, @karthickmurugan, [lukaszuznanski](https://github.com/lukaszuznanski), [madhavraj2004](https://github.com/madhavraj2004), @marc4, [mbuella](https://github.com/mbuella), @mehrazmorshed, @merkushin, @mosescursor, @mrfoxtalbot, @mujuonly, @mukesh27, @muryam, @n8finch, @ndiego, @nikunj8866, @noruzzaman, [oskardydo](https://github.com/oskardydo?utm_source=chatgpt.com), @passoniate, @praful2111, @psykro, @ravigadhiyawp, @rollybueno, @sakaruk, @sandeepdahiya, @sandipsinh007, @sejas, @shailu25, @shimotomoki, @shiponkarmakar, @sirlouen, @tomayac, @vipulgupta003, @wojtekn, @wpaurorautasic, @yannickdecat, @zaerl, @zieladam. Thank you all for being part of this journey! Here’s to making WordPress easier and more accessible for everyone. *Props to @akirk, @berislavgrgicak, @janjakes, @bpayton, @yannickdecat for their help with writing and reviewing this post. Also, props to all of you who helped get Playground where it is today!*, WordPress Playground: 2025 Year in Review, Adam's Perspective, 01kbmqb1xn7eqggg0abjazwkzp.