You can see, here, the light view, and how the publication is structured, with an event for each section. (The sections are only visible, if you hover over them. Otherwise, it's just flowing text.)
And here is the CLI output, from the bash terminal. I'm now including an optional tag "type" that contains the text "book", so that it's easy to recognize books.
The formatting is designed for an eBook, but a stylesheet for an online article would probably have the background color for the code sections a bit lighter.
That's what I think isn't really necessary.
I will display those code sections the same way I will display other code sections within my :Zaplab: Zaplab widgets. Chachi will display them in their own style. And even Alexandria has its own style for this.
If creators want :110percent: guarantee over how their visual content is displayed, they should use the formats suited to that: video, PDFs, Hypernotes, ... For textual content like this, this isn't the priority and I think authors very much prefer that the styling of their content fits in with the app their readers choose to engage with it.
The only reason you'd want to have an actual formatting file is when you'd want to, for example, create a PDF or printed book from this. Then you'd use an app to go from the nostr events to some very specific styling you'd define page by page. This app could tap into the nostr events and create something like a word or InDesign file, with all the formatting, that can be shared and collaborated on. Then you'd export from that app to the PDF's or book printers.
I feel like you're not even reading anything I'm writing. Obviously, I'm talking about exporting the data to files.
I think I completely misunderstood what you meant with "a stylesheet for an online article" then. When would you ever need a nostr event for that? That's what I don't get.
Because you can create downloadable articles in HTML. They're packages.
You can then read them offline or upload them someplace else and make them available online, in isolation of the client.
Some of my magazine subscriptions offer this. Read online or download.
You can also create a website with 30040/30041 notes, export it as HTML, and then display it under your domain.
There's something similar to this from the band devs, but this would be something you could host yourself, edit, and overwrite. So, more dynamic and personalized. You could auto-publish after you replace notes, for instance.
You know what I mean? Like, you could have a website consisting of NIP-62 events and just edit/add/delete the events, and the website would upate.
Obviously, you can't dictate to a client, how to display your notes. You can only provide a stylesheet and they are free to ignore it and use their own.
But there can be fields in stylesheets that are used in the .adoc file, like custom fields, and the client might not know how to format those. You can define them in the stylesheet.
Like, you wanted something with very exacting formatting, called a "hypernote". You could just create a .css with a style called "hypernote" and give that to the devs to integrate into their default .css.
Then, you would just need to create a 30041 including the .adoc tag "hypernote" and it would render in HTML, the way you'd defined it. It would use a Nostr Asciidoc event to generate hypernotes on the fly, without storing HTML in the events.
We could add all of the supported tags to a drop-down box and let people add custom ones, or something.
Whatever. Zukunftsmusik.
I see. If I replace "hypernote" with "newspaper style" or "geeky gothic" or sth in what you wrote, I get it. Thanks.
Hypernotes are/will be a different thing 👉 Interactive pdf / microwebsite with a fixed size that :110percent: displays as intended by any app that implements it.
There's no point in having different content formats in the notes because any client can display Asciidoc content however they want. It would be redundant information.
Alexandria displays them as HTML because it's web-based. (There is no such thing as displaying markup in a browser, just HTML.) A client can generate an ePUB, PDF, LaTeX, txt, doc, etc. document from the events and the author can stipulate which stylesheet to use, in that case. But editing that document would have no effect on the state of the event it was generated from; it's a snapshot. The Nostr event is the Single Point of Truth.
