Try implementing a built-in Gutenberg playground (#14497)

WordPress · Mar 25, 2019 · 8625b82 · 8625b82
1 parent e7141f9
commit 8625b82
Show file tree

Hide file tree

Showing 11 changed files with 1,749 additions and 16 deletions.
diff --git a/.gitignore b/.gitignore
@@ -12,3 +12,6 @@ phpcs.xml
 yarn.lock
 docker-compose.override.yml
 /wordpress
+
+playground/dist
+.cache
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -114,6 +114,12 @@ You can pick among all the <a href="https://github.com/WordPress/gutenberg/issue
 
 The workflow is documented in greater detail in the [repository management](/docs/contributors/repository-management.md) document.
 
+## Playground
+
+The Gutenberg repository also includes a static Gutenberg playground that allows testing and developing in a WordPress-agnostic context. This is very helpful for developing reusable components and trying generic JavaScript modules without any backend dependency.
+
+You can launch the playground by running `npm run playground:start` locally. The playground should be available on [http://localhost:1234](http://localhost:1234).
+
 ## Testing
 
 Gutenberg contains both PHP and JavaScript code and encourages testing and code style linting for both. It also incorporates end-to-end testing using [Google Puppeteer](https://developers.google.com/web/tools/puppeteer/). You can find out more details in [Testing Overview document](/docs/contributors/testing-overview.md).