Sweet. I can use Asciidoc in my long forms?
Discussion
No, but some of the long-form clients will implement 30040/30041. Then you can choose Markdown or Asciidoc, by selecting which type of event to publish.
Expect everyone to eventually move to Asciidoc, though, since it covers the simpler Markdown and anything more complex is difficult in Markdown. As you know, can't even resize images or make a decent table or ordered list.
We're going to be publishing eBooks, eMagazines, and academic journals, so we couldn't stick to Markdown. And Asciidoc has the plugins for ePUB, Asciimath, PlantUML, and LaTeX generation, and etc. Very smooth from one format to another, and you can use style sheets, so that you have a universal branding of the documents.
We're working on the #Alexandria client parser, at the moment, which is a Nostr-focused extension of the Asciidoc parser.
Excellent! The future is bright, the future is purple.
You can see some Asciidoc examples, here, and see how Markdown and Asciidoc compare (look very similar, most people won't notice a difference).
And here, you can see the current parser code for the Asciidoctor extension from nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn
Based upon:
The Asciidoctor website is written in Asciidoc, so it's also a nice example of how pretty you can make your notes.
Holy shit, gitwogitworkshop.devis lit!
I knooooooooooooow. 😅
That's why I moved from the nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl npub to only using this one, since it's the one I use for GitWorkshop and I spend so much time on there, now.
Just reading through this now: