-
Notifications
You must be signed in to change notification settings - Fork 260
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove wp-now from the repository. See #473.
- Loading branch information
Showing
94 changed files
with
3,655 additions
and
10,183 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -83,6 +83,40 @@ only pull the latest revision of the trunk branch: | |
git clone -b trunk --single-branch --depth 1 [email protected]:WordPress/wordpress-playground.git | ||
``` | ||
|
||
## Vision | ||
|
||
Make WordPress instantly accessible for users, learners, extenders, and contributors by building foundational software tools developers can use to create interactive, zero-setup, JavaScript applications with WordPress. | ||
|
||
More specifically, here is a preliminary outline of the areas Playground will focus on. These items are not set in stone, and your feedback and contributions are crucial to help shape the direction. | ||
|
||
### Learning WordPress Through Exploration | ||
|
||
Playground aims to shift the WordPress learning journey from following screenshots and videos into engaging with a live site where it's safe and easy to creatively explore the concepts being taught. | ||
|
||
Imagine live Playgrounds that guide users through building their first website, customizing a theme, or setting up an e-commerce store. Furthermore, users would have the freedom to take a detour and explore on their own. The goal is to not to create specific tutorials or apps, but rather to empower developers with the tools necessary to build them. | ||
|
||
Key features include support for pre-defining an initial site setup and the ability to provide step-by-step interactive instructions. | ||
|
||
|
||
### Learning WordPress Development Through Writing Code | ||
|
||
Playground aims to encourage and accelerate learning WordPress development. | ||
|
||
Imagine an in-browser code editor with an instant preview of everything you build. New developers would be guided through building their first WordPress extensions, and experienced developers would hone their WordPress skills with live code snippets and interactive examples embedded in the documentation and tutorials. Furthermore, developers would be able to start developing locally with zero or almost zero setup steps. | ||
|
||
The goal is not to build such a full-featured code editor in Playground, but rather to provide the tools necessary to build one. | ||
|
||
Key features include running PHP code in Playground, an abstraction for synchronizing files with a Playground instance, and a PHP binary that supports CLI tools like wp-cli or phpunit. | ||
|
||
|
||
### Instant access to WordPress ecosystem | ||
|
||
Playground aims to empower developers to build WordPress applications that are available in an instant and without any server infrastructure. | ||
|
||
WordPress ecosystem consists of many powerful extensions that could become accessible without any pre-requisites. Imagine using WordPress as a notes app, getting acquainted with plugins and themes through official live demos, or starting a full-featured development environment with a single-click. The goal is not to build such applications, but to empower the ecosystem to make them available on demand. | ||
|
||
Key features include abstraction for integrating a custom filesystems, in-browser support for network requests, and the ability to use and configure specific PHP extensions. | ||
|
||
## Contributing | ||
|
||
You also can run WordPress Playground locally as follows: | ||
|
@@ -139,10 +173,6 @@ Another strong inspiration was the [Drupal in the browser demo](https://seanmorr | |
|
||
A worthy mention is Wasm Labs’s closed-source [WordPress in the browser](https://wordpress.wasmlabs.dev/) shared before this project was first published. There is no public repository available, but their [technical overview](https://wasmlabs.dev/articles/wordpress-in-the-browser/) gives a breakdown of the technical decisions that project took. WordPress Playground draws inspiration from the same PHP in the browser projects and makes similar technical choices. | ||
|
||
## Using WP-NOW for local environment | ||
|
||
WordPress Playground comes with `wp-now`. `wp-now` is a Command Line Interface (CLI) tool designed to streamline the process of setting up a local WordPress environment by using only Node.js. If you are looking to set up `wp-now` specifically, you can follow [this README.md](/packages/wp-now/README.md). | ||
|
||
## Contributing | ||
|
||
WordPress Playground is an ambitious project in its early days. If the feature you need is missing, you are more than welcome to start a discussion, open an issue, and even propose a Pull Request to implement it. |
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.