Move the docs to WordPress.org (#3381)

You've served us well, docutron, but it's time to move.

The docs now live here: https://wordpress.org/gutenberg/handbook/

Author: pento

.travis.yml

@@ -63,16 +63,3 @@ jobs:
         - npm install || exit 1
         - npm run build || exit 1
         - ./bin/run-e2e-tests.sh || exit 1
-
-before_deploy:
-  - npm install
-  - cd docutron
-  - npm install
-  - cd ../
-  - npm run docs-build
-
-deploy:
-  provider: surge
-  project: ./docutron/build/
-  skip_cleanup: true
-  domain: gutenberg-devdoc.surge.sh

CONTRIBUTING.md

@@ -102,18 +102,6 @@ If you'd like to contribute to the design or front-end, feel free to contribute
 
 ### Contribute to the Documentation
 
-We're using an internal tool called `docutron` to generate the [Gutenberg Documentation Website](http://gutenberg-devdoc.surge.sh). You can run a local version of this website by cloning the repository and then running :
+Documentation is automatically synced from master to the [Gutenberg Documentation Website](https://wordpress.org/gutenberg/handbook/) every 15 minutes.
 
-```bash
-npm install && npm run docs-start
-```
-
-To add a new documentation page, you'll have to create a markdown file in the [docs](https://github.com/WordPress/gutenberg/tree/master/docs) folder and create a story referencing this file in the docs [stories file](https://github.com/WordPress/gutenberg/blob/master/docs/index.js) like so:
-
-```js
-addStory( {
-	name: 'story-name', // used in the url
-	title: 'Story Title',
-	markdown: require( './story-markdown-file.md' ),
-} );
-```
+To add a new documentation page, you'll have to create a Markdown file in the [docs](https://github.com/WordPress/gutenberg/tree/master/docs) folder and add an item to the [manifest file](https://github.com/WordPress/gutenberg/blob/master/docs/manifest.json).

README.md

@@ -12,7 +12,7 @@ This is the development hub for the <a href="https://make.wordpress.org/core/201
 
 WordPress already supports a large amount of "blocks", but doesn't surface them very well, nor does it give them much in the way of layout options. By embracing the blocky nature of rich post content, we will surface the blocks that already exist, as well as provide more advanced layout options for each of them. This will allow you to easily compose beautiful posts like <a href="http://moc.co/sandbox/example-post/">this example</a>.
 
-Check out the <a href="https://github.com/WordPress/gutenberg/blob/master/docs/faq.md">FAQ</a> for answers to the most common questions about the project.
+Check out the <a href="https://wordpress.org/gutenberg/handbook/reference/faq/">FAQ</a> for answers to the most common questions about the project.
 
 ## Contributors
 
@@ -24,7 +24,7 @@ Gutenberg is built by many contributors and volunteers. Please see the full list
 - <a href="https://make.wordpress.org/core/2017/05/05/editor-how-little-blocks-work/">How Blocks Work</a>
 - <a href="https://github.com/Automattic/wp-post-grammar">WP Post Grammar Parser</a>
 - <a href="https://make.wordpress.org/core/tag/gutenberg/">Development updates on make.wordpress.org</a>
-- <a href="http://gutenberg-devdoc.surge.sh/">Documentation: Creating Blocks, Reference, and Guidelines</a>
+- <a href="https://wordpress.org/gutenberg/handbook/">Documentation: Creating Blocks, Reference, and Guidelines</a>
 
 ## How You Can Contribute
 

blocks/README.md

@@ -52,7 +52,7 @@ to describe the behavior of your custom block.
 Note that all JavaScript code samples in this document are enclosed in a
 function that is evaluated immediately afterwards.  We recommend using either
 ES6 modules
-[as used in this project](https://github.com/WordPress/gutenberg/blob/master/docs/coding-guidelines.md#imports)
+[as used in this project](https://wordpress.org/gutenberg/handbook/reference/coding-guidelines/#imports)
 (documentation on setting up a plugin with Webpack + ES6 modules coming soon)
 or these
 ["immediately-invoked function expressions"](https://en.wikipedia.org/wiki/Immediately-invoked_function_expression)
@@ -237,7 +237,7 @@ editor interface where blocks are implemented.
 - `attributes: Object | Function` - An object of attribute schemas, where the
   keys of the object define the shape of attributes, and each value an object
   schema describing the `type`, `default` (optional), and
-  [`source`](http://gutenberg-devdoc.surge.sh/reference/attributes/)
+  [`source`](https://wordpress.org/gutenberg/handbook/reference/attributes/)
   (optional) of the attribute. If `source` is omitted, the attribute is 
   serialized into the block's comment delimiters. Alternatively, define 
   `attributes` as a function which returns the attributes object.

blocks/editable/index.js

@@ -84,7 +84,7 @@ export default class Editable extends Component {
 				`Invalid value of type ${ typeof value } passed to Editable ` +
 				'(expected array). Attribute values should be sourced using ' +
 				'the `children` source when used with Editable.\n\n' +
-				'See: http://gutenberg-devdoc.surge.sh/reference/attributes/#children'
+				'See: https://wordpress.org/gutenberg/handbook/reference/attributes/#children'
 			);
 		}
 

docs/design.md

@@ -220,4 +220,4 @@ If you'd like to contribute, you can download a Sketch file of the Gutenberg moc
 
 A pattern file is here:  **<a href="https://cloudup.com/c0Q8RQDHByq">Download Pattern Sketch file</a>**
 
-Be sure to also read <a href="https://github.com/WordPress/gutenberg/blob/master/docs/faq.md">the FAQ</a>, and <a href="http://gutenberg-devdoc.surge.sh/">how to build blocks</a>.
+Be sure to also read <a href="https://wordpress.org/gutenberg/handbook/reference/faq/">the FAQ</a>, and <a href="https://wordpress.org/gutenberg/handbook/">how to build blocks</a>.

docs/faq.md

@@ -51,7 +51,7 @@ Gutenberg will work in modern browsers, and Internet Explorer 11.
 
 ## How do I make my own block?
 
-The API for creating blocks is a crucial aspect of the project. We are working on improved documentation and tutorials. Check out the [Creating Block Types](http://gutenberg-devdoc.surge.sh/blocks/) section to get started.
+The API for creating blocks is a crucial aspect of the project. We are working on improved documentation and tutorials. Check out the [Creating Block Types](https://wordpress.org/gutenberg/handbook/blocks/) section to get started.
 
 ## Does Gutenberg involve editing posts/pages in the front-end?
 
@@ -97,7 +97,7 @@ Blocks will be able to provide base structural CSS styles, and themes can add st
 
 Other features, like the new _wide_ and _full-wide_ alignment options, will simply be CSS classes applied to blocks that offer this alignment. We are looking at how a theme can opt in to this feature, for example using `add_theme_support`.
 
-*See:* [Theme Support](http://gutenberg-devdoc.surge.sh/reference/theme-support/)
+*See:* [Theme Support](https://wordpress.org/gutenberg/handbook/reference/theme-support/)
 
 ## How will editor styles work?
 
@@ -146,7 +146,7 @@ If you would like to contribute to the accessibility of Gutenberg, we can always
 
 ## Are there any design resources for Gutenberg?
 
-Yes, primarily https://github.com/WordPress/gutenberg/blob/master/docs/design.md
+Yes, primarily https://wordpress.org/gutenberg/handbook/reference/design-principles/
 
 We are still adding more documentation.