You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just being present in this repository and on the #meta-playground slack channel
Here’s a quick summary of the current state of WordPress Playground:
Vision and Roadmap for Playground are both in place, the latter will likely continue to evolve.
Documentation exists and got good feedback. I also opened a GitHub issue to collaborate with the WordPress.org documentation team.
Github actions exists for deploying the documentation site, Playground npm packages, and the Playground website.
wp-now recently served ~70 people on @luisherranz workshop and we’ve only seen a single technical issue. @danielbachhuber and the team behind the tool will focus on gathering feedback and making sure no critical issues arise. Any framework-level problems will be escalated to the core Playground repository (this one)
The interactive code block got approved for WordPress plugins directory. I will mark it as public before my leave and I would love to eventually see it enabled in courses on Learn.WordPress.org .
This isn't technically an issue but I'm publishing it as such for visibility.
I’ll be starting my 3 months sabbatical on Friday, June 23rd. @dmsnell will be watching over WordPress Playground while I’m away. This includes:
Here’s a quick summary of the current state of WordPress Playground:
The text was updated successfully, but these errors were encountered: