Already love #Asciidoc. It's a publishing game-changer.
Sorry, not sorry.
Discussion
The Nostr implementation of it is still a bit buggy, but it works well enough, that I decided to just move everything over and beta test it for nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 .
It'll all look more polished, soon. Excuse the construction site, please. 🏗️🚧
Thank you for finding the bugs.
Isn't markdown more standard and what Nostr already uses?
Yes, for normal articles (30023/24). And all long-form accept the simplest markdown, like headers and bullet lists and etc. But wikis (30818) and modular articles (30040/41) will also support Asciidoc.
Asciidoc allows us to do real publishing, and to include things like custom tables, img resizing, UML (including PlantUML), Latex, AsciiMath, stylesheets for magazine or website publishing, scientific journals, etc.
We need to patch or make a new NIP for long-form-posts with Asciidoc support. Seems superior to Markdown overall.
That already exists, with kind 30041.
30041 only functions as a modular article, if you link it to a 30040 index. Otherwise, it's just an Asciidoc article.
Interesting.. So how does this work in practice? You create a kind 30040 header event and add kind 30041 article/section events in the e tags of the header event?
Yes, you can list "e" tags for any event kind, including 30041s.
You can also list Kind 01, Wiki pages, articles, other 30040s (creating a hierarchy), etc.
What's superior about it?
note1qmuw8fh0dte04zz3ptlcnec033tl2ufpjl0effmyrvw33r2k4htq6znqgc
Allright I browsed that site a bit and got convinced as well. Especially by this: https://docs.asciidoctor.org/asciidoc/latest/stem/ ❤️