Open thatvideoshopguy opened 1 year ago
As an alternative, would it be better and/or preferred to move to a documentation tool that better supports markdown?
Reasoning:
Suggestion:
If you did want to move I would suggest moving to mkdocs + mkdocs-material + mkdocstrings for generating docs and mike for managing them on GitHub Pages.
Here's a sample from one of my own projects and the mkdocs.yml
that generated it (may wish to poke through /docs
and /scripts
as well).
Helping out:
If you decide you prefer this direction let me know - I'm happy to help.
I've thrown together a branch for parsedmarc
+ mkdocs
.
Deployed version available at: https://nhairs.github.io/parsedmarc/latest/
Let me know if you'd like me to finish this off and turn it into a PR (probably a decision for @seanthegeek)
I noticed that the documentation was converted from reStructuredText (RST) to Markdown (MD) with this commit by @seanthegeek. I would like to discuss the reasons for this change and propose converting the documentation back to RST.
RST offers several advantages over MD in the context of large-scale documentation within Sphinx:
myst-parser
), which are powerful ways to add semantic markup and custom functionality.myst-parser
.Please share your thoughts on the initial conversion and whether there are specific reasons for using MD over RST.
Thank you for considering this suggestion and I would be happy to get involved in this conversion, if it goes ahead.