Open gordonwatts opened 4 years ago
One great example of documentation that I like to refer back to is numba. Observe that it's organized into sections for users and developers. The user section consists of two parts:
As for notebooks, I think they should supplement documentation, but not replace it. Numba uses a dedicated page for tutorials, but we could also consider writing a documentation page for each topic (e.g. complex func_adl usage) and then linking a notebook at the end with examples. Alternately, there is a fancy tool called nbsphinx which enables Sphinx to take a notebook and generate documentation from it.
@AndrewEckart - this is the tool we've been thinking of using for this: https://jupyterbook.org/intro.html
As a user I want a place to go to learn a lot about ServiceX and using it
Approach
Tools
Target Audience
What should the book contain
qastle
direct usageqastle
(to get theqastle
string back)Possible Future Topics
These would become new issues that we could write up later on.
To Do