Outliner Block
An outliner block is the fundamental atomic unit of information in Logseq (and similar outliner apps like Roam Research or Workflowy).
Instead of treating a document as a continuous sheet of text made of traditional paragraphs, an outliner treats every single line or bullet point as an independent, self-contained block of data.
Key Characteristics of an Outliner Block
1. Granular Identity
Every bullet point you create in Logseq is assigned a unique identifier (a invisible UUID under the hood). Even if a block is just a single sentence inside a long daily journal, Logseq views it as its own distinct item.
2. Strict Hierarchical Structure
Blocks exist within parent-child tree relationships formed through indentation (tabbing):
- Parent Block: Holds main ideas or context.
- Child Block: Indented underneath a parent block, inheriting its context.
- Folding/Collapsing: You can collapse any parent block to instantly hide dozens of child blocks underneath it, keeping long pages easy to scan.
3. Infinite Nesting
You can indent blocks as deep as you need (Parent \(\rightarrow\) Child \(\rightarrow\) Grandchild \(\rightarrow\) Great-Grandchild). This allows you to break complex ideas or project breakdowns into manageable sub-components without cluttering the screen.
Why Blocks Matter: The Power of Block Manipulation
Because every bullet point is an independent block, you can interact with individual ideas in powerful ways:
- Block Referencing: You can summon a specific bullet point from any page or journal into a completely different page without retyping it.
- Block Embedding: You can mirror a block somewhere else. If you update the content in the embedded block, it updates everywhere across your vault in real time.
- Granular Linking: You don't just link to a whole page (e.g.,
[[Project Alpha]]); you can link directly to a specific sentence or sub-task within that page.
- Zooming (Focus Mode): Clicking on any block's bullet point "zooms in" to make that specific block the root of your page, temporarily hiding everything else so you can focus on one thought thread.
Document-Based vs. Block-Based Comparison
| Aspect | Traditional Document (e.g., Word, Notion, Obsidian) | Outliner Block System (Logseq) |
|---|---|---|
| Basic Unit | The Page / Paragraph | The Individual Bullet (Block) |
| Structure | Linear prose with headings (# H1, ## H2) | Nested bullet tree |
| Linking Level | Links connect Page A to Page B | Links connect specific ideas across any page |
| Primary Interaction | Writing long-form prose top-to-bottom | Capturing rapid atomic thoughts and organizing hierarchically |