New issue
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
Setup documentation framework #5
Comments
Sphinx seems a bit dated and somehow feels heavy, so I wanted to try a fresher alternative. I attempted MkDocs and here's what I found:
In the end, I can get nice docs with MkDocs, but I'd have to either hand-format all my API entries (e.g., function signatures), which is basically the "plain Markdown" option, or I'd have to hack on some of the auto-api solutions to get them working. Searching the web for "mkdocs vs sphinx" also turned up this issue, which has some additional thoughts So it looks like I'll stick with Sphinx. On the plus side, there's a Material theme for Sphinx and some nice options for editing with Markdown instead of ReST (see the first comment in the linked issue), and Sphinx is being actively developed, so not only is it more mature but it'll probably keep improving. |
While I haven't tried it yet, the Material theme may have issues being deployed on ReadTheDocs. There's also pradyunsg's new furo theme which also looks pretty good. |
Sphinx is now building with a GitHub action and deploying to https://goodmami.github.io/wn, so I think this can be closed, although at some point I may want to host at ReadTheDocs. |
I'm undecided if we should use Sphinx, MkDocs, or even plain Markdown rendered by GitHub (example).
The text was updated successfully, but these errors were encountered: