Feature/remove editorial workflow (#8)

This commit is contained in:
Daniel Lautzenheiser
2022-10-01 13:45:01 -04:00
committed by GitHub
parent 5e6164efc4
commit 10b442428a
116 changed files with 344 additions and 7362 deletions

View File

@ -95,17 +95,6 @@ backend:
The configuration above specifies your backend protocol and your publication branch. Git Gateway is an open source API that acts as a proxy between authenticated users of your site and your site repo. (We'll get to the details of that in the [Authentication section](#authentication) below.) If you leave out the `branch` declaration, it defaults to `master`.
### Editorial Workflow
**Note:** Editorial workflow works with GitHub repositories, and support for GitLab and Bitbucket is [in beta](/docs/beta-features/#gitlab-and-bitbucket-editorial-workflow-support).
By default, saving a post in the CMS interface pushes a commit directly to the publication branch specified in `backend`. However, you also have the option to enable the [Editorial Workflow](../configuration-options/#publish-mode), which adds an interface for drafting, reviewing, and approving posts. To do this, add the following line to your Simple CMS `config.yml`:
```yaml
# This line should *not* be indented
publish_mode: editorial_workflow
```
### Media and Public Folders
Simple CMS allows users to upload images directly within the editor. For this to work, the CMS needs to know where to save them. If you already have an `images` folder in your project, you could use its path, possibly creating an `uploads` sub-folder, for example: