Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

ODM2 Sphinx doc system and docstring conventions documentation #1

Open
emiliom opened this issue Jan 30, 2018 · 2 comments
Open

ODM2 Sphinx doc system and docstring conventions documentation #1

emiliom opened this issue Jan 30, 2018 · 2 comments

Comments

@emiliom
Copy link
Member

emiliom commented Jan 30, 2018

I assume that this "meta" repo is just like any other, and can have issues. So, given that it's intended as a repo that provides common information across the ODM2 software ecosystem, I think this is a good place (for now anyway) to craft and eventually store documentation about the conventions and systems we've put in place for code docstrings and to generate Sphinx documentation (both automatic API docs as well as complementary Sphinx pages).

Because that system was first developed for odm2api, currently the documentation we've compiled is found as issues in that repo:

Unless there are objections, I'll eventually migrate that content into a mix of issues and a markdown document on this meta repo.

@emiliom
Copy link
Member Author

emiliom commented Oct 9, 2018

Note to self: add instructions on how to install and run sphinx locally, to be able to test new documentation edits. I'll copy the detailed documentation from the internal NANOOS DMAC sphinx docs.

@emiliom
Copy link
Member Author

emiliom commented Jan 28, 2019

@emiliom emiliom changed the title Test - issue for ODM2 Sphinx doc system and docstring conventions documentation ODM2 Sphinx doc system and docstring conventions documentation Jan 29, 2019
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

No branches or pull requests

1 participant