Get AI summaries of any video or article — Sign up free
How I converted my physical Zettelkasten (slip-box) to Obsidian thumbnail

How I converted my physical Zettelkasten (slip-box) to Obsidian

Joshua Duffney·
5 min read

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.

TL;DR

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?

The workflow treats attention as a limited resource. Reading and taking literature notes happen in one block, then abstraction happens in another: literature ideas are distilled into atomic, reusable units. Those atomic ideas become permanent notes, which then accumulate until they’re added to the slip-box—often within 24 hours. This staged approach mirrors how the system manages cognitive load rather than trying to do everything in one pass.

What role do keywords and aliases play if note titles aren’t treated as stable names?

Keywords act as navigational descriptors that can span multiple notes. They’re not meant to be the literal name of a single note; instead, they represent themes that can grow into topics. Aliases add a digital convenience layer: they let the user search for a concept (like “permanent note”) and jump directly to the relevant note, while the index and linked pathways still drive discovery.

When does a keyword-only theme become a structure note?

The system uses a threshold based on how many notes cluster under a theme. Once a keyword has around three or four attached notes, it’s time to create a structure note so the topic can be organized more coherently. The names of these structure notes stay “temporarily valid” and can be revised as understanding improves.

How does the index support “navigation by path” rather than direct searching?

Search is used to reach the index, not to jump straight to every destination. From the index, the user follows linked pathways—like moving from “smart notes” to related sequences and then to specific themes—so stumbling upon adjacent notes becomes part of the workflow. That repeated exposure helps load relevant ideas into short-term memory when they’re needed.

What’s the difference between inserting a note into the slip-box and connecting it to other notes?

Insertion is about discoverability: the note must be linked into the index/structure sequences so it isn’t orphaned. Connecting note-to-note links is a deeper relationship step that can be done later. This separation keeps the system usable early, even before the full web of connections is built.

How does the workflow handle expanding topics over time?

Topics expand through sequences and evolving structure. In the slip-box folder, related notes can be organized into sequences by appending letters/numbers to unique IDs, allowing a topic to grow as new permanent notes are added. Structure headings and labels are treated as fluid drafts that can be renamed or moved when the creator’s understanding changes.

Review Questions

  1. What threshold (in terms of number of related notes) triggers the shift from keyword-only organization to creating a structure note?
  2. How does the workflow use aliases to balance fast retrieval with the slip-box habit of navigating via linked pathways?
  3. Why does the system postpone note-to-note linking, and what problem does that postponement avoid?

Key Points

  1. 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. 2

    A single index acts as the navigation hub; search is used to reach the index, not to bypass it entirely.

  3. 3

    Keywords provide bottom-up thematic organization, and once a theme reaches roughly 3–4 notes, it graduates into a structure note.

  4. 4

    Structure notes and headings are intentionally “temporarily valid” so they can be renamed or reorganized as understanding improves.

  5. 5

    Sequences expand topics by appending letters and numbers to unique IDs, letting a topic grow without redesigning the whole system.

  6. 6

    Aliases enable quick jumps to important concepts while still keeping navigation centered on index pathways.

  7. 7

    Note insertion (making a note discoverable) is separated from later note-to-note linking to prevent orphan notes and reduce early complexity.

Highlights

The conversion prioritizes paper-faithful behavior in Obsidian—index-driven navigation and bottom-up topic growth—over building an elaborate graph.
A keyword becomes a structure note when it accumulates about 3–4 related permanent notes, reflecting a shift from “theme tagging” to “topic framing.”
Aliases provide search speed, but the workflow still pushes users to navigate through the index path to repeatedly surface related notes.
The system separates “getting into the slip-box” from “connecting to other notes,” deferring deeper linking to keep the process manageable.

Topics