Closed jcassady closed 4 months ago
I think pdoc (https://pdoc3.github.io/pdoc/) could also be a solution for this.
Pdoc generates html directly of all docstrings and follows module hierarchy. Don't know if it also works with GitHub Actions Workflow, no experience with that (yet).
Hi @nickterhaar, I'll take a look at pdoc. However, I just merged @gdevakumar's PR adding phinx documentation support: https://github.com/jcassady/llava-benchmark/pull/10
It looks like adding a github workflow to generate the html on pushes to the main
branch is easy, so I'll get that setup soon.
I added .github/workflows/docs.yml
to generate the html from the .rst
files that Sphinx creates, then deploy to GitHub Pages:
@gdevakumar Would you be able to share the steps you used to create the .rst
files with phinx? I had an issue generating the index.rst
file when I gave this a go.
@jcassady , these are the steps i followed:
pip install sphinx sphinx-rtd-theme
mkdir docs
cd docs
sphinx-quickstart
and proceed with defaultsdocs/conf.py
, docs/index.rst
files as shown in the commitsphinx-apidoc -o . ..
make html
This will generate all the relevant docs!
Thanks for sharing @gdevakumar!
Description: The goal of this issue is to leverage docstring comments in the source code to automatically generate HTML documentation pages for GitHub Pages. By doing so, we can provide clear and accessible documentation for users and contributors.
Proposed Solution:
Docstring Parsing: We need a tool that can extract docstrings from the Python source code. One option is to use the
sphinx-markdown-builder
Python module, which integrates with Sphinx to generate Markdown documentation from docstrings. This will allow us to create Markdown files that can be easily converted to HTML.GitHub Actions Workflow:
main
branch or when new commits are made.Additional Resources: