Location: #playground Slack Channel
The WordPress Playground team held its weekly meeting on September 26, 2024. Here’s a summary of what was discussed.
Project Updates
Translation Progress
The team celebrated significant translation contributions from @Béryl, @rollybueno, @shimomura tomoki, and @Shail Mehta:
- 3 new pages in Japanese
- 2 new pages in French
- 2 new pages in Gujarati
- 5 new pages in Portuguese
Blueprints
Several improvements were made to Blueprints:
- Replace randomString() with randomFilename() in installAsset() – fixes an issue with random empty folders appearing
- Separate computing the runtime configuration from compiling a Blueprint
Playground Web Instance
Key updates to the web instance include:
- Disable curl_share_init by default (to make Composer work) –
composer.pharnow works in Playground - Resolve the Blueprint declaration for the ‘View Blueprint’ button
- Report Blueprint v2 progress
- Split Playground remote initialization logic into Blueprint version-specific workers
- Initial support for Blueprints v2 (can be tested at https://playground.wordpress.net/?experimental-blueprints-v2-runner=yes&php=8.3#{%22version%22:2})
Other Updates
- PHP Worker: listen to all PHP instances events via worker.addEventListener()
- Declare the correct Blueprints v2 types
- Website: Isolate resolveBlueprintFromURL() calls
- Client: Explicit Blueprints v1 handler
- Fix Playground CLI boot from native dirs on Windows
- Client: Expose Blueprints v2 runner via a feature flag
Documentation
@fellyph added steps to translate docs using the GitHub UI, making it easier for contributors to participate in the translation efforts.
Team Updates
@janjakes is attending a meetup and continuing work on a PHP implementation of the MySQL protocol to enable tools like phpMyAdmin to run with SQLite. This requires completing column metadata implementation.
@zieladam worked on:
- Running Blueprints v2 on playground.wordpress.net
- Supporting
composer.phar - A Playground-based desktop app to help new WordPress contributors write their first patch
- Various stability improvements
@fellyph worked on:
- Adding new pages for Brazilian Portuguese
- Assisting community members with creating pull requests
- Creating a guide for translating with the GitHub UI
- Planning for the upcoming Playground meetup
Open Floor
The team discussed several topics:
Documentation preferences: Team members shared documentation they admire from the PHP ecosystem, including Svelte tutorials, Vue docs, Laravel documentation, and Symfony docs.
AI for PR triage: The team discussed using AI to perform initial triage on pull requests related to translations.
Use cases beyond WordPress: There was interest in showcasing more use cases in documentation that focus on PHP and Node outside the WordPress ecosystem.
Feature idea: @zieladam suggested that https://playground.wordpress.net/php-playground.html could include a file browser and terminal for simple commands like wp user list or composer require, providing a nice way to experiment with PHP packages.
Next Steps
The conversation continues in the #playground Slack Channel. Community members interested in contributing to WordPress Playground can join the discussion there.