Making the :Zaplab: #ZaplabDesign package work on Web too.
That way I can:
- use my #asciidoc renderer for its documentation online
- build a simple #Zapdocs app with it, so that others can do so too
https://cdn.satellite.earth/84b67564ca48e0d15f33e18229395fd1e7be1eafc0b13f96049b64bfac3f43d2.mov
wow, can I use this from a regular React JS app?
I have no clue sir. That'd sure be neat and avoid me having to write out the design package in React too 😜.
I'll ask Claude, brb.
The thing I hate the most on Markdown and AsciiDoc is the 6 levels of headers that we need to find a way to render nicely with just formatting changes (we can't do numberated sections).
No one uses 6 levels of headers without enumerating them. It's just dumb.
:110percent: true and frustrating indeed, especially since around here we can have chapters as separate events.
I like my white 🔄 grey color switching as a work around.
Solutions without color change are unreadable for me.
That's why I am excited to see some movements to define Nostr's own markdown structure. We need to solve this.
