#nosciidoc seems to be the best fit for most long form text:
:mail: Mail
:note: Notes (as in actual note taking)
:wiki: Wikis
:article: Articles (kind 30040)
:book: Books
Etc...
So I need help in defining it.
ā as I'm working on a WYSIWG editor for it
nostr:npub1uvhwdxy980y0ufdprjz3j5j3wd2wpl3v5lf36r68fq895xs7ptvsscpjgx do you guys have a spec already with the parts of AsciiDoc you ignore and the parts of Nostr you add?
Do you have an AsciiDoc package? It will be huge for everyone.
There's nothing for Flutter.
So I have my own yes.
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.
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.
Tx
And even the web asciidoc stuff is really bad rn. Only Alexandria has somewhat proper rendering.
State of MarkDown Nostr is barely better btw.
No WYSIWYG editor that integrates even one Nostr-native thing.
They all copy, paste andstop there.
Same for short text in fact.
I just hacked TextField for notes, but AsciiDoc was a too much for me when I was exploring the Curated Publications NIP. Iād definitely use your package for AsciiDoc if you publish it.
before an editor you need a parser
would be good if it was a cross-platform rust library
I have parser + renderer.
Still adapting both regularly, so I want to settle on a clear spec now.
Editor doesn't need the parser technically btw. You could translate your different segments to desired output on publish.
where is the code?
nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn
We observe all of the existing AsciiDoc syntax, currently, which is easy since we use the asciidoctor.js parser.
The one addition we have, so far, is [[double brackets]] for d-tag-based hyperlinks. We'll be writing asciidoctor extension modules to support that, and we may add additional syntax over time, if needed.
I love the logo!
We seem to be working on interlapping things.
https://tribewiki.org is yet another asciidoc + nostr client, and a WYSWYG editor would be a great addition to that.
Keep us posted!
