With a conda package now available, it seems like a good next step would be to create some minimal Sphinx documentation, mainly to document the REST API's -- which ones are available, their usage, etc.
I realize there's a test endpoint somewhere, and its swagger interface provides good documentation. But relying on a test endpoint for general documentation may be a little frail? Would be cool if you could leverage some of that swagger stuff to "export" static HTML or markdown/ReST that could be incorporated into the Sphinx docs ...
Anyway, not saying this is a high priority. Just creating this issue while the thought is in my head. We can discuss at the next BiGCZ/ODM2 call.
With a conda package now available, it seems like a good next step would be to create some minimal Sphinx documentation, mainly to document the REST API's -- which ones are available, their usage, etc.
I realize there's a test endpoint somewhere, and its swagger interface provides good documentation. But relying on a test endpoint for general documentation may be a little frail? Would be cool if you could leverage some of that swagger stuff to "export" static HTML or markdown/ReST that could be incorporated into the Sphinx docs ...
Anyway, not saying this is a high priority. Just creating this issue while the thought is in my head. We can discuss at the next BiGCZ/ODM2 call.