There are a number of elements supported by AsciiDoc that aren't available in Markdown[0].

For most writing, Markdown is perfectly sufficient. If you're doing complex stuff, however, AsciiDoc might make expressing your intent more straightforward.

[0]: https://docs.asciidoctor.org/asciidoc/latest/asciidoc-vs-mar...

Thanks, this article does not do a great job of highlighting Asciidoc’s USPs

> I don't see anything that Asciidoc would do better than Markdown.

If you don’t see anything, it must be because you have closed your eyes. Asciidoc does a ton of things that Markdown can not.

Complex tables. Admonitions. Generated ToCs. Definition lists. Block image with alt text. Inclusions. Block titles. In-line anchors. Conditional directives. Live code inclusion.

Just all the stuff that’s required to write complete, professional documentation instead of blog posts and readme notes.

I didn’t remember any of that from the article so I went back and checked. Seems that although you’re absolutely right, the article doesn’t give any details whatsoever other than obliquely hinting at it somewhere towards the bottom of the article.

Thanks for the comment, it actually seems quite a bit more interesting now.