Add Sphinx autodoc and intersphinx about yellowbrick

[bbengfort]

I think the documentation will be extremely important, especially since it will have to contain images, example code, and a lot of details about how to work with Yellowbrick. We're taking a lot of inspiration from Seaborn; it and the pandas documentation reveal how important it is to visually and intuitively explain how to use the library. If Sphinx will help us achieve that level of documentation (after all, both Pandas and Seaborn use Sphinx) then I'm all for it.

[bbengfort]

Planning on moving all the documentation over to reStructuredText and Sphinx?

[lauralorenz]

Yes

Sent from my iPhone

On Jun 25, 2016, at 4:41 PM, Benjamin Bengfort [email protected] wrote:

Planning on moving all the documentation over to reStructuredText and Sphinx?

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

[lauralorenz]

I actually assumed yall were already using sphinx; now that I'm in it I see you're actually using mkdocs which we can stick with if yall like, though I don't see anything like sphinx autodoc for autogenerated api documentation on the mkdocs guide/documentation so I personally am pro sphinx in this case

[lauralorenz]

I would consider the scope of this one closed by #35 and the scope of implementing it more widely to be represented by open issue #36. Reopen if you think otherwise