How I converted my physical Zettelkasten (slip-box) to Obsidian
Based on Joshua Duffney's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Permanent notes are produced by abstracting literature ideas into atomic units, then added to the slip-box on a cadence (often within 24 hours).
Briefing
The core takeaway is a practical workflow for converting a physical Zettelkasten (“slip-box”) built from Smart Notes into Obsidian without over-engineering: import permanent notes, then integrate each new note by indexing it with keywords/aliases and placing it into the right “structure note” sequence so it’s navigable later. The emphasis isn’t on building a perfect graph. It’s on recreating the physical system’s bottom-up discovery—where navigating through an index path repeatedly surfaces related ideas and keeps them within reach.
The process starts with a deliberate reverse-engineering goal: could enough notes be taken from Smart Notes to reconstruct the system well enough to “use Smart Notes to create Smart Notes”? Over roughly a month, the creator wrote 100+ physical note cards (spanning more than 46 pages) and then imported them into Obsidian. The first iteration keeps things close to the paper slip-box: no extra custom plugins, and a focus on how permanent notes move into the slip-box and become findable.
A key design decision is separating attention stages. Literature reading and literature-note creation happen in distinct time blocks, and permanent notes are produced by abstracting literature ideas into atomic, reusable units. Those permanent notes then enter the slip-box on a cadence—often within 24 hours. In Obsidian, permanent notes live in a “slip box” folder, with optional note sequences handled by appending letters and numbers to unique IDs so topics can expand as understanding grows.
Navigation is built around a single index rather than scrolling. The index links to the rest of the system, while keywords act as a flexible layer of organization. Instead of treating note titles as stable categories, keywords are used to reflect themes spanning multiple notes. When a keyword accumulates enough related notes—around three or four—the system shifts from a keyword-only approach to creating a “structure note” that can hold a more coherent topic. These structure notes are intentionally “temporarily valid,” meaning headings and labels can be renamed or reorganized as the understanding matures.
The walkthrough then demonstrates how a new permanent note gets integrated. A note is opened, its best-fit structure is located via the index and existing sequences, and then the note is linked into the appropriate structure note using keywords and, when helpful, aliases. Aliases support fast retrieval via search (e.g., jumping directly to “permanent note” concepts) while still preserving the slip-box’s navigation-by-path behavior. The system also treats the index as the central navigation hub: search brings up the index, and from there the user follows linked pathways that intentionally expose additional relevant notes.
Finally, the workflow distinguishes between “getting a note into the slip-box” and later “connecting note to note.” The first step prevents orphan notes by ensuring the note is discoverable through the index and structure sequences. Deeper cross-linking is deferred for a separate pass. The result is a simplified, paper-faithful digital slip-box that prioritizes retrieval through navigation, bottom-up topic formation, and the slow-hunch principle—good ideas need time before they crystallize into stable structure.
Cornell Notes
The conversion centers on rebuilding a physical Zettelkasten workflow inside Obsidian using a bottom-up index, keywords, and structure notes—without chasing a complex graph. Permanent notes are created by abstracting literature ideas into atomic units, then added to the slip-box on a regular cadence (often within 24 hours). Navigation relies on a single index that links to sequences and themes; keywords guide discovery, and once a theme reaches about 3–4 related notes, a structure note is created to hold a more coherent topic. Aliases enable quick search while preserving the slip-box habit of navigating by linked pathways. Deeper note-to-note linking is postponed so new notes aren’t left orphaned.
Why separate literature reading, literature-note abstraction, and permanent-note creation into different time blocks?
What role do keywords and aliases play if note titles aren’t treated as stable names?
When does a keyword-only theme become a structure note?
How does the index support “navigation by path” rather than direct searching?
What’s the difference between inserting a note into the slip-box and connecting it to other notes?
How does the workflow handle expanding topics over time?
Review Questions
- What threshold (in terms of number of related notes) triggers the shift from keyword-only organization to creating a structure note?
- How does the workflow use aliases to balance fast retrieval with the slip-box habit of navigating via linked pathways?
- Why does the system postpone note-to-note linking, and what problem does that postponement avoid?
Key Points
- 1
Permanent notes are produced by abstracting literature ideas into atomic units, then added to the slip-box on a cadence (often within 24 hours).
- 2
A single index acts as the navigation hub; search is used to reach the index, not to bypass it entirely.
- 3
Keywords provide bottom-up thematic organization, and once a theme reaches roughly 3–4 notes, it graduates into a structure note.
- 4
Structure notes and headings are intentionally “temporarily valid” so they can be renamed or reorganized as understanding improves.
- 5
Sequences expand topics by appending letters and numbers to unique IDs, letting a topic grow without redesigning the whole system.
- 6
Aliases enable quick jumps to important concepts while still keeping navigation centered on index pathways.
- 7
Note insertion (making a note discoverable) is separated from later note-to-note linking to prevent orphan notes and reduce early complexity.