* Move spell/link checking docs to README: It seems more natural to put these along
with the build instructions and it reduces the size of the contributing
section (which is already a fair bit to read).
* Refactor/redo 'contributing': Seperate style guide from other contributing advice,
and expand
it
Co-authored-by: Mark Reid <mreid@mozilla.com>
Co-authored-by: Elke Vorheis <evorheis@mozilla.com>
This type of information belongs in the top-level README in my
opinion -- more than once I've checked out the repository and
fumbled on how to get back to the contributing section on how
to actually view my changes.
This includes quite a number of things, but the main goals were:
* update, fix, or remove references to deprecated tools (like ATMO)
* Add GCP data platform reference material, and shift the focus from the AWS pipeline to the GCP one
* General cleanup, such as splitting long lines and using like references instead of inline links.
Other things:
* document `sample_id`
* Fix a bunch of broken links
* Update projects page
* Fix broken links
* Fix dead links reported by wbeard
* Add google analytics
* Add style guide
* Add deploy notes
* Direct README to contributing docs
* Fix up some spelling and formatting errors
* small fixes to build instructions and links
- added sample_id as constraint in sample query
so it's not misread as an int field
- intro link should fix#31
Github.com uses the top level README.md for the main description of this
repository. This change configures GitBook to use ./introduction.md as
the book README and provides a more helpful README.md for readers
visiting the Github repository.
Jan-Erik Rediger
Jan-Erik Rediger
Tim D. Smith
William Lachance
Teon L Brooks
Mark Reid
William Lachance
Ryan Harter
Chris Beard