Design for #Zapdocs is ready.
Discussion
Next is:
- building it out with the #ZaplabDesign widgets
- pointing it to just one specific kind 30040 (type: documentation) on one specific set of relays (kudos to nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz for this event kind)
Then:
- fetch replies, zaps, etc...
This app will not let you sign events (replies, zaps, etc..) within it.
For that it'll point to the recommended apps by the Communities this 30040 is targeted at.
Well that’s quality stuff! Congratulations
After 5 minutes poking around your posts and website, I’m impressed but… I’m still not clear.
Can I please get a link to find out more about #Zapdocs?
The #Zapdocs idea only came up two days ago.
I need a Documentation for the :Zaplab: Zaplab Design package I'm building in Flutter.
👇
I can't find anything yet that's Nostr-based and realize the kind 30040 event is perfect for this.
👇
I have my design widgets, asciidoc (and soon Markdown) renderer, etc... and can totally build this
👇
I make a design for the thing first
👇
I share said design for feedback
That's it, for now 😉
I'm working on something that facilitates structured documentation, technical reports, proposals, etc.
Have you looked at using readme.com?
#notetoself Need to display two levels of "Chapters" in the main tree of the docs (only when the kind 30040 provides it)