You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've spent the last few days looking for a documentation system to pull docstrings, convert them and emit markdown. I need a relatively rich input format and RST or Scriba look like they'll do the trick. I've got some legacy Scriba to work with too, and don't fancy converting it. Generally I like the concept of CommonDoc and I think good documentation needs to be a combination of hand-crafted and generated.
With this issue I'd like to explore what the best way to add a markdown package to emit docs/sections as markdown. In theory this should be simpler than the current HTML, since there's no formatting directives or style that need to be handled. The use case is to emit MD to be further processed by a documentation system generator, in this case Hugo. There are many styles ('themes') available, and this way I don't have to concern myself with styling and deployment.
How would one of you experienced with CommonDoc approach this? Initially I thought of:
Cloning the HTML emitter code paths however, to my eye, they're a bit convoluted and involve many systems and dependencies.
Walk the doc tree and use a generic template system like cl-template or html-template to emit the markdown. Despite the name, html-template is actually agnostic to the output format.
Maybe just walk the tree and manually emit?
I think any of these would work; the sticking point at the moment is the conversion of the docstring text from scriba to markdown, which I think happens in a combination of common-html and pandocl.
Any ideas?
The text was updated successfully, but these errors were encountered:
I've spent the last few days looking for a documentation system to pull docstrings, convert them and emit markdown. I need a relatively rich input format and RST or Scriba look like they'll do the trick. I've got some legacy Scriba to work with too, and don't fancy converting it. Generally I like the concept of CommonDoc and I think good documentation needs to be a combination of hand-crafted and generated.
With this issue I'd like to explore what the best way to add a markdown package to emit docs/sections as markdown. In theory this should be simpler than the current HTML, since there's no formatting directives or style that need to be handled. The use case is to emit MD to be further processed by a documentation system generator, in this case Hugo. There are many styles ('themes') available, and this way I don't have to concern myself with styling and deployment.
How would one of you experienced with CommonDoc approach this? Initially I thought of:
I think any of these would work; the sticking point at the moment is the conversion of the docstring text from scriba to markdown, which I think happens in a combination of common-html and pandocl.
Any ideas?
The text was updated successfully, but these errors were encountered: