Create comprehensive documentation

[coddingtonbear]

Currently, this repository relies on just a simple readme and a few basic examples. Additionally, given that this library is composed of parts made by a variety of people, various components use different styles. If a documentation repository existed, several existing problems might be fixed including:

• Code & API style inconsistencies: Much of this library has been contributed by community members and follows their personal styles instead of matching the idiosyncratic style of this library. Ideally, the library would follow a documented style that could be pointed-at when performing code reviews.
• Testing standards: Right now, I'm not even sure what the test coverage of this library is, and general PRs often include no tests. This is understandable given that testing standards are not documented here, and it's perhaps unclear how to easily make tests given how this library relies on scraping a web interface.
• Documentation standards: Rarely do new PRs document the feature they're adding. Ideally, contribution guidelines would exist that would make it clear that that documentation should be included in each submitted PR.

[coddingtonbear]

Added! At the moment, I've left "Testing standards" minimally-specified -- mostly because I'm not super sure how to make testing a library like this easy -- but this'll have to do for the moment.