asciidoctor-skins

I recently switched from Markdown to AsciiDoc. It is much better in my opinion. The syntax is similar enough to MD that just having the adoc cheatsheet bookmarked is enough to switch. But it's more structured, much more fully featured, just two big implementations (AsciiDoc and AsciiDoctor) which are largely compatible. There's only one way to mark the language of a code block, only one way to make lists, only one way to make footnotes, etc. Also it actually has first-class support for things like footnotes and admonitions[0] etc. It is a syntactic sugar layer on the DocBook XML format which is apparently used to make actual books. But AsciiDoctor compiles it to everything from DocBook XML to HTML to Markdown to ePub to PDF. Another thing I like is that AsciiDoctor actually comes with a good default stylesheet. If you just turn MD into HT

Eh, I'd say they're pretty different goals and use cases in reality. Pandoc is great for translation into other formats, where the other format then is applied final styling using downstream tools. AsciiDoctor is for the Asciidoc format, but, generally includes some nice tooling for commonly used output formats. Yes, you can use pandoc to convert asciidoc to something else, but in general, I've noticed that asciidoctor has great support for HTML themes: https://asciidoctor.org/docs/produce-custom-themes-using-asc... https://github.com/darshandsoni/asciidoctor-skins The PDF styling directly out of the asciidoctor tool, on the other hand, isn't as advanced. So going from asciidoc to DocBook can make sense here, and I think is probably still done to do things like create truly professional looking PDFs. What to use? Depends on your toolchain