[r0ckarong]

I just wish people would start building this kind of stuff around Asciidoc and not Markdown. Markdown works fine for notes and short how-to's but once you move into longer manuals that need more structure elements you quickly run out of options.

[rychco]

I agree, but unfortunately Asciidoc’s adoption is limited (imo) by the fact that the two most supported parsers are written in Ruby & JavaScript. Not having a C library really limits its potential reach. I personally tried it and enjoyed it, but Ruby/Javascript don’t fit into my projects or preferred tools.

[sshine]

Markdown vs. AsciiDoc: I find that mdBook is sufficient for my needs.

Where Markdown comes short for me is presentation layout. The only worthy contender of LaTeX so far is Typst. I’ve made my resume and my slides with Typst, and it’s amazing.

I really like SciPress, and I think a web-based VSCode with the right plugins and a presentation layer holds a LOT of potential.

[EligibleDecoy]

I really agree. All of our team documentation is in asciidoc. Importing diagrams from other files, variables, and vastly better tables are the best features for us. I feel like asciidoc’s weakness is that there is only 1 library, and it’s in ruby. Whereas markdown has libraries in almost all languages, making it easier to support.

[neb519]

I honestly hadn't heard of Asciidoc until I read this. Looks interesting.

Note that Scipress Markdown supports "directives" which in turn means I can include all types of elements like popovers, blur screens, paywalls, etc.