I've started adding sphix docs. You can build the documentation with:

cd docs
pip install -r requirements.txt
make clean html

There's still a bunch of work to do, including porting over much of the existing documentation, but if you want to get started on documenting the C torch.xxx functions they're listed in torch/docs.py.

We're using Google style Python docstrings because they tend to be nicer to read then pure reStructuredText:

http://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html

Also worth reading is the Python docstring convention:

https://www.python.org/dev/peps/pep-0257/

• For C-implemented functions put the type signature as the first line. (Don't do this for python implemented functions)
• Use triple quotes

Last, a tidbits from Documenting Python:

7.2.5. Economy of Expression
More documentation is not necessarily better documentation. Err on the side of being succinct.
It is an unfortunate fact that making documentation longer can be an impediment to understanding and can result in even more ways to misread or misinterpret the text. Long descriptions full of corner cases and caveats can create the impression that a function is more complex or harder to use than it actually is.