Setup MKDocs for Documentation

[shyamd]

This is a simple barebones setup of mkdocs:

• Very simple index that is a copy of the readme
• Simple API reference docs using mkdocstrings
• Autogenerated changelog using PR names

[codecov]

Codecov Report

Merging #294 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #294   +/-   ##
=======================================
  Coverage   90.05%   90.05%           
=======================================
  Files          54       54           
  Lines        2273     2273           
=======================================
  Hits         2047     2047           
  Misses        226      226           

Flag	Coverage Δ
#unittests	90.05% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 17c3fe9...ead2465. Read the comment docs.

[ml-evs]

Is this the right URL? materials-consortia.github.io redirects to optimade.org, so I guess this should either go to optimade.org/optimade-python-tools (if we get someone to update the domain settings for us) or to optimade-python-tools.github.io?

[shyamd]

Oh, good point. I don't know what happens to project repo pages when the org page is redirected...

[ml-evs]

Any way we can test it before merging? Guess we need to enable Pages for this repo for one (will leave that to you when you're ready)

[shyamd]

http://materials-consortia.github.io/optimade-python-tools goes to a 404 under github pages so I think should work. I can't test the deploy until this is merged in as mkdocs gh-deploy uses the current remote to find the gh-pages branch. That being said, the docs will still work. Just the link back to the docs won't initially.

[ml-evs]

Thanks @shyamd, lets see if this works :)