Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Generate Docs #6

Open
aayush26 opened this issue Oct 1, 2017 · 9 comments
Open

Generate Docs #6

aayush26 opened this issue Oct 1, 2017 · 9 comments

Comments

@aayush26
Copy link
Owner

aayush26 commented Oct 1, 2017

Generate Docs with examples

@joserc87
Copy link
Collaborator

joserc87 commented Oct 1, 2017

One awesome (but sometimes painful) way of creating documentation in python is with sphinx. The cool thing about it is that it can be hosted in https://readthedocs.org/, so it will look like this: http://docs.readthedocs.io/en/latest/getting_started.html. readthedocs works like travis, so the server will build the documentation every time we push to github.

Maybe we can wait until there is actually something to document, but I leave this here for the future

@aayush26
Copy link
Owner Author

aayush26 commented Oct 1, 2017

@joserc87 Cool. Great idea. Lets push some more codes and release a production ready version 1. Then we will look into it.

@aayush26
Copy link
Owner Author

aayush26 commented Nov 5, 2017

PR: #28

@aayush26 aayush26 self-assigned this Nov 5, 2017
@aayush26
Copy link
Owner Author

aayush26 commented Nov 5, 2017

Barebones done.
working url for documentation: http://pirant.readthedocs.io

@deepbrook
Copy link
Contributor

I have added docstrings in my PR #29 - you could auto-generate the API reference with autodocs, if you guys are using sphinx ?

@aayush26
Copy link
Owner Author

aayush26 commented Nov 22, 2017

@nlsdfnbch Thanks for adding docstrings. We are using sphinx and hosting it at readthedoc, though its in very initial stage with almost no documentation.
All setup has been done. Your PR seems to add good amount of docstring. I am looking into it.

I am looking for someone who likes and writes good documentation ( I really wonder if I can find one though considering everyone hate documenting and I am very poor in it.) Including Getting started and code examples.
Most probably, I will end up doing it. Haha..

@deepbrook
Copy link
Contributor

@aayush26 , luckily you'll only need to document the public methods properly (with examples and such). The private methods and objects don't need that sort of documentation - usually a brief explanation of params and their expected type is sufficient.

Since you guys are using sphinx then, you should be able to build the documentation (from the docstrings)
doing this:

.. automodule:pirant
    :members:

.. automodule:pirant.apps
    :members:
etc

That would allow you to write the documentation directly in the source code as well, sparing you the need to maintain two documentations.

@radhikasundararaman24
Copy link

Hello: I'd like to help the community with some doc help. WHat are you looking for at this point?

@aayush26
Copy link
Owner Author

@radhikasundararaman24 Sure. You can look the existing docstrings and check if they are generating docs correctly. If no, you can add automodule:* as mentioned above to create docs.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

4 participants