## Summary Adam Zieliński, creator of WordPress Playground, explains how WordPress runs directly in the browser via WebAssembly, with no Apache, MySQL, or server needed. He built the first MVP in a week to escape the burden of lengthy setup instructions while writing tutorials. Playground has grown into a platform for interactive demos, plugin and theme previews, offline-first editing, and persistent sites, and he frames it as a foundational layer that removes setup friction for anyone learning, teaching, or building with WordPress. ## Key Points - Playground compiles PHP to WebAssembly so WordPress runs in a browser tab, and also in Node.js or natively in mobile apps. - The motivation was practical: setting up Node.js, Git, npm, and WP installs made tutorials painful, so Zieliński prototyped a zero-setup environment. - Early Playground was stateless and lost edits on refresh; persistent sites and local file system syncing now solve that. - The Playground plugin is approved in the WordPress.org directory, enabling interactive demos in docs, training, and translations. - It makes realistic theme previews easy with dummy data, fixing a long-standing problem with unrealistic WP theme previews. - Automattic prototyped a mobile app running WordPress natively through Playground, saving notes as HTML synced via iCloud. - Dream features include real-time collaboration in Gutenberg at the browser layer, offline-first editing, and edge or blockchain hosting experiments. ## Claim Atoms - **PHP compiled to WebAssembly runs WordPress in-browser** — no server, database, or local stack required; works in browsers, Node.js, and mobile. - **Playground is "a platform for building platforms"** — Zieliński's framing: remove all friction so anyone can learn, teach, build, or test instantly. ## Links - [[3. Resources/Permanent Notes/Emulated Local Dev Trades Production Fidelity for Zero-Setup Speed]] — grounds — Playground's WebAssembly runtime supplies the zero-setup side of the speed-versus-fidelity trade - [[3. Resources/Permanent Notes/Time-to-Hello-World Is the Critical Developer Experience Metric]] — applies-in — removing the server, database, and toolchain setup compresses the path from opening a tutorial to running WordPress - [[3. Resources/Permanent Notes/Zet · Playground demos improve client feedback on themes]] — grounds — Zieliński identifies realistic browser previews with seeded content as a primary Playground use case - [[3. Resources/MOCs/DevRel MOC]] — connects Playground's zero-setup runtime to documentation, training, demos, and a shorter developer on-ramp.