* website: redo mobile nav to use Link and be rid of select input
* fix react className prop
* add zebapy to contributors
* website: upgrade gatsby deps to release candidate
* fix lint
* website: initial conversion to gatsby v2
* fix unexpected history use warning
* use commonjs only to fix gatsby error
* fix gatsby import error with sidecar
* remove unused postcss-colour-functions
* remove unused prop
* lowercase layout filename import to match actual file
* chore(lint): format code
The command `yarn start` is dependent on the `npm-run-all` package, therefore we can't recommend this as the first command someone runs after they just clone the repository in case they don't have it globally installed. Trying to `yarn start` without this package gets:
```
/bin/sh: run-s: command not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
```
Therefore, on first setup it is recommended to run `yarn bootstrap` as the first command.
<!--
Thanks for submitting a pull request!
Please make sure you've read and understood our contributing guidelines;
https://github.com/netlify/netlify-cms/blob/master/CONTRIBUTING.md
If this is a bug fix, make sure your description includes "fixes #xxxx", or
"closes #xxxx", where #xxxx is the issue number.
Please provide enough information so that others can review your pull request.
The first three fields are mandatory:
-->
**- Summary**
<!--
Explain the **motivation** for making this change.
What existing problem does the pull request solve?
-->
Was going through the quick-start and noticed 404 to links
**- Test plan**
<!--
Demonstrate the code is solid.
Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
-->
Just simple link changes.
**- Description for the changelog**
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
e.g Changed (https://netlifycms.org/docs/hello) to (/docs/hello)
**- A picture of a cute animal (not mandatory but encouraged)**
* Add hint to example admin config
* Add hint and hint position boolean above/below widget
* Style hint for both above and below widget
* Add hint and hint_above options to docs
* Remove hint above and make hint plaintext
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.
* dev: add GitHub detailed issue templates
* dev: update PR template
contributing guidelines link is already in PR UI
changelog message is no longer needed -- it is generated from commit messages
* dev: use bug report template on CMS crash
* Update bug_report.md
* docs(add-to-your-site): include verbose document links
- add extra references to config.yml
* docs(collection-types): provide consistent examples
- include link to configuration doc
- describe admin UI behaviour when accessing files
* docs(add-to-your-site): make authentication phrasing less biased
- add note regarding core behaviour fetching remote files
* docs(collection-types): add note about configurable branches
* docs(website): add more descriptive language to configuration notes
- include deep links to documentation where applicable
* docs(website): change link titles to match their target content
