We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be preferable for documentation to be built with Sphinx or MkDocs and published to a dedicated docs site.
Current documentation consists of:
It's all there, but it would be better prestented and easier to navigate if it were on a dedicated docs site.
It hopefully wouldn't be a huge task; the docs files are all .md and the docstrings are (aka 'should be') in numpy format.
Which one, Sphinx or MkDocs? Sphinx is probably more flexible, although would likely involve more work.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It would be preferable for documentation to be built with Sphinx or MkDocs and published to a dedicated docs site.
Current documentation consists of:
It's all there, but it would be better prestented and easier to navigate if it were on a dedicated docs site.
It hopefully wouldn't be a huge task; the docs files are all .md and the docstrings are (aka 'should be') in numpy format.
Which one, Sphinx or MkDocs? Sphinx is probably more flexible, although would likely involve more work.
The text was updated successfully, but these errors were encountered: