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
Instead of focusing on DocBook vs CommonMark, I think it would be good to instead introduce a --format param or something similar that allows outputing to a chosen format. This would allow nixdoc to be more versatile and flexible for future formats.
IMO, it would be good to generate something that other, fantastic, documentation generators might be able to use. doxygen, rustdoc, javadoc, sphinx etc. all generate documentation that is searchable, has links back to the source, have syntax highlighting, etc.
Being able to output a format that they (or another tool) might understand would probably significantly decrease the effort needed to recreate output similar to theirs.
The text was updated successfully, but these errors were encountered:
Instead of focusing on DocBook vs CommonMark, I think it would be good to instead introduce a
--format
param or something similar that allows outputing to a chosen format. This would allownixdoc
to be more versatile and flexible for future formats.IMO, it would be good to generate something that other, fantastic, documentation generators might be able to use.
doxygen
,rustdoc
,javadoc
,sphinx
etc. all generate documentation that is searchable, has links back to the source, have syntax highlighting, etc.Being able to output a format that they (or another tool) might understand would probably significantly decrease the effort needed to recreate output similar to theirs.
The text was updated successfully, but these errors were encountered: