Refine workflow and associated documentation

[gemfarmer]

• refine server and build scripts
  • Currently site developers are either using the following commands to serve the project locally:
    • bundle exec jekyll serve: this does the trick, but is long, and rebuilds the jekyll-archives entirely, instead of incrementally.
    • ./serve: shorter, and removes the jekyll-archives gem to avoid building or rebuilding archives. This works great for development, but has the unfortunate side-effect of modifying the Gemfile.lock.
• add/edit server and build script documentation. Even if there are multiple ways to run the site, there should only be one method documented.
• add/refine contributing documentation

[gemfarmer]

After giving this a little more consideration, I think that jumpstarting the site differently in development vs CircleCI/production shouldn't be an issue as long as the documentation prevents us from overwriting the Gemfile.lock every PR.

@gboone @mugizico does that make sense to both of you?

[gemfarmer]

We discussed forking the PR here for incremental jekyll archives builds instead of continuing to modify the build script.

cc @gboone

[gemfarmer]

Started working on 18F version of Jekyll archives. So far it isn't speeding up regeneration.

[coreycaitlin]

Blocked: waiting for response from the plugin developer.

[gemfarmer]

See #1849 for more info on why this is blocked

[coreycaitlin]

Closing this out — it's in much better shape! 🎉