+1 for ASCIIDoc. Now that I use ASCIIDoc, I cannot go back to Markdown. It’s just to limiting for anything moderate to serious documentation.
Yes, please!
+1 for asciidoc as a default option to use as well
I did some cleanup on the forum and moved/reorganized some threads.
July 2025 Notice: support for ASCIIDoc in Obsidian Core is not on the roadmap.
Here are some community plugins about ASCIIDoc (please, comment about the plugin in their respective thread):
3 Likes
+1 for asciidoc support! atleast initially being able to open .adoc files as read-only (rendered) would be great!
+1 For asciidoc !
+1 for adoc
+1 for Asciidoc support.
+1 for Asciidoc support.
1 Like
+1 for native Asciidoc support
I would prefer typst, but to each their own 
Could be interesting to explore but it looks to be an asciidoc fork with a little less functionality and closed source support stuff throw in. Personally I like the large scope and open nature of asciidoc for future proofing my note taking application, but as you say, to each their own.
typst is open source, only their web interface is closed. the engine is open and can run locally. It is not a fork of ASCIIDOC, even if some syntax is based on ASCIIDOC. Typst is meant to replace LaTeX, and currently does not work for HTML export (sadly).
for what obsidian does, asciidoc is definitely better (and a much needed upgrade compared to md), but I like pagination, so typst is nicer for that
1 Like
There is a thread for typst, please continue there for it.