Preview Gutenberg Development Branches in Your Browser ![rw-book-cover](https://s.w.org/images/home/wordpress-default-ogimage.png) ## Metadata - Author: [[WordPress Playground]] - Full Title: Preview Gutenberg Development Branches in Your Browser - Category: #articles - Document Note: --- tags: [WordPress, Gutenberg, Playground] author: WordPress Playground source: Make WordPress reference: [https://make.wordpress.org/playground/2025/11/26/preview-gutenberg-development-branches-in-your-browser/] date created: 2025-12-01 12:00 --- # 🏷️ Title: Preview Gutenberg Development Branches in Your Browser ## 🧭 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 can now load Gutenberg development branches directly in the browser using a query parameter, letting you test trunk and any feature branch without local setup ([intro explanation](https://read.readwise.io/read/01kb8cjpc9414qqn0s7vtfsbn9?endLexposition=00002_00000-003E&startLexposition=00000&emphasizeText=WordPress+Playground+now+loads+Gutenberg+development+branches+directly+in+your+browser)). - Why it matters. - Lowers friction to test bleeding‑edge Gutenberg, improving feedback loops and making contribution and QA more accessible ([why this matters](https://read.readwise.io/read/01kb8cjpc9414qqn0s7vtfsbn9?endLexposition=0000A_00003_00000-001A&startLexposition=00004&emphasizeText=Previously%2C+you+could+only+preview+specific+PRs+in+Playground%2C+and+now+you+can+preview+any+branch)). - Key stakeholders. - Gutenberg and Core contributors, theme/plugin developers, educators, documentation writers, QA and testing teams. - Risks and tradeoffs. - Uses latest successful GitHub Actions artifact, so previews may lag a few commits behind to favor reliability over absolute freshness ([artifact note](https://read.readwise.io/read/01kb8cjpc9414qqn0s7vtfsbn9?endLexposition=0000Y_00002-0010&startLexposition=0000U&emphasizeText=Playground+loads+the+latest+available+build+artifact+from+GitHub+Actions)). - Bottom line. - A simple URL parameter now turns Playground into a fast, shareable lab for any Gutenberg development branch or PR, directly in the browser. --- ## 📖 Main Content - The article introduces a new capability in WordPress Playground: loading Gutenberg development branches via URL parameters so you can test them in-browser instead of cloning repos, running builds, and managing local installs ([problem it solves](https://read.readwise.io/read/01kb8cjpc9414qqn0s7vtfsbn9?endLexposition=00002_00000-003E&startLexposition=00000&emphasizeText=This+solves+a+common+challenge%3A+testing+bleeding-edge+Gutenberg+development+typically+requires+cloning+repositories)). - Motivation: Gutenberg’s trunk changes daily, and experimental work happens in feature branches. Previously, Playground only previewed specific pull requests; now it can preview any branch, including trunk and experimental branches ([new possibilities](https://read.readwise.io/read/01kb8cjpc9414qqn0s7vtfsbn9?endLexposition=0000A_00003_00000-001A&startLexposition=00004&emphasizeText=Previously%2C+you+could+only+preview+specific+PRs+in+Playground%2C+and+now+you+can+preview+any+branch)). - Mechanism: - A new Query API parameter `gutenberg-branch` is added to Playground URLs. - Example for trunk: `https://playground.wordpress.net/?gutenberg-branch=trunk`. - Example for a feature branch: `https://playground.wordpress.net/?gutenberg-branch=add/new-feature` ([usage examples](https://read.readwise.io/read/01kb8cjpc9414qqn0s7vtfsbn9?endLexposition=0000M_00000_00000-0014&startLexposition=0000C&emphasizeText=Playground+introduces+two+new+Query+API+parameters+gutenberg-branch)). - Pull-request previews continue to work unchanged for both Core and Gutenberg, using `core-pr` and `gutenberg-pr` parameters, such as `?core-pr=9500` or `?gutenberg-pr=73010` ([PR section](https://read.readwise.io/read/01kb8cjpc9414qqn0s7vtfsbn9?endLexposition=0000S_00000_00000-001b&startLexposition=0000O&emphasizeText=Pull+request+previewing+still+works+exactly+as+before)). - Implementation detail: when previewing a branch, Playground pulls the latest available build artifact from Gutenberg’s GitHub Actions. If the most recent commit is still building, it falls back to the previous successful artifact, so you might see code that’s a few commits behind but stable ([freshness vs reliability](https://read.readwise.io/read/01kb8cjpc9414qqn0s7vtfsbn9?endLexposition=0000Y_00002-0010&startLexposition=0000U&emphasizeText=This+means+you+might+see+changes+from+a+few+commits+back%2C+not+the+absolute+latest+code)). - Use cases: - Testing and bug reporting against trunk or experimental branches. - Embeddable environments for documentation and education, e.g., linking docs for a trunk-only feature directly to a live Playground instance showing it ([education example](https://read.readwise.io/read/01kb8cjpc9414qqn0s7vtfsbn9?endLexposition=0000Y_00002-0010&startLexposition=0000U&emphasizeText=For+example%2C+if+you%27re+documenting+a+new+Gutenberg+feature+still+in+trunk%2C+link+directly+to+a+Playground+instance+that+demonstrates+it)). - The conclusion encourages developers to start testing immediately, use the Query API broadly, and feed early issues back into WordPress and Gutenberg development ([call to action](https://read.readwise.io/read/01kb8cjpc9414qqn0s7vtfsbn9?endLexposition=0000g_00000_00002_00000-000F&startLexposition=0000a&emphasizeText=With+branch+previewing%2C+you+can+explore+these+changes+the+moment+they+merge)). --- ### 🗒️ Notes - Playground now supports loading Gutenberg’s trunk and any feature branch purely via URL parameters, eliminating local environment setup and build steps. - The feature targets “bleeding-edge” workflows where contributors and early adopters need to see trunk and experimental branches as they evolve. - New Query API parameter: - `gutenberg-branch=trunk` → loads the current trunk build. - `gutenberg-branch=branch-name` → loads a named branch (e.g., `add/new-feature`). - Existing PR support remains: - `core-pr=####` for WordPress Core PRs. - `gutenberg-pr=#####` for Gutenberg PRs. - Behind the scenes, the environment is built from the latest successful GitHub Actions artifact for that branch, not necessarily the tip commit. - This design prioritizes dependable previews over the absolute newest commit, so tests and demos are less likely to break due to a failing CI build. - Intended usage contexts: - QA and regression testing ahead of release, especially against trunk. - Trying out experimental blocks/features that live on non‑merged branches. - Documentation and tutorials that embed or link to a Playground session matching an in-progress Gutenberg state. - Educational environments where learners can experiment without touching a local install. - The article positions Playground as a browser-based “lab” where contributors can explore merged changes quickly, then “report issues early, and contribute to WordPress development—all from your browser.” --- ## 📚 References - WordPress Playground announcement: “Preview Gutenberg Development Branches in Your Browser” — https://make.wordpress.org/playground/2025/11/26/preview-gutenberg-development-branches-in-your-browser/ - WordPress Playground: https://playground.wordpress.net/ - Gutenberg GitHub repository: https://github.com/WordPress/gutenberg - WordPress Core Trac / GitHub mirrors for PR context: - Core: https://github.com/WordPress/wordpress-develop - Gutenberg PRs: https://github.com/WordPress/gutenberg/pulls --- ## 🗣️ Paraphrase - Paragraph A paraphrase. - WordPress Playground can now load any Gutenberg development branch straight in the browser, letting you test trunk or featur - Summary: WordPress Playground now loads Gutenberg development branches directly in your browser. Test the latest trunk changes or explore feature branches without creating a pull request or setting up a loc… - URL: https://make.wordpress.org/playground/2025/11/26/preview-gutenberg-development-branches-in-your-browser/ WordPress Playground now loads Gutenberg development branches directly in your browser. Test the latest `trunk` changes or explore feature branches without creating a pull request or setting up a local environment. This solves a common challenge: testing bleeding-edge Gutenberg development typically requires cloning repositories, running build scripts, and managing local installations. Now you can skip all that. ##### Why does this matter? New features land `trunk` daily, and experimental work occurs in feature branches before being merged into pull requests. Previously, you could only preview specific PRs in Playground, and now you can preview any branch. This opens new possibilities: * Test the Gutenberg `trunk` branch to catch issues before they reach release. * Explore Gutenberg experimental features and fixes before they’re merged. ##### How do you preview branches? Playground introduces two new [Query API](https://wordpress.github.io/wordpress-playground/developers/apis/query-api/) parameters `gutenberg-branch`. Add them to your Playground URL to load specific branches. **Preview Gutenberg trunk or a specific feature branch:** ``` https://playground.wordpress.net/?gutenberg-branch=trunk ``` Other branches: ``` https://playground.wordpress.net/?gutenberg-branch=add/new-feature ``` ##### What about pull requests? Pull request previewing still works exactly as before for Gutenberg and WordPress core. If you know the PR number, use: ``` https://playground.wordpress.net/?core-pr=9500 https://playground.wordpress.net/?gutenberg-pr=73010 ``` ##### What should you know? When you preview a branch, Playground loads the latest available build artifact from GitHub Actions. If GitHub Actions is still building the most recent commit, Playground uses the next available build. This means you might see changes from a few commits back, not the absolute latest code. This approach strikes a balance between freshness and reliability. This feature works anywhere you use the Playground Query API, ideally, for testing and bug reporting. The playground can be embedded for educational purposes in future releases. For example, if you’re documenting a new Gutenberg feature still in `trunk`, link directly to a Playground instance that demonstrates it. ##### Start testing today The WordPress and Gutenberg teams constantly ship improvements. With branch previewing, you can explore these changes the moment they merge, report issues early, and contribute to WordPress development—all from your browser. Try it now and learn more about [Query API documentation](https://wordpress.github.io/wordpress-playground/developers/apis/query-api/). Some content could not be imported from the original document. [View content ↗](https://widgets.wp.com/likes/?ver=15.3-a.5#blog_id=234157394&post_id=325&origin=make.wordpress.org&obj_id=234157394-325-692b35947fb47), Preview Gutenberg Development Branches in Your Browser, WordPress Playground, 01kb8cjpc9414qqn0s7vtfsbn9.