Knowledge Concepts
A structure note (also called a map of content or index note) is a note that organizes other notes — a high-level overview that links to related permanent
A structure note (also called a "map of content," "index note," or "hub note") is a note whose primary purpose is organizing and linking to other notes — rather than containing a new idea itself. In a Zettelkasten or linked note system, a structure note provides a bird's-eye view of a cluster of related permanent notes: it's the entry point and table of contents for a topic or project, letting you navigate a group of ideas without having to remember which specific note contains which specific thought.
Structure notes are the scaffolding that organizes atomic notes into navigable knowledge.
The structure note concept emerges from the practical challenge of using a Zettelkasten at scale. Niklas Luhmann's slip-box grew to 90,000 cards — and he navigated it through a combination of direct links between notes and higher-level index cards that grouped related notes by theme or project.
Luhmann maintained a separate "keyword register" — effectively a structure note system — that mapped themes across his slip-box. When developing a book chapter, he'd begin with the keyword register, find the relevant permanent notes, and see how they connected.
Sönke Ahrens describes this in How to Take Smart Notes (2017): as a slip-box grows, emergent outlines form from clusters of linked permanent notes. A structure note makes that emergent outline explicit.
The term "map of content" was popularized by Nick Milo, creator of the Linking Your Thinking (LYT) framework — a method for using structure notes as the primary navigation layer in an Obsidian-based knowledge system.
A structure note typically has three components:
1. An overview statement: What is this cluster about? A 2-4 sentence introduction describing the theme, project, or question the linked notes address.
2. A curated list of links: Links to the most relevant permanent notes on the topic, often with a brief annotation indicating what each note contributes.
3. A brief synthesis: Optional but valuable — a statement of what you currently understand about the topic, or the key tensions/questions that remain unresolved. This is what distinguishes a structure note from an index: it contains your current thinking about the relationship between the linked notes.
Example structure note:
Map of Content: Cognitive Bias and Decision-Making
This cluster covers the mechanisms of cognitive bias, the debate about their reducibility, and practical debiasing approaches. Growing since 2024 reading program on behavioral economics.
Foundational mechanisms:
Specific biases:
Debiasing:
Open questions: The relationship between cognitive bias in individuals and organizational decision-making (note 103) is underdeveloped. The debiasing literature is more pessimistic than the popular literature suggests — most techniques work only in specific conditions. Worth developing a permanent note on this gap.
| Feature | Structure note | Permanent note |
|---|---|---|
| Primary content | Links to other notes + navigation | A single idea, own words |
| Represents | A cluster or theme | One idea |
| Has links | Yes — outgoing to permanent notes | Yes — bidirectional to related notes |
| Contains new idea | Usually not | Yes |
| Scale | One per theme/project | One per distinct idea |
| Stability | Updated as cluster grows | Relatively stable once written |
Structure notes are meta-notes: notes about groups of notes. They're necessary because a flat, unstructured collection of permanent notes becomes difficult to navigate as it grows.
A product designer has been building a knowledge system in Obsidian for 18 months. They have 340 permanent notes spanning UX research, product strategy, cognitive psychology, and business development.
Without structure notes: When starting a new project on onboarding redesign, they search "onboarding" — get 23 notes. They search "user research" — get 41 notes. They spend 40 minutes trying to reconstruct which notes are most relevant. They know they have a cluster of ideas about first-time user experience but can't efficiently navigate to them.
With structure notes: They have a structure note called "Map of Content: First-Time User Experience" that links to:
Plus a brief synthesis: "The core tension in onboarding design: reduce friction (fewer steps, simpler choices) vs. ensure user understands value before investing. The evidence favors progressive disclosure with immediate value demonstration over comprehensive setup flows."
Starting the onboarding project: they open the structure note, read the synthesis, navigate to the 5 most relevant permanent notes. 10 minutes instead of 40.
Topic maps: Overview of a subject area you've been building notes on. "Map of Content: Behavioral Economics," "Map of Content: API Design Patterns." These grow as the topic cluster grows.
Project notes: A hub for a current project — linking to all relevant permanent notes, resources, decisions, and open questions. Closer to a project home page than a topic map.
Outline notes: A structure note organized as an outline of an essay, article, or document in progress — each section linked to the permanent notes that will be developed into prose for that section.
Author/source index: A structure note organizing everything you've read from a particular author or in a particular domain: "Notes from Kahneman's work," "Zettelkasten implementation notes."
Structure notes emerge naturally when:
The mistake is creating structure notes too early — before there are enough permanent notes to organize. An empty or near-empty structure note is organizational overhead without value. Let the cluster grow first; create the structure note when navigation becomes difficult.
"Structure notes are the primary entry point to the slip-box." In a well-developed Zettelkasten, both direct links (following links between permanent notes) and structure notes (navigating from topic overview to specific notes) serve different navigation purposes. Structure notes are useful but not the only way to navigate.
"A structure note is just an index." An index lists notes; a structure note curates and synthesizes them. The synthesis — "what I currently understand about this topic, and what questions remain" — is what distinguishes a structure note from a plain list of links.
"I should have a structure note for every topic." Create structure notes when they solve a navigation problem, not as a requirement. Small clusters (under 8 notes) often navigate fine through direct links; structure notes add most value for larger, more active clusters.
Permanent note: The atomic note that structure notes link to and organize.
Zettelkasten / slip-box: The note system in which structure notes provide navigation.
Map of content (MOC): Nick Milo's term for structure notes in the Linking Your Thinking framework — widely used in the Obsidian community.
PARA: Tiago Forte's organization system — structure notes parallel the "Projects" and "Areas" levels, providing overviews of active work and ongoing domains.
What's the difference between a structure note and a folder? A folder organizes files by location — a file can only be in one folder. A structure note organizes notes by linking — a permanent note can be linked from multiple structure notes if it's relevant to multiple themes. Structure notes support non-hierarchical organization; folders are inherently hierarchical.
How do I know which permanent notes to include in a structure note? Start with the notes most central to the theme — the ones you'd want a new reader to understand first. Then add notes that address the key questions or tensions you've identified in the topic. A structure note doesn't need to include every note on a topic — only the most navigationally useful ones.
Should I update structure notes regularly? Yes — structure notes should reflect the current state of your knowledge. When you add new permanent notes to a topic cluster, update the relevant structure note. When your understanding of a topic synthesizes further, update the synthesis statement. A stale structure note is less helpful than no structure note.
Structure notes solve the navigation problem that emerges as a Zettelkasten grows from dozens to hundreds to thousands of notes. Without them, the atomic notes that make individual ideas findable become collectively unnavigable — you know the notes exist, but can't efficiently access the right cluster when you need it. With them, each topic cluster has a curated entry point and a synthesis of current understanding — converting a flat network of notes into a navigable knowledge system.
For more on this, see Web Clipping vs. Bookmarking.
More WebSnips articles that pair well with this topic.
Knowledge transfer is the deliberate process of moving knowledge from where it exists — an individual, team, or system — to where it is needed, in a form
A browser extension is a small software add-on installed in a web browser that adds features or modifies behavior — blocking ads, saving passwords
A content calendar is a planning tool that schedules what content will be published, when, where, and by whom — turning a content strategy from vague
A context window is the maximum amount of text an AI language model can process in a single interaction — everything in the prompt, the conversation
A knowledge silo is a condition where knowledge, information, or expertise is isolated within a team, department, or individual — inaccessible to others
A large language model (LLM) is a neural network trained on massive amounts of text to predict and generate language.