Zettelkasten note-taking in 10 minutes
Reading is hard and books don’t work. Zettelkasten aka slip-box note-taking is the new cool kid on the block. Don’t go down the same rabbit hole as I did, researching the method for tens of hours. This article should be enough of the introduction to get you started.
Illustration: Ljubica Petkovic
Slip-box method promises to prevent your notes from piling up deep within your note-taking app and being forgotten. Instead, using this method will improve the value of your notes as you create more of them. This method also gives you better and quicker feedback than usual note-taking.
As with everything else you want to utilize iteration. Read this article, use it to create your first couple hundred notes and then research more details if you feel like your current process should be improved.
The slip-box method
The source for the method summary is Sönke Ahrens’ book How to Take Smart Notes. I only added the technical aspects.
You write notes with a clear purpose: your future self is going to be reorganizing them and using them to produce articles or books.
You fill your slip-box with notes by following this process:
1) make notes as you read
Advice #2: Always use your own words. Copying doesn’t give you feedback on your understanding.
Let’s call these resource notes. Writing resource notes is where you get the first feedback from the method: Are you paying attention and do you understand the text? At this step, you are not trying to predict how your notes are going to fit in the slip-box, you are just trying to capture the essence of the text.
You can use a separate app like Zotero for these notes. But I recommend having them as Markdown files in a
Folder structure so far:
└── Resources └── Sonke Ahrens - How to Take Smart Notes.md
--- title: How to Take Smart Notes: One Simple Technique to Boost Writing, Learning and Thinking – for Students, Academics and Nonfiction Book Writers author: Sönke Ahrens type: book link: https://www.goodreads.com/book/show/34507927-how-to-take-smart-notes --- # How to Take Smart Notes - **Short feedback loop** - Writing literary notes provides quick feedback on our understanding of the text. We double-check this understanding when we try to make permanent notes out of the literary notes. (p54) - Fleeting notes - they are supposed to capture an idea for a brief period before it is processed, 1 or 2 days max (p43)
The file content format is arbitrary, I choose to use Frontmatter for the metadata, but it’s not that important.
2) write atomic, self-contained, permanent notes
Remember, the purpose of slip-box is to aid your future self to make use of the notes for writing. The main unit of information within the method is a permanent note. This note is:
- atomic: always focused on a single topic, that makes linking notes easier
- self-contained: you will forget the context in a few weeks, the note needs to explain itself in separation from the fleeting context
- permanent: you are never going to delete the note, it might just fade into the background if there aren’t many links to it
- concise: few paragraphs maximum, restricting the size helps you get the gist and keep the note atomic
You try to turn you reference notes into permanent notes whilst avoiding conflict of concepts and duplication, these problems show the clearest when you think “How am I going to link this note to the other of my slip-box notes?”
Permanent notes are just markdown files in a separate folder. These files need to have a unique identifier so other notes can link to them unambiguously.
Folder structure so far:
├── Resources │ └── Sonke Ahrens - How to Take Smart Notes.md └── Permanent notes └── 20200605153129 Slip-box.md
3) link permanent notes together
The purpose of linking is to give you feedback, avoid duplication and capture the context of the permanent note. Ask yourself: How does the piece of information fit into the network of my permanent notes? Does it complement, contradict or otherwise interfere with your current notes?
The linking is done by placing links like these
[] into notes. Most of the slip-box software allows you to click on this link and opens a note with ID
20200606154308 for you.
Folder structure so far:
├── Resources │ └── Sonke Ahrens - How to Take Smart Notes.md └── Permanent notes ├── 20200605145305 Slip-box software.md └── 20200605153129 Slip-box.md
# Slip-box ... See also: - [] Slip-box software
graph LR; A["20200605153129 Slip-box"] -- "[]" --> B[20200605145305 Slip-box software]
4) tag permanent notes
Advice #3: Tag the notes by the context you would like to retrieve it by
Example: You have a note on Stanford prison experiment3. Using tags like
#experiment is hardly going to aid you in finding this note when you are writing or thinking about a problem. Better would be
#"power dynamics in groups"
#"misuse of power"
This is the part that took me a long time to research. But it is simple.
Zettlr in 2 minutes
- Download and install Zettlr (on Mac
brew cask install Zettlr)
- Set it up for Zettelkasten
- Create a new note (
N), add name the generated ID (e.g.
20200606154308 My first note.md)
- Create a second note (e.g.
20200605145305 My second note.md)
- Link from first note to second note by typing
[[in the first note and using auto-complete
- Archive - looks great, no vendor lock-in, but not open-source and it is macOS only
- nvAlt Famous notational velocity.
- Zotero - you might want to add this to your toolbox if you plan on academic publication of your work. Overkill for anyone else.
The closest to a full slip-box example are Andy Matuschak’s notes.
This should be enough detail to get you started. The critical idea is atomic notes linked together. That prevents the notes from being forgotten somewhere deep in your note-taking app.
Zettlr is a good app to start with. The slip-box is just a few text files linked together with unique ids. Many other apps support the same linking style as Zettlr.
Don’t do a big migration of your current notes. You can migrate them when you are planning to use them.
This article has been translated to Russian language by Vladimir on softdroid.net.
I changed the example from Sonke’s book a bit to make more sense to me. ↩︎