Skip to content

Added tools for automated documentation with Sphinx and Numpydoc#88

Merged
tylertreat merged 2 commits intotylertreat:masterfrom
nickstanisha:master
Apr 10, 2016
Merged

Added tools for automated documentation with Sphinx and Numpydoc#88
tylertreat merged 2 commits intotylertreat:masterfrom
nickstanisha:master

Conversation

@nickstanisha
Copy link
Contributor

I've added a docs directory containing the necessary scripts and tools to make some simple automated documentation using Sphinx. I've also changed the docstrings to use the Numpy style so that the automated documentation can be presented in the nice format provided by Numpydoc. In addition to the nice formatting, Sphinx also provides tools for searching and browsing the documenation.

Moving forward, you could decide to follow these directions and host your documentation on Github directly, which I've done here: https://nickstanisha.github.io/BigQuery-Python/ by creating a gh-pages branch of my fork.

The content of the documentation stayed the same, the only change was the formatting. Additionally, no code was changed so all tests are still passing.

Using numpydoc allows aesthetically pleasing and easy to read documents to be created using Sphinx. You can see real examples of this with Numpy's own documentation (https://docs.scipy.org/doc/numpy-1.10.0/reference/generated/numpy.mean.html). This docs directory contains the basic file structure necessary for creating automated documentation based off NumPy styled Docstrings.
@tylertreat
Copy link
Owner

Thanks! I will try to get the docs hosted soon.

@tylertreat tylertreat merged commit 65896b3 into tylertreat:master Apr 10, 2016
@nickstanisha
Copy link
Contributor Author

No problem! Thanks for the merge!

@tylertreat
Copy link
Owner

@nickstanisha I pushed the docs to the gh-pages branch. Any idea why some files are 404'ing despite being in the branch? http://tylertreat.github.io/BigQuery-Python/

@nickstanisha
Copy link
Contributor Author

@tylertreat I don't see any 404-ing casually browsing through the docs. Try adding a blank .nojekyll file at the top directory of your branch to prevent GitHub pages from processing the HTML with Jekyll. That should make everything behave like you'd expect.

@tylertreat
Copy link
Owner

That did the trick, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants