Also, there's the one Wikistr and Njump use. I've tested it against my docs and it works quite well.

https://github.com/fiatjaf/svelte-asciidoc

You can see what our Nostr-Markup covers, in the input field, here, and in the code base. I can put it in a wiki page and add it to our project 30040.

That's the parser we use on anything that isn't Asciidoc, like kind 1111 or 30023, and we use part of it on Asciidoc. Let me go write that up, as it sounds sort of confusing.

https://next-alexandria.gitcitadel.eu/contact

Reply to this note

Please Login to reply.

Discussion

We use shamelessly use straight Asciidoctor on Alexandria. 😂

It's very powerful, especially, once you get into publishing complex documents and stuff.

It has zero Nostr native stuff tho.

And asciidoc has a buuuuunch stuff that contracdicts / overlaps with things we have by default on Nostr.

things that existed long before nostr.

there's a lot of inertia in that

We have a basicMarkupParser that runs first and includes the Nostr-y stuff, and that can run before Asciidoc _or_ advancedMarkupParser.

Always two steps. Second step ignores the parts that are already parsed.

Tx