Obsidian & Zettelkasten for Book Summary (Literature Note)
Based on Darin Suthapong's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Import Kindle highlights into Obsidian with Readwise so book evidence is automatically available for later linking.
Briefing
A practical workflow for turning book reading into durable knowledge hinges on one move: convert highlights and personal reflections into a structured “literature note” inside Obsidian, then connect those insights into permanent notes and chains of thought. The payoff is a summary that doesn’t fade after the reading session—each claim can be traced back to the exact highlight, and each insight can be linked to broader ideas already stored in a personal knowledge system.
The process starts with Zettelkasten-style capture, framed through a “six C’s” approach: capture fleeting and literature notes from daily thoughts and consumed information, then connect them, crystallize the distilled insights into permanent notes, and create outputs that strengthen understanding. For book summarization specifically, the capture step splits into two streams: (1) book highlights and (2) the reader’s impressions, reflections, and emerging outline. Kindle highlights can be imported automatically into Obsidian using Readwise, while reflections are captured separately on an iPad in Notability and then linked into Obsidian.
Once the initial outline exists, the workflow shifts into review and refinement. Highlights are checked against the draft summary to spot missing references, add supporting details, and tighten the logic. A key technique here is progressive summarization: repeatedly “highlight the highlight” by exporting Kindle highlights as a PDF into Notability, then revisiting and updating the Obsidian note so links stay current. For faster cross-referencing, Obsidian is split into two panes—one showing the evolving summary, the other showing the highlights—so the writer can directly connect specific passages to specific sections.
To make those connections precise, the method uses block-level linking inside Obsidian. By searching for a phrase from a highlight (e.g., “nice training”) and inserting a link to the relevant text block, the summary becomes navigable: hovering reveals the linked highlight, and clicking jumps back to the Kindle highlight for full context.
After the literature note is refined, the workflow crystallizes insights into permanent notes. Each permanent note is guided by questions aimed at future usefulness: how future self can apply the idea, how it aligns or conflicts with existing notes, and what it means within the larger Zettelkasten network. The permanent notes are then arranged into “chains of thought” by ordering them into a sequence that makes sense, cutting and pasting to establish flow, and tagging the chain (e.g., hashtag thought/not nice). In graph view, filtering by that tag reveals the relationships as a map—an at-a-glance view of how ideas connect.
Finally, permanent notes are tied back to the broader personal knowledge base (“Saddle casting” in the creator’s terminology). The example centers on a book about niceness and social anxiety: the insight that niceness can stem from fear is linked to earlier fleeting notes about fear when meeting people, and then connected to other literature notes such as negative self-stories traced to childhood experiences. The workflow also distinguishes note types with different icons (permanent notes, literature notes, and “concept notes” like scared/fear).
The last step is optional but strongly encouraged: turn the finished summary into an external artifact—an article, YouTube script, or social post—by copying the book summary outline and sharing it publicly, reinforcing learning through communication.
Cornell Notes
The workflow turns Kindle reading into lasting knowledge in Obsidian by converting highlights and reflections into a literature note, then distilling insights into permanent notes. Highlights are imported with Readwise and reflections are captured in Notability, then linked into Obsidian to form an initial outline. The summary is improved through progressive summarization and block-level linking, using split-pane review so each section can be supported by specific highlights. Permanent notes are created by asking how each insight helps future self and how it fits or clashes with existing notes, then organizing them into tagged chains of thought for graph-based visualization. The result is a navigable knowledge network that can be shared externally as an article or post.
How does the workflow transform raw Kindle highlights into a summary that stays accurate over time?
What’s the difference between a literature note and a permanent note in this system?
Why use split-pane editing while refining the book summary?
How are “chains of thought” built, and what do tags accomplish?
How does the workflow connect a new book insight to earlier personal notes?
What’s the optional final step, and why does it matter?
Review Questions
- When refining a literature note, what specific techniques keep the summary tied to the original source highlights?
- What questions should guide the creation of permanent notes, and how do those notes differ from literature notes?
- How do tags and graph view help visualize chains of thought in this workflow?
Key Points
- 1
Import Kindle highlights into Obsidian with Readwise so book evidence is automatically available for later linking.
- 2
Capture reflections separately in Notability, then link them into Obsidian to generate an initial book-summary outline.
- 3
Use progressive summarization by repeatedly revisiting highlights and updating the linked notes so the summary stays grounded in source text.
- 4
Refine the outline by reviewing highlights in split-pane mode and adding missing references or connections.
- 5
Create block-level links from summary sections to exact highlight text so hovering or clicking reveals the supporting passage in Kindle.
- 6
Distill insights into permanent notes using future-utility and alignment/conflict questions, then organize them into tagged chains of thought for graph-based review.
- 7
Share the finished summary externally (article/social/YouTube) to reinforce learning through communication.