Closed moshi4 closed 2 years ago
I think this comment is fundamental!
Thank you for your advice, and I'm sorry for my late response. I'm so busy now, but I will try to resolve this issue as soon as possible.
There is no particular need to rush, so you are free to deal with this issue at your own pace. I created PR (#17) myself to resolve this issue, so please check it out when you have time.
Hi, ponnhide
Currently, the API documentation is in the README, and its content is roughly the same as the docstring (by @DanNBullock work #8). However, the API documentation in the README is difficult for users to reference, and it seems generally not a good practice to manually write the specifications separately in both the API documentation and the docstring. To solve this problem, how about automatically generating an HTML-format API document from the docstring and hosting it on GitHub Pages?
Using pdoc3, you can easily generate HTML-format API documentation from docstrings in your code.
After the automatic generation of HTML API docs, you can publish them to your users by simply placing the generated docs in a directory in your repository where GitHub Pages is enabled.
You can also configure GitHub Actions to automatically update the API docs after a Push/Pull-Request to GitHub, if you are interested in trying this. If needed, I can provide an automated API docs generation workflow with GitHub Actions that I use.
The following article may be helpful (in Japanese).
Best Regards,