I wish Asciidoc was more popular
1–10 of 124 posts
Re: I wish Asciidoc was more popular
#2I love Asciidoc, especially with PlantUML. I have used them together on various projects to version, and host internal documentation. The code block snippet generator is super useful as well. Spring Framework documentation is a shining example of how useful it can be!
Re: I wish Asciidoc was more popular
#3Well, here comes the obligatory org-mode comment:
Org mode does most of that, too. And a lot more. And while you cannot use it in Github issues, you can in README files on Github.
Re: I wish Asciidoc was more popular
#4Very briefly on admonitions: there is nothing stopping you from adding them to markdown yourself:
You _really_ shouldn’t
play with matches, Debbie.
warning {
display: block;
color: red;
}
Relying on asciidoc for styling elements like admonitions always felt like the wrong tool for the job. Like writing a Java generator in Perl, instead of just writing actual Java.
Re: I wish Asciidoc was more popular
#5I write all my professional docs in AsciiDoc (even made a tool to pull AsciiDoc comments out of the code and into various documents), but always disliked having to pull ruby into my toolchain.
Is the Python3 asciidoc (any of the several that have sprung up) good enough to replace asciidoctor nowadays?
Re: I wish Asciidoc was more popular
#6I write all my professional docs in AsciiDoc (even made a tool to pull AsciiDoc comments out of the code and into various documents), but always disliked having to pull ruby into my toolchain. Is the Python3 asciidoc (any of the several that have sprung up) good enough to replace asciidoctor nowadays?
Use AsciiDoctorJ. Under the hood it's JRuby, but as a user you won't really notice, it's just a Java program.
Re: I wish Asciidoc was more popular
#7Well, here comes the obligatory org-mode comment: Org mode does most of that, too. And a lot more. And while you cannot use it in Github issues, you can in README files on Github.
I don't use emacs, so an emacs mode isn't that useful for me.
Re: I wish Asciidoc was more popular
#8I write all my professional docs in AsciiDoc (even made a tool to pull AsciiDoc comments out of the code and into various documents), but always disliked having to pull ruby into my toolchain. Is the Python3 asciidoc (any of the several that have sprung up) good enough to replace asciidoctor nowadays?
Use AsciiDoctorJ. Under the hood it's JRuby, but as a user you won't really notice, it's just a Java program.
Having to download a JRE is not any better than having to pull Ruby from the RH Software Collections, meanwhile Python is already there...
Re: I wish Asciidoc was more popular
#9Well, here comes the obligatory org-mode comment: Org mode does most of that, too. And a lot more. And while you cannot use it in Github issues, you can in README files on Github.
I don't use emacs, so an emacs mode isn't that useful for me.
Org-mode stuff can be authored outside emacs. There's even a Visual Studio Code addon for it. And pandoc groks it.
But yeah, to unlock the true power of org-mode you need emacs.
Re: I wish Asciidoc was more popular
#10Well, here comes the obligatory org-mode comment: Org mode does most of that, too. And a lot more. And while you cannot use it in Github issues, you can in README files on Github.
I don't use emacs, so an emacs mode isn't that useful for me.
Org is also just a file format with extensions available in VS Code, vim, sublime, and Atom. I've personally used the VS Code extension, I think it works just as well as the Markdown extension.