AsciiDoc (the format) is currently being developed in an Eclipse Foundation working group (https://projects.eclipse.org/working-group/asciidoc https://projects.

AsciiDoc (the format) is currently being developed in an Eclipse Foundation working group (https://projects.eclipse.org/working-group/asciidoc https://projects.eclipse.org/working-group/asciidoc). This working group includes leads from both the Asciidoctor/Ruby and Asciidoc/Python projects. (I'm lurking on the mailing lists but not really part of this effort.) It seems like the goal is to shore up the AsciiDoc standard and prevent further divergence between Python AsciiDoc tools and AsciiDoctor. IMO AsciiDoc's advantage over Markdown, RST, LaTeX and others is its adoption of DocBook XML as an industrial-strength backing format. The combination of a pragmatic markup language and a proven, stable, and relatively media-independent translation target is unique and extremely useful. I'm an enthusiastic believer in Asciidoc-the-language, but the tooling situation is confusing in parts, fragmented in others, and not really living up to its premises. This is exactly why I'm watching the asciidoc-wg project with great interest. My personal wish is for a modern and first-class replacement for the various AsciiDoc-to-PDF flows. I'd bet on CSS Paged Media, although it's been a long haul. The current options (FO/XSLT, dblatex, and asciidoctor-pdf) all have pretty severe limitations. If any of the AsciiDoc/AsciiDoctor devs are reading this, thank you 1,000,000 times for your efforts. It's an extremely complex project and I am grateful there's a community of talented people working on it.