To get started editing this site, you'll need Node v12+. We recommend using nvm.
Once that's installed, you'll need yarn as well.
Start developing by initializing your node modules:
yarnThen start the gatsby development server:
yarn build
yarn developPlenty of information may show, but you should eventually see something like:
You can now view gatsby-starter-default in the browser.
⠀
http://localhost:8000/
⠀You can edit the site by editing the files in src/. This site uses CSS, JS, and css-in-js.
💡 Note that for most images, you'll want to run
yarn buildbefore they show up correctly on the development site.
If you're here to write some of our plentiful documentation, use these foolproof steps:
- Ensure you've completed the Quick Start above, and have a server running.
- Make a new branch for your new document post.
- Create a new directory (or sub-directory, or sub-sub-directory) in
src/docslikemy-doc - Create an
index.mdfile insrc/docs/my-doc(or whatever you named your doc). This will be your document's markdown page. - Write the frontmatter for the page like so:
---
title: "My Snazzy Article"
---- Optionally, include any assets you need (images, etc) alongside
index.md, and reference them directly, eg:[my-image](./my-image) - Watch your markdown come to life in your browser by visiting the corresponding path to your document from
/docs(in this case, we'd visitdocs/my-doc) - When satisfied, commit the result for review.
As long as permissions work and everything is aligned in the stars, you ought to be able to deploy with:
yarn deployIf you see strange behavior from developing or building the app, try npx gatsby clean. This should use the gatsby-cli to clean out frayed node modules or other unexpected hitches.