I’d love a node based interface to build “notes trees”.

Think of the Notes Tree as an article, but it is made of a multitude of notes, highlights and links by the author AND other plebs. You start reading at the trunk with the intention of reaching the end, the tip of the tree. But, you can sidetrack your audience in branches (additional information, anecdotes, sponsored content, referenced conversations, media,…).

This would make the reading of an article a tad more interactive. If I am not interested by the content of a branch, I can read its summary note and move on, or if I want to I can explore the branch.

When building the tree I would see the existing connection between notes (quote notes, replies) and decide what notes and what connections I want to include in the note tree. I could load notes and other “assets” in a “notes library” and easily drag, drop, connect and rearrange. I could write private notes that would be published only once the tree is published.

The UX of exploring a published tree would be client specific (same with the building of it)

VFX compositing meets blog writing. Lateral thinking or waste of time?