I really like AsciiDoc and would encourage anyone to give it a try, especially for things like software documentation (in all forms). I very much despise the trend to write sharepoint or wiki/Confluence pages as a means for software documentation. I want my documentation to reside next to my source code, not at some obscure corporate URL. The problem is simply that github, gitlab, and friends adopted Markdown and so…
Compare AsciiDoc and Markdown
11–20 of 137 posts
Re: Compare AsciiDoc and Markdown
#12Earlier quoted context omitted.
Github already supports Restructured Text (reST) in READMEs, and some other markdown flavours. Do not know about AsciiDoc but looks interesting.
As can be seen here, GitHub renders Asciidoc just fine: https://github.com/asciidoctor/asciidoctor.js
Re: Compare AsciiDoc and Markdown
#13But it's less supported, so I stopped using it.
Re: Compare AsciiDoc and Markdown
#14We use Dropbox Paper for team documents(not source code documentation). I actually like it. The thing that makes MarkDown documents less appealing is the inability to handle images seamlesslessly(drag and drop). Most of the time, our documents involve images to explain stuff. Uploading them somewhere, and then manually adding a tag and correctly copy/paste the url in MD makes it less appealing that just drag & drop a…
Re: Compare AsciiDoc and Markdown
#15We use Dropbox Paper for team documents(not source code documentation). I actually like it. The thing that makes MarkDown documents less appealing is the inability to handle images seamlesslessly(drag and drop). Most of the time, our documents involve images to explain stuff. Uploading them somewhere, and then manually adding a tag and correctly copy/paste the url in MD makes it less appealing that just drag & drop a…
Have a look at Typora [0]. It's my main Markdown editor for this reason (and others).
Re: Compare AsciiDoc and Markdown
#16It sounds so archaic.
Re: Compare AsciiDoc and Markdown
#17The point of Markdown is having a very tiny set of features: headers, paragraphs, lists, links, pre-formatted text, etc. You can learn this in minutes. Having Markdown with more features is against what makes Markdown useful: minimalism.
I disagree... Markdown is no longer a single unified version. There are multiple implementation, extensions, etc. The original Markdown spec by itself isn't that useful and there is a reason so many extensions have been made for it. It can maintain simplicity while still adding new features. Pandoc has some great examples of Markdown extensions that are really useful.
Re: Compare AsciiDoc and Markdown
#18Re: Compare AsciiDoc and Markdown
#19The point of Markdown is having a very tiny set of features: headers, paragraphs, lists, links, pre-formatted text, etc. You can learn this in minutes. Having Markdown with more features is against what makes Markdown useful: minimalism.
Re: Compare AsciiDoc and Markdown
#20The funny thing is that on their page markdown has better syntax highlighting than their own markup language
This must be contributing a lot to the adoption difficulty (at least for resource-limited open-source projects). There's a good chance you will not find an AsciiDoc parser library for your favourite programming language.