Add blurb clarifying various project docs

[eharkins]

Description of proposed changes

1. Add a blurb making it clear what information should go in the nextstrain.org documentation vs augur, auspice.
2. fix local static site build instructions. Despite my changes to the static site build instructions, I think this importing code from auspice-client/customisations into the static-site means we have to install the root repo node dependencies in addition to the static-site ones even if we just want to run the static site (i.e. if someone is following the instructions in the document in question here with a fresh clone). Although perhaps there is a way to set up node dependencies so this isn't necessary? If not we should change the instructions to something like npm ci && cd static-site && npm ci

Related issue(s)

#164

Testing

Locally with gatsby + testing links work

Thank you for contributing to Nextstrain!

[eharkins]

Despite my changes to the static site build instructions, I think this importing code from auspice-client/customisations into the static-site means we have to install the root repo node dependencies in addition to the static-site ones even if we just want to run the static site (i.e. if someone is following the instructions in the document in question here with a fresh clone).

Given this, @jameshadfield and I have been discussing a good way to have the instructions until we have a better solution (see #158).

James suggests something along the lines of:

cd nextstrain.org
npm run install
npm run build # builds both auspice _and_ the static site
npm run server # see essentially a nextstrain.org clone

Along with a separate section for the dev server that says something like: “there’s a development server version as well, but it’s not perfect… here’s how you can use this”

[tsibley]

👍 for the install + build + server approach. That's what I've always done locally, as running the two "apps" separately doesn't realistically test changes anyway. (It's also possible to setup automatic re-runs of the build + server steps when files change, which I've used from time to time instead of hot reloading.)