# A GitHub-Linked Blueprint Recouples Block Themes With Version Control ## Claim A browser-based WordPress sandbox that reloads its linked theme or plugin straight from GitHub on every session turns "try it in Playground" into an actual step in a version-controlled dev loop, not just a demo. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds when the blueprint points at a real, actively-maintained GitHub repo for the theme or plugin under test. - Breaks down if the blueprint caches the GitHub source instead of fetching latest, or if the linked repo isn't the actual deploy target (staging drift between the repo and the live site). - Does not establish that this replaces a full local dev environment — only that it restores a version-control checkpoint the site editor's file-decoupling had removed. ## Evidence Elliot Richmond describes WordPress Playground's blueprint layer as a JSON config that assembles theme, content, and plugins for a client-side, WebAssembly-run WordPress instance. When a blueprint links to a GitHub repository, Playground reloads the latest version of that repo's contents on every load — recoupling block theme development with version control after the block/site editor decoupled themes from files. > "Every time that blueprint is loaded, it loads the latest version of that plugin." ## Links - [[Zet · Playground demos improve client feedback on themes]] — because contrasts on purpose; same mechanism (disposable browser sandbox) applied to client-facing feedback rather than developer version control - [[Reproducible Environments Encode Repeated Setup as Config]] — because evidence-for; the blueprint is a specific instance of setup-as-config making an environment reproducible - [[3. Resources/MOCs/Events/WordCamp Europe 2026 MOC]] — because applies-in; a concrete dev-workflow pattern worth demoing at a community event ## Tests / falsifiers - Confirm directly whether a blueprint URL caches its GitHub source or fetches the true latest commit on every load — if it caches, the "always latest" claim needs a TTL caveat. - Test with a repo under active CI (frequent commits) vs. a rarely-updated repo to see whether the recoupling behavior holds under load/rate-limiting. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/The Power of WordPress Playground]] — Elliot Richmond on Playground blueprints for client training and version-controlled block theme development.