One of the developers of the neovim project provided really useful (and mostly accurate) feedback about why he prefers Sphinx over Asciidoctor.
I think this feedback can help us understand where we can focus to make Asciidoctor an even better publishing toolchain and hopefully win out over Sphinx in the long run.
Asciidoctor didn't start out as a replacement for Sphinx, but since we've covered so much ground over the last 2 years, it's interesting that it's now being compared to it. I believe Asciidoctor needs to be combined with a static site generator (or other build tool) (middleman, Awestruct, jBake, Gradle, etc) to cover all the requirements. It would simply be out of scope for Asciidoctor core to try to be one itself. However, there's nothing stopping us from composing tools...and arguably it puts Asciidoctor in a better place because it doesn't run the risk of being monolithic.
Locked
