-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vision and Philosophy #472
Comments
… in a dedicated space. See #473. (#475) ## What? Removes the interactive-code-block project from the main WordPress playground repository so it can live in a dedicated space. As outlined in #473, WordPress Playground is re-focusing on [the vision](#472) and separating the framework from the applications. Once `interactive-code-block` is committed into a separate repo, a link will be added to this PR.
… dedicated space. See #473. (#476) ## What? Removes the VS Code extension from the main WordPress playground repository so it can live in a dedicated space. As outlined in #473, WordPress Playground is re-focusing on [the vision](#472) and separating the framework from the applications. Once the code removed by this PR is committed to a separate repo, a link will be added to this PR.
Previous changes to wp-now directory can be browsed at https://github.com/WordPress/wordpress-playground/tree/trunk/packages/wp-now Previous changes to bin directory can be browsed at https://github.com/WordPress/wordpress-playground/tree/trunk/bin ## What? Moves `wp-now` from the main WordPress playground repository to a dedicated space. As outlined in WordPress/wordpress-playground#473, WordPress Playground is re-focusing on WordPress/wordpress-playground#472 and separating the framework from the applications.
Previous changes to wp-now directory can be browsed at https://github.com/WordPress/wordpress-playground/tree/trunk/packages/wp-now Previous changes to bin directory can be browsed at https://github.com/WordPress/wordpress-playground/tree/trunk/bin Moves `wp-now` from the main WordPress playground repository to a dedicated space. As outlined in WordPress/wordpress-playground#473, WordPress Playground is re-focusing on WordPress/wordpress-playground#472 and separating the framework from the applications.
…space. See #473. (#477) ## What? Removes `wp-now` from the main WordPress playground repository so it can live in a dedicated space. This PR also removes VS Code extension – merge #476 first. As outlined in #473, WordPress Playground is re-focusing on [the vision](#472) and separating the framework from the applications. Once the code removed by this PR is committed to a separate repo, a link will be added to this PR.
… in a dedicated space. See #473. (#475) ## What? Removes the interactive-code-block project from the main WordPress playground repository so it can live in a dedicated space. As outlined in #473, WordPress Playground is re-focusing on [the vision](WordPress/wordpress-playground#472) and separating the framework from the applications. Once `interactive-code-block` is committed into a separate repo, a link will be added to this PR.
… dedicated space. See #473. (#476) ## What? Removes the VS Code extension from the main WordPress playground repository so it can live in a dedicated space. As outlined in #473, WordPress Playground is re-focusing on [the vision](WordPress/wordpress-playground#472) and separating the framework from the applications. Once the code removed by this PR is committed to a separate repo, a link will be added to this PR.
…space. See #473. (#477) ## What? Removes `wp-now` from the main WordPress playground repository so it can live in a dedicated space. This PR also removes VS Code extension – merge WordPress/wordpress-playground#476 first. As outlined in #473, WordPress Playground is re-focusing on [the vision](WordPress/wordpress-playground#472) and separating the framework from the applications. Once the code removed by this PR is committed to a separate repo, a link will be added to this PR.
@adamziel adding this to the docs info |
I've updated the description with a Mindmap of everything Playground can enable. I've also updated the project vision.
|
WordPress Playground Vision and Philosophy
Mindmap of everything Playground can enable
Vision
Bring WordPress to Everyone
Playground exists to bring WordPress to everyone—regardless of their skill level, platform, device, and internet speed.
WordPress should be instantly accessible to users, learners, extenders, and contributors with a single click. No pre-requisites, no installation wizards, no tricky errors.
For WordPress as we know it today, it means:
However, that's just the beginning. Playground can enable so much more.
With Data Liberation, WordPress will become your central content hub for everything from personal notes, to ebooks, to social posts—all stored locally and synced across your devices. With Playground's portability, it will always be a single click away, whether you're using a web browser, a native mobile app, or your favorite code editor running on a remote server. The goal is not to build such applications, but to build a solid platform that empowers the community to build them.
Key features include synchronizing data, WASI build, and mobile apps devtools.
Project philosophy
Focused Framework over Alluring Add-ons
Playground focuses on the minimum work required to fulfill its vision. Therefore, new features are evaluated based on the following question: Does it bring the project closer to its vision in the long run?
Every new feature, no matter how great, makes the codebase a little bit more difficult to approach and adds a little extra time to weekly maintenance. Saying yes to an appealing feature is tempting, but it means saying no to something else. Saying no is difficult, but it makes space for what's indispensable.
Therefore, Playground makes the difficult decision and chooses to focus on its vision – even when that means saying no.
Diligent Design over Quick Quirkiness
Let the long-term success of the project lead the solutions. Some changes can be done quickly, other require more time. Move as fast as the problem allows, but no faster. Move as slow as the problem requires, but not slower.
Developers are under all sorts of time pressures so let's be kind to our future selves. An hour of diligence today saves ten hours of maintenance tomorrow.
Modular Minimalism over Coupled Complexity
WordPress Playground follows the Unix philosophy:
As Antoine de Saint-Exupéry said, "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." Let's aim for this kind of perfection.
The text was updated successfully, but these errors were encountered: