diff --git a/Makefile b/Makefile index 58443e3e3..3545a4187 100644 --- a/Makefile +++ b/Makefile @@ -6,6 +6,7 @@ browserify = $(bin)/browserify exorcist = $(bin)/exorcist eslint = $(bin)/eslint http-server = $(bin)/http-server +gh-pages = $(bin)/gh-pages mocha = $(bin)/mocha mocha-phantomjs = $(bin)/mocha-phantomjs node = node @@ -42,6 +43,10 @@ dist: $(shell find ./lib) package.json examples: @ $(browserify) $(browserify_flags) ./examples/index.js --outfile ./examples/build.js +# Deploy the latest examples to GitHub pages. +gh-pages: + @ $(gh-pages) --dist ./examples + # Install the dependencies. install: @ npm install diff --git a/Readme.md b/Readme.md index 8b2f469ac..321f515e6 100644 --- a/Readme.md +++ b/Readme.md @@ -5,10 +5,10 @@

A completely customizable framework
for building rich text editors in the browser.


-

Why? · Principles · Examples · Plugins · Documentation · Contributing!

+

Why? · Principles · Demo · Examples · Plugins · Documentation · Contributing!


-

+


@@ -60,6 +60,12 @@ Slate tries to solve the question of "[Why?](#why)" with a few principles: 7. **Clear "core" boundaries.** With a plugin-first architecture, and a schema-less core, it becomes a lot clearer where the boundary is between "core" and "custom", which means that the core experience doesn't get bogged down in edge cases. +
+### Demo + +Check out the [**live demo**](https://ianstormtaylor.github.io/slate) of all of the examples! + +
### Examples diff --git a/package.json b/package.json index 5cd1a8af5..d9441d198 100644 --- a/package.json +++ b/package.json @@ -39,6 +39,7 @@ "eslint-plugin-import": "^1.10.2", "eslint-plugin-react": "^5.2.2", "exorcist": "^0.4.0", + "gh-pages": "^0.11.0", "http-server": "^0.9.0", "mocha": "^2.5.3", "mocha-phantomjs": "^4.0.2",