Playground Meeting Summary: June 13, 2025


The Playground team held its first meeting in a while on Friday, June 13, 2025, at 15:00 UTC. The discussion covered recent developments, contributor updates, and an open floor for questions.

Announcements

Several recent updates and resources for WordPress Playground were shared:

  • Workshops: Two recent workshops from WordCamp Europe were highlighted:
  • Recent Developments: A June 2025 “What’s new for developers?” post detailed several Playground enhancements:
    • Direct support for data URLs in the blueprint-url query parameter.
    • The PHP environment now includes the Intl extension.
    • A new SQLite driver has been integrated, with more details in this post.
    • The CLI now supports mounting the current working directory.
    • Dynamic mounting of symlinked directories is now supported.
  • Major Update: A significant recent update also included 64-bit integer support, the exif extension, a Blueprint bundle format, and numerous stability improvements.

Contributor Updates

Team members shared their current focus:

  • @zieladam is concentrating on Blueprints v2, including the specification and an all-in-one-php-blueprints.phar runner that can work on any PHP web host. The next steps involve improving Playground CLI compatibility with native PHP.
  • @fellyph is in his first week of contributing and has been triaging issues. He is also looking into requests for contributor badges, documentation updates, a potential landing page for new users, and has submitted a fix for the mobile view.
  • @karthickmurugan noted he has been unable to contribute recently due to other project work but hopes to schedule time for contributions soon.

Open Floor

@janwoostendorp shared his positive experience with the WordCamp Europe workshops and has started writing automated tests for his Default Featured Image plugin. He raised a performance question, noting that his tests take about 12 seconds to run in a CI environment, with roughly 8 seconds spent downloading a theme.

@zieladam explained that themes are not currently cached in the CI, but this will be resolved in Blueprints v2, which will implement an HTTP cache for all resources, not just WordPress core. This will result in a significant speed improvement once the Playground CLI is updated. As a temporary workaround for faster local development, he suggested using a local theme .zip file with a bundled reference in the blueprint.