Build public-facing documentation

[ryaanahmed]

We want, ideally, two things:

1. an easy-to-read user's guide / tutorial that walks a user through creating a simple project using our toolkit
2. comprehensive API documentation, probably automatically generated

We're going to use

• Sphinx (http://www.sphinx-doc.org/en/master/) to automatically generate docs from our code
• Read the Docs for hosting our documentation https://readthedocs.org/

[ryaanahmed]

I'm not assigning this now, but I'd suggest that the test projects you're creating this week can feed into the user's guide.

I'll do the initial Sphinx setup.

[ryaanahmed]

Outline doc for the user's guide: https://docs.google.com/document/d/1JXodqJZNiI76qbNnJhujHc4C8IN4V43S0xnZkm7vsk0/edit?ts=5d1b754e

[ryaanahmed]

Some good examples: http://web.mit.edu/music21/doc/usersGuide/usersGuide_01_installing.html https://guide.elm-lang.org/

[ryaanahmed]

https://gender-analysis.readthedocs.io/

[ryaanahmed]

@samimak37 -- Sphinx has a bunch of warnings that explain why some of the formatting is funky. You can install Sphinx into your venv with pip, and then go to documentation/source and run make html locally.

[ryaanahmed]

Let's add 'next' and 'previous' to the bottom of pages on the user's guide (i.e., so that users on the "Installation" page can click through to "tutorial" etc.)

[MBJean]

This issue is concluded as of PR #154. Closing.