-
Notifications
You must be signed in to change notification settings - Fork 589
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
Asciidoc Support #73
Comments
What do you mean by “arbitrary extensions”? |
There are several complicating factors to consider..
|
One thing you could do is convert the ADR Markdown to Asciidoc with Pandoc and feed it into your Asciidoc-based publishing pipeline. |
@mikeholler did you finally make adaptations to support asciidoc? |
Hey @stephlag, my coworkers and I decided that it's not a bit deal if we maintain ADRs in markdown and our other architectural docs in asciidoc, since they're all converted to HTML for viewing. I think support for different formats would still be a good goal for this project, but I don't have enough stake in the game to help make it happen. |
One major advantage of asciidoc is the possibility to include embedded diagrams via plantuml for example. Markdown > Pandoc > Asciidoctor is of no help in that case. |
Implements issue npryce#73
Hey all, I've made a PR to allow using AsciiDoc instead of Markdown (#101). Unfortunately, the CI fails on MacOS due to a weird I've taken the option to have the language specified at ADR log initialisation. Can you tell me what you think about it? |
Hi there,
I love this project and want to use it internally. We like to use adoc (asciidoctor) and judging from some time I spent reading the source code it seems pretty simple to support an alternative format. Would you be interested in accepting a PR that adds support for arbitrary extensions, so we (and others) can use the markup language we feel comfortable with?
The text was updated successfully, but these errors were encountered: