Move to mkdocs

[maebert]

This PR moves the documentation to MkDocs. This has several advantages:

• Significantly easier and faster build process than sphinx
• Docs are written in Markdown instead of ReST, which lowers the barrier to entry for new contributors
• Direct deployment to github-pages

Development

pip install mkdocs
make html # opens the docs and live-reloads
make docs # builds docs and deploys them to gh-pages

This PR also

• Consolidates doc edits from master, rc1, and rc2
• Simplifies and modernizes the landing page
  
• Modernizes the assets
• Includes wonderful social banners for sharing on Twitter, Facebook, etc:
  
• Switches to a modified ReadTheDocs theme that fixes some readability issues (turns out the web has changed quite a bit since 2012...):
  

[maebert]

@wren @micahellison Anything blocking this merge? It doesn't touch functionality, but it consolidates a lot of doc edits from various branches to get a clean slate.

[wren]

@maebert Nope, I think this is a good idea. It's only held up by organizing the backlog, which has been my priority so far.

Although, I'm just a little confused about why jrnl.sh looks like it's already updated. I thought that wasn't supposed to happened until this PR was merged?

Also, I think this PR should be against master (I updated it), and it looks like it might need some rebasing.

[maebert]

@wren Oh damn, I think I accidentally deployed that form my branch while testing :-/

Rebased against master, should be good to go now.

[wren]

?

[wren]

lgtm

We should update that one line at some point, though.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.