This post summarizes the Playground meeting held on December 12, 2025, in the #playground Slack channel
Announcements
WordPress 6.9 was released, and Playground supported testers and developers throughout the release process. At State of the Word 2025 on December 2nd, Matt Mullenweg highlighted Playground and recognized contributors for translating the documentation.
The team published several posts celebrating 2025:
- WordPress Playground: 2025 Year in Review covers major improvements and new features
- Adminer and phpMyAdmin in WordPress Playground introduce the experimental Database pane
- Introducing the New Live Blueprint Editor for WordPress Playground details the improved Blueprint editing experience
Playground videos on WordPress.tv are now categorized and easier to find.
The project now has 49 contributors with Playground badges.
GitHub updates
PHP-WASM
- Added smoke tests for
proc_openin CI - Support for PHP 8.5
- Removed static intl extension artifacts
- Disabled profiling data file generation at runtime
Playground CLI Support for Intl is now included.
Documentation
- Updated resources page with WordCamp Wroclaw presentation
- Removing references to github-proxy.com (service being discontinued)
- New translations added in Portuguese and Japanese
Website Improvements to database administration and the Blueprints Editor.
Blueprints Added support for Intl.
Contributor updates
@zieladam is pairing with @bpayton to implement multiple workers by default in the Playground CLI to increase speed. Once shipped, multiple workers may also work in the browser with SharedArrayBuffer support.
@Fellyph met with the Brazilian community to collect feedback, update GitHub Proxy references, write content for non-technical users, organize Playground videos, and review translations.
@andr3ribeiro started contributing this month with internationalization work and plans to help with technical issues after completing translations.
@Beryldlg is returning to publish the French translations of the documentation next week.
Open floor discussion
Documentation translation workflow
@Beryldlg raised questions about automatic translations and requested a way to receive notifications when documentation changes. This would help translation teams review and improve automated translations.
The team discussed:
RSS feed for documentation changes @zieladam created an RSS feed that refreshes daily to track documentation changes. @Fellyph Cintra will add this to the documentation.
Translation review process. The team agreed on a workflow where initial automated translations are published and improved over time. For accuracy:
- Human translations will include a footer signature (like the French translations)
- Automated translations will include a notice at the bottom
- Contributors can add translator comments for content that needs review, such as:
<!-- Translators, this is accurate but it also will change pretty soon: --><!-- Translators, this may not be fully accurate yet: -->
@Fellyph Cintra will create a footer component to distinguish between translation types.
Next steps
If you need help contributing to Playground, reach out to @Fellyph. The next Playground meeting scheduled for the 26th of December will move to the 9th of January. Join the conversation at #playground Slack channel.