@spinningthoughts I used #Logseq enough to appreciate and like its block-based approach and to understand why it’s structured as an outliner. But simpler dedicated outliner tools like Bike don’t appeal to me at all.
For me, outlines are usually a special-purpose way to structure certain kinds of information, and I like that the Outliner plugin for #Obsidian lets me combine outlines with standard paragraphs in a single file.
@EpiphanicSynchronicity The way I would frame it, the Outliner fills the role of, well as above: capture-and-triage. It keeps information together so that during triage you can *move things around*.
After that come different interfaces and also data structures for the purposes of review and synthesis and integration.
@spinningthoughts Not saying this is right or wrong for anyone else, but *for me* sometimes capture and triage is best accomplished with simple or nested hierarchical bullet points, and other times one or more paragraphs, or one or a series of freestanding individual sentences or phrases.
And (again for me), outlines/bullets aren’t *just* for quick capture and triage. Sometimes they’re the best way to present ideas and information in their final form, whether on their own or among paragraphs.
@EpiphanicSynchronicity challenging my own definitions in a good way here. All of this definitely also belongs in the overall system design and definition.
To sharpen the above: that‘s the justification for why the design goes down as far as making individual bullets full independent entities.