Thanks. Yup agree :Check:
Cool, I can work with that. Then, as long as it's text, it can just be 99% the same creation / reading tools under the hood. Just need to switch icon, name and (sometimes) serif to sans font.
I suggested we add a "type" tag, to denote specific content.
Yes, this would be for any longer, more-complex document.
https://github.com/nostr-protocol/nips/pull/1600#issuecomment-2544617399
Discussion
Asciidoctor stylesheets will handle the custom formatting stuff, for HTML rendering or publishing. We haven't implemented that, yet, though. Would probably be a linked 30042 event, containing formatting. Or some new "style" tag, or whatnot.
Currently have that planned for v0.3.0.
Like, we'll need to offer some different themes for publishing books or journals, and make them customizable. So, it's not just HTML stuff.
Of course, you will be able to design the content with adoc once, and then set different stylesheets for different formats (ePUB, LateX, HTML, GitHub-flavor markdown, etc.) many times.
So, probably needs to be a separate event, specifying the format for a particular use case (book, hypernote, online Magazine, etc.)
Like, you could publish something as a series of articles, as an online magazine, or as a document to be downloaded and read on ePaper. You wouldn't necessarily want to formatted identically, everywhere, or using the same title page or cover Image, or whatnot.
You could also reuse format events, or reuse zettles in a different document with different formatting.
Complicated, so v0.3.0.
You can see how difficult it is, just configuring index event tags. 😂
Why do you need an event for the formatting (stylesheet)? Why can't it just **be** the format (file type)? And then you link those PDF's, epubs, etc... to the index event.
You already have a format type (Asciidoc). This is for display or export to other types.
You don't want to have a bunch of event-copies containing different formatting, as you'd then have to change the event content in each copy, to edit it. Nightmare.