(outdated) Playground Roadmap #131
Comments
|
Thank you so much for this fantastic writeup @artemiomorales! 💯 It summarizes all the directions and ideas really well. |
|
Based on feedback, I updated the Interactive WordPress Courses description to temper expectations on how much impact this feature may have in reality and to be more specific. Before
After
|
|
Many items from this early roadmap were resolved and it's time for a new direction and a new roadmap. The new roadmap is available in #525. It reflects the Playground's goal to be a foundational tool that empower developers of interactive, zero-setup, and accessible software tools based on WordPress. Some tools, like wp-now, are developed in the playground-tools repo and some, like Live Translations, are explored by open-source extenders. Big shout out to everyone who contributed – you made it possible for Playground to become what it is today! 🎉 |
Users should be able to get high-level overview of where Playground currently stands. We can use this issue to provide that overview, with the aim of facilitating discussion, contributions, and a general sense of where this project is headed.
I'll summarize prior discussions as well as I can, though please feel free to provide your own thoughts and feedback as well.
Overall Vision
WordPress Playground aims to help make interacting with WordPress as seamless as possible, providing support in areas including learning, design, and development, in order to empower users at all levels of experience across the WP community.
For additional background on this vision, see @adamziel's introductory post.
Strategy
Our current strategy with Playground is to act as a startup. The idea is to stand up features as quickly as possible, gather feedback from users, and based on that, identify which areas of Playground can provide the greatest impact so we can prioritize further development accordingly.
This means that onboarding new contributors for the time being is less important than creating initial features that will allow us to get more enthusiasm and feedback for the project.
Target Experiences
At the moment, our goal is to create the building blocks to be used in enabling broad kinds of experiences.
Here follow key experiences we're targeting and links to issues that comprise them. Note: Many of the identified issues are applicable in more than one scenario.
Interactive WordPress Courses
Users should be able to learn aspects of WordPress, whether at the beginner or expert level, directly on web pages where the course material is hosted without needing to set up a custom development environment. This would enable instant learning experiences that could be the deciding factor for new developers to learn and contribute to WordPress over the competition.
Learning WordPress isn’t easy. You have to set up the environment, find the right courses, and connect all the dots by yourself. This drives a lot of people away. With a guided, interactive experience, many of them would stay.
To accomplish this, teachers would ideally have the ability to implement full WordPress development environments in the browser as part of their educational materials. This is something we can work towards; stepping stones include being able to run code snippets and embed less fully featured Playground instances.
Relevant Issues
WordPress Previewer
Users should be able to preview plugins, themes, and full site editing customizations purely in browser without needing to implement those changes on a live, staging, or local instance of WordPress. Furthermore, they should be able to export their browser preview so they can share it with others or import it into a server-powered WordPress instance.
Relevant Issues
Additional Experiences and Notes
While our focus is on the targets above, here follow additional experiences and points of consideration that have bearing on project development.
Cloudfest Hackathon
From March 18-20, @adamziel and Daniel Bachhuber will lead an initiative to create a full WordPress in-browser development environment at the CloudFest Hackathon, where they'll tackle many of the issues in this post. This is particularly relevant for Interactive WordPress Courses.
In-Browser Bug Reporting
Users should be able to reproduce bugs in Playground and export the state so it can be shared in bug reports with relevant parties on the development side. Developers should then be able to build frontends to import that data and see the bugs reproduced in their own Playground instances. This would greatly improve the workflow for identifying and fixing bugs.
Relevant Issues
In-Browser Testing
Users should be able to easily preview pull requests in the WordPress and Gutenberg repositories using Playground, as well as include pull request-specific data in the Playground instance.
Relevant Issues
Translation Workflows
Users should be able to view and edit translations in browser, as well as be able to migrate Playground modifications back into server-powered WordPress instances.
Relevant Issues
Interactivity API Course
As Interactive WordPress Courses become supported, we think creating an introduction to the upcoming interactivity API could be a great use case for both showcasing Playground and providing an easy onramp to introduce developers to the new concepts.
Relevant Issues
Conclusion
This is meant to be a living issue and its primary purpose at the moment is to capture the breadth of the Playground project and give an idea of how the pieces fit together. I would love to hear everyone's feedback so we can include that input in this roadmap and discussion. Thanks! 🙏
The text was updated successfully, but these errors were encountered: