Remove editorial workflow doc

Contents moved to config options and architecture docs

website/site/content/docs/architecture.md

@@ -62,4 +62,17 @@ The control component receives three (3) callbacks as props: `onChange`, `onAddA
 
 Both control and preview widgets receive a `getAsset` selector via props. Displaying the media (or its URI) for the user should always be done via `getAsset`, as it returns an AssetProxy that can return the correct value for both medias already persisted on the server and cached media not yet uploaded.
 
-The actual persistence of the content and medias inserted into the control component is delegated to the backend implementation. The backend will be called with the updated values and a list of assetProxy objects for each field of the entry, and should return a promise that can resolve into the persisted entry object and the list of the persisted media URIs.
+The actual persistence of the content and medias inserted into the control component is delegated to the backend implementation. The backend will be called with the updated values and a list of assetProxy objects for each field of the entry, and should return a promise that can resolve into the persisted entry object and the list of the persisted media URIs.
+
+
+## Editorial Workflow implementation
+
+Instead of adding logic to `CollectionPage` and `EntryPage`, the Editorial Workflow is implemented as Higher Order Components, adding UI and dispatching additional actions.
+
+Furthermore, all editorial workflow state is managed in Redux - there's an `actions/editorialWorkflow.js` file and a `reducers/editorialWorkflow.js` file.
+
+### About metadata
+
+Netlify CMS embraces the idea of Git-as-backend for storing metadata. The first time it runs with the editorial_workflow setup, it creates a new ref called `meta/_netlify_cms`, pointing to an empty, orphan tree.
+
+Actual data are stored in individual `json` files committed to this tree.

website/site/static/_redirects

@@ -1,3 +1,4 @@
 /docs/custom-authentication /docs/authentication-backends 301
 /docs/extending /docs/custom-widgets 301
-/docs/validation /docs/custom-widgets/#advanced-field-validation 301
+/docs/validation /docs/custom-widgets/#advanced-field-validation 301
+/docs/editorial-workflow /docs/configuration/#publish-mode 301