gcg/static-cms
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(fix): revert prettier formatting on markdown files (#1612)

Browse Source 
Prettier formatting our markdown files is causing bugs because of the
differences between Gatsby's parser and Prettier's. Also, Prettier
formats the inline code-blocks containing example CMS configs, but the
formatting it uses doesn't really make much sense or match the suggested
CMS config style.

It doesn't actually make much sense to format the docs anyway, since we
use the CMS itself to edit/generate them.
This commit is contained in:
Caleb
2018-08-14 11:33:13 -06:00
committed by GitHub
parent dd56d6e2d9
commit ebc2471c6b
40 changed files with 452 additions and 502 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
website/content/docs/update-the-cms-version.md
View File

@ -15,12 +15,11 @@ If you are using a package manager like Yarn or NPM, you will use their standard
If you are using the CMS through a CDN like Unpkg, then that depends on the version tag you are using. You can find the version tag you are using in the `/admin/index.html` file of your site.
- (Recommended) If you use `^2.0.0`, the CMS will do all updates except major versions automatically.
- It will upgrade to `2.0.1`, `2.1.0`, `2.1.2`.
- It will not upgrade to `3.0.0` or higher.
- It will not upgrade to beta versions.
- It will upgrade to `2.0.1`, `2.1.0`, `2.1.2`.
- It will not upgrade to `3.0.0` or higher.
- It will not upgrade to beta versions.
- If you use `~2.0.0`, the CMS will do only patch updates automatically.
- It will upgrade `2.0.1`, `2.0.2`.
- It will not upgrade to `2.1.0` or higher.
- It will not upgrade beta versions.
- It will upgrade `2.0.1`, `2.0.2`.
- It will not upgrade to `2.1.0` or higher.
- It will not upgrade beta versions.