Contributions are always welcome, no matter how large or small. Before contributing, please read the code of conduct.
Install yarn on your system: https://yarnpkg.com/en/docs/install
Only required on the first run, subsequent runs can use
yarn
to both bootstrap and run the development server usingyarn develop
. Since this starter using the netlify-lambda, there could be further issues you, please check the Readme for further information and set up questions.
$ git clone https://github.com/netlify-templates/gatsby-starter-netlify-cms
$ yarn
Starts the development server. This task runs both the start:app
and start:lambda
scripts.
$ yarn start
Build the static files into the public
folder, turns lambda functions into a deployable form. This task runs both the build:app
and build:lambda
scripts.
$ yarn build
Removes all the files from public
, .cache
directories using the rimraf
command.
yarn clean
Runs the clean
script and starts the gatsby develop server using the command gatsby develop
. Since this is not starting the lambda server it can be used when you only changing the site and not the lambda functions.
yarn develop
This command is shorthand for gatsby serve
yarn serve
Not implmented yet
yarn test
Formats code and docs according to our style guidelines using prettier
yarn format
Runs the develop
command, this mapping is needed so we can start both gatsby and lambda with one command (yarn start
).
yarn start:app
Runs the netlify-lambda
command, starts the lambda server in develop mode.
yarn start:lambda
Builds the gatsby app
yarn build:app
Runs the netlify-lambda build
command, compiles the functions.
yarn build:lambda
We actively welcome your pull requests!
If you need help with Git or our workflow, please ask on Gitter.im. We want your contributions even if you're just learning Git. Our maintainers are happy to help!
Netlify CMS uses the Forking Workflow + Feature Branches. Additionally, PR's should be rebased on master when opened, and again before merging.
- Fork the repo.
- Create a branch from
master
. If you're addressing a specific issue, prefix your branch name with the issue number. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Run
yarn test
and ensure the test suite passes. (Not applicable yet) - Use
yarn format
to format and lint your code. - PR's must be rebased before merge (feel free to ask for help).
- PR should be reviewed by two maintainers prior to merging.
By contributing to the Gatsby - Netlify CMS starter, you agree that your contributions will be licensed under its MIT license.