Improvements to note portability support both LogSeq’s stated purpose and the natural underlying needs of users.
- Logseq is a knowledge base for private thoughts.
- Blocks are the smallest addressable and thus linkable unit.
- Pages are a special form of blocks.
- Knowledge base as capturing thoughts infers that it is emergent (think not just agile, but in complexity theory)
The term emergent entity essentially refers to complex systems or patterns that emerge from the interaction of simpler components. (blocks)
Blocks are the smallest addressable unit. Ideas could be small or in the form of systems or patterns. Emergent design necessitates blocks being easily movable and referencable (linkable). Nomadic but not wandering
So… the sticky pad and board. Blocks, pages & graphs for a hierarchy of knowledge. The other components are still part of the architecture and may be used differently for different use cases. What is novel writing? A hierarchy of story. Line, paragraph, chapter, and book.
Proposed sticky note a board use case: in pictures
So by “portability” and “sticky notes” do you mean “moving blocks from one page to another, without losing their identity”?
- Why to move a block around, instead of simply modifying its tags or properties?
- Moving a block around is:
- for when its previous position was wrong
- not for signifying a change of its status
- Blocks can have:
- multiple tags
- multiple mutable properties
- but only one direct hierarchical parent
- The various parts and sections of a story are hierarchical, while the knowledge within them is not.
- Logseq combines:
- the restrictive hierarchy of an outliner
- the unrestrictive connectivity of a graph
- If blocks become nomadic, they won’t always be found in some expected place.
- The user may need to hunt for them.
- In contrast, if blocks have a natural expected place, they don’t need to move.
- The user’s memory has an easier time navigating the graph.
- The importance of that increases quickly as the graph grows.
I mean move a block to a different hierarchical parent. Imagine you put one concept (block) under a concept (page). But you want to change that easily. You want to move it like a sticky note to another column because thought (block) creation is different than thought (block) organization.
As in the difference between relative database design and page database design. If you think your thoughts are organized, think again. They are chaotic, but you often lose them if you don’t note them. The organization of blocks is a secondary step to the ideation of blocks.
Does that make sense to you?