death by nips. honestly, it's not a bad way to go.

Been thinking about how to navigate stuff like that structure for nips on github is to rigid to navigate and gives off a vibe that you need understand a majority of the content before you can get started on your own project. (1) should probably move to a knowledge base format (wiki-like, wikifreedia) with (2) modular articles: being able to compose a new article from other article fragments/section. my spec for that is a blend of the long form content and lists hyperlinked, composable, remixable. - Describe your client by composing fragments of implemented nips, pointing to the original content. - Apply a transformation to the nip44 definition - you don't need/care to write the original definiton, but you want your readers to read it alongside the implementations in different clients. If a fragment comes from an existing article, you can navigate to the source within the KB https://wikifreedia.xyz/nkbip-01/dc4cd086cd7ce5b183