I felt like this document should be referenced in the README so that new users don't have to go looking for it.
**Summary**
I had to look around for this file, some people might not!
**A picture of a cute animal (not mandatory but encouraged)**
Me and my dogs:
* 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
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.
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.
<!--
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**
Add Plugin Contributor https://github.com/hennessyevan/netlify-cms-widget-youtube
<!--
Explain the **motivation** for making this change.
What existing problem does the pull request solve?
-->
**- Test plan**
<!--
Demonstrate the code is solid.
Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
-->
**- Description for the changelog**
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
**- A picture of a cute animal (not mandatory but encouraged)**
