Zettelkasten: 3 More Tips

TL;DR

Treat tags as entry points into a subset of notes; use links to express relationships between notes.

Briefing Cornell Notes

Briefing

A well-run Zettelkasten system depends less on adding more metadata and more on using a few structural tools with discipline. Three fixes stand out: tags function as entry points (not as note-linking glue), a dedicated tag index acts like a “home page” for searching, and list sequences—often called “fall gazette”—provide a clean way to branch ideas into structured trails.

First, tags should be treated as doors, not corridors. In many Zettelkasten setups, tags get used like extra pathways that imply relationships between notes. Here, that’s the wrong mental model. Tags don’t determine how notes link to one another; links do. Instead, tags exist to give readers (and the system) controlled entry points into the slip box—typically by using the same keyword across a small number of slips. The transcript emphasizes parsimony: only a very small fraction of notes should carry tags. If the slip box is a building, tags are doors to specific rooms, not hallways connecting everything.

Second, the system benefits from a tag index that lists every tag and where it points. The approach described mirrors Luhmann’s practice: whenever a new tag is introduced, it’s added to an index. That index becomes the starting point for queries—where someone with a question begins before following internal links deeper into the network. The transcript also notes that this can be implemented in a software-agnostic way, even if some tools already generate tag lists automatically.

Third, list sequences (fall gazette) are presented as another linking mechanism built from branching. A list sequence is a child note that grows out of an existing parent note. One idea leads to a note; a related but distinct idea branches off; then another branch continues from the same parent or from earlier branches. The result is a structured chain of related notes that can be followed as a sequence. Luhmann used this pattern frequently, and the transcript illustrates how IDs can reflect the branching structure—such as 1 → 1a → 1a1.

Finally, the transcript contrasts that structural ID style with a modern alternative: using date/time as IDs. Digital tools make searching, linking, and retrieval easier when IDs encode time, and that practical affordance is offered as a reason many people moved away from Luhmann-style alphanumeric branching IDs.

Together, these three additions—door-like tags, an index for fast entry, and branching list sequences—aim to keep the slip box navigable. The goal isn’t more organization for its own sake; it’s a system where retrieval is predictable and relationships are expressed through the right mechanism: links for connections, tags for entry, and branching structures for evolving idea trails.

Cornell Notes

The transcript recommends three structural upgrades to a Zettelkasten workflow: use tags sparingly as “doors” (entry points) rather than as “corridors” that create relationships, maintain a tag index as a starting page for queries, and use list sequences (“fall gazette”) to branch related ideas into child notes. Tags do not link notes; links do. A tag index should be updated whenever new tags are added, so searching begins at the index and then moves through internal links. List sequences create structured trails by branching from parent notes, and IDs can mirror that branching (Luhmann used hierarchical IDs like 1 → 1a → 1a1), while modern systems often use date/time IDs for better digital retrieval.

Why does the transcript insist that tags are “doors not corridors”?

Tags are meant to provide entry points into the slip box, not to determine how notes connect. Links are the mechanism that ties notes together. The transcript stresses that tags should be used with restraint—only a very small number of slips are tagged at all—so each tag functions like a door into a limited set of notes rather than a network-wide hallway.

What is a tag index, and how does it change how someone searches a Zettelkasten?

A tag index is a maintained list of all tags in the system. When a new tag is created, it’s added to the index. That index acts like a home page: a person with a question starts by checking the index, then follows the relevant internal links to reach the deeper notes.

How do list sequences (“fall gazette”) link ideas differently than simple tagging?

A list sequence is a child note branching off from a parent note. One idea produces a note; a related but not identical idea branches from that same parent; additional ideas keep branching, creating a structured trail. This is a linking method based on branching relationships, not on applying tags.

How did Luhmann’s ID scheme relate to list sequences, and what’s the modern alternative?

In the described example, hierarchical IDs mirror branching: a note labeled 1 spawns a branch labeled 1a, and another branch could become 1a1. The transcript contrasts this with modern practice: many people use date/time as IDs because digital tools improve searching, linking, and retrieval when IDs encode time.

What practical rule emerges from the transcript about when to tag notes?

Only tag a note when it should serve as an entry point under a specific keyword, and keep tagging sparse. The system should not treat tags as mandatory metadata on every slip; instead, tags should be reserved for a small subset of notes that benefit from being reachable via that keyword.

Review Questions

In a Zettelkasten, what should links do versus what should tags do, and why does confusing those roles hurt retrieval?
How would you design a tag index so it supports fast question-driven searching rather than slow browsing?
Describe how a list sequence grows from a parent note and how IDs can reflect that branching structure.

Key Points

1
Treat tags as entry points into a subset of notes; use links to express relationships between notes.
2
Use tags sparingly—only a small fraction of slips should carry tags to keep navigation meaningful.
3
Maintain a tag index listing every tag and update it whenever a new tag is added.
4
Start searches from the tag index, then follow internal links to reach the relevant network of notes.
5
Use list sequences (“fall gazette”) to branch related ideas into child notes, creating structured trails of thought.
6
Consider hierarchical IDs that mirror branching (e.g., 1 → 1a → 1a1) or use date/time IDs if digital retrieval is the priority.

Highlights

Tags don’t connect notes—links do. Tags mainly provide controlled entry points, so they should be used sparingly.

A tag index functions like a “home page” for the slip box: it’s the first place to look before diving into linked notes.

List sequences grow by branching child notes from parent notes, and IDs can mirror that branching structure (or be replaced by date/time IDs for modern retrieval).

Topics

Zettelkasten
Tags
Tag Index
List Sequences
Note IDs