I chose to not specify how to create sections which could be just as easily a stylistic choice as it is a client choice. Maybe the client only wants to split second level headings of markdown or recursively create individual articleheaders for all heading levels and only have bulleted items as notes. Having the option allows for heterogeneous media - let The Nostr Report build a modular article of the week for events that happened. Composed of short form, long form, git events and a popular modular article that itself aggregates notes surrounding some topic. Maybe a user wants to make an artistic literary tribute to Douglas Hofstadter and make a book that not only references itself (as books occasionally do), but to branch, twist into itself becoming its own maze to navigate. Sure, why not? ๐Ÿคท

Replies (3)

I was just thinking it'd get more traction, if we could have a diagram showing example structures for different types of documents, and then I could create test collections for the different types and they could see how it works.
The article header in theory should help you not worry about how nested it is. You are only traversing one list at a time and using the rules to render each individual element. ``` def renderHeader(nevent) for e in nevent.tags: render(e, kind=e.kind) ``` An article header would just render the .content feld, which is just stringified json metadata not unlike kind0. So it will just be a title card among the other notes that are rendered - keeping the rest of the article unrendered beyond that level.
โ†‘