Video summary
Obsidian: The King of Learning Tools (FULL GUIDE + SETUP)
Main summary
Key takeaways
Main ideas, concepts, and lessons
-
Purpose of the video
- The speaker introduces Obsidian as a “personal network of knowledge,” aligned with the Zettelkasten / Second Brain approach.
- The value comes from a simple, minimal, sustainable workflow rather than chasing a “perfect” setup.
-
Hidden danger when starting
- Watching many different tutorials can lead to perfectionism and a “Frankenstein” system:
- Mixing features from many creators
- Constantly optimizing
- Adding plugins/gimmicks instead of doing the actual work (writing/learning)
- The solution: strip the system down to bare essentials and move forward with what works.
- Watching many different tutorials can lead to perfectionism and a “Frankenstein” system:
-
Why do this at all? (3 major learning benefits)
- Forces slower, deeper processing
- Slower note-writing reduces “speed reading.”
- Writing forces you to dwell on ideas → deeper understanding and lasting impact.
- Provides instant feedback
- Struggling to express an idea in writing reveals gaps in understanding.
- This is contrasted with school/essay scenarios where feedback comes later (or not at all).
- Writing acts as a “feedback loop” + reflection.
- Creates connections across ideas (not isolated folders)
- Traditional subject folders can isolate ideas.
- The speaker’s metaphor: understanding deep topics requires combining multiple disciplines (e.g., their biology/physics/chemistry story).
- Zettelkasten encourages cross-linking so the “bigger picture” emerges.
- Forces slower, deeper processing
-
Notes become a reusable writing engine
- Two writer models are contrasted:
- Writer A (book-first planning)
- Research gets trapped inside drafts.
- Later work repeats research.
- Writer B (ideas-first through note network)
- Reads and captures ideas as notes.
- Later reorganizes them into a book.
- Notes can be reused across multiple projects.
- Writer A (book-first planning)
- The system is framed as building a personal writing assistant that grows stronger over time.
- Two writer models are contrasted:
Methodology / step-by-step instructions (detailed)
A) Build the system in Obsidian (overall setup stages)
- Install Obsidian
- Download/install from Obsidian’s website.
- Create a Vault
- A vault is the top-level storage folder where Obsidian keeps your notes (notes become files in that folder).
- Recommended storage
- Put the vault in cloud storage (e.g., Google Drive / OneDrive) so it’s backed up and accessible across devices.
- Use a step-by-step approach
- The speaker warns it can be confusing to understand everything at once; they present steps gradually.
B) Create folders (the system uses 6; only some are essential)
Create six folders, each with a role:
-
Rough notes (optional / light use)
- Temporary ideas, reminders, quick capture.
- Examples mentioned:
- Idea list for future research
- Daily word count tracking
-
Source material (active)
- Store “insights from anything you consume”:
- Books, videos, articles, podcasts, Twitter threads, etc.
- Can include subfolders by source type.
- Some source notes may remain “unsorted” until finalized.
- Store “insights from anything you consume”:
-
Tags (active; crucial for navigation)
- Tags are implemented as empty notes.
- Apply a tag by linking to a tag note:
- Type
[[tagname]] - If the tag note doesn’t exist, Obsidian creates it.
- Type
- Then move tag notes into the Tags folder so main notes don’t get cluttered.
-
Indexes (background/for later scaling)
- As tag size grows, convert a big tag into an index:
- Add subheadings inside the tag note
- Link the notes belonging under each subheading
- Purpose: prevent “spider web” navigation problems.
- As tag size grows, convert a big tag into an index:
-
Template (active setup, then mostly forgotten)
- Stores a template for main notes.
-
Workhorse / Main notes folder (active)
- All main (atomic) notes go here.
- Unlike folder-per-topic systems, this folder is intentionally “flat” to allow connections to emerge.
C) Adjust essential Obsidian settings
- Files and links
- Set default location for new notes to the main notes folder.
- Appearance
- Optional: choose a theme if desired.
- Hotkeys
- Configure a hotkey for inserting templates:
- Example: Ctrl+T (or Cmd+T on Mac)
- Configure a hotkey for inserting templates:
- Core plugins
- Enable templates plugin (needed for template insertion).
- Community plugins
- Optional; don’t rely on them.
- Examples used:
- “Better Word Count” (word count feature)
- “Smart Random Note” (random note generation)
- Advice: don’t add too many plugins or you’ll overcomplicate the system.
D) Create the note template (main note structure)
In Template settings, select the template folder, then create a template with sections including:
- Date/time via template variables (auto-insert)
- Status
- Tag area (for hashtags / linked tag concepts)
- Title
- Hashtags/subheadings
- “hashtag followed by space”
- More hashtags create smaller subheadings
- Reference section at the bottom
- For linking to source material and related notes
E) Capture and write notes (daily workflow)
- Create a new note
- Use Ctrl+O
- Search for a title
- Use Shift + Enter to create a new note if it doesn’t exist (avoids duplicates)
- Insert the template
- Use the template hotkey (e.g., Ctrl+T)
- The template structure is added automatically.
-
Write in two stages: “Source notes” then “Main notes”
- Source material notes
- Located in the Source material folder.
- Include:
- Title of the book/source
- Link (only if online; not needed for print)
- Page numbers and quotes (if applicable)
- Then expansion in your own words
- Emphasis: don’t fall into passive learning by only copying quotes.
- Main notes
- Created after source notes are done.
- Self-contained and independent from the source notes.
- Purpose:
- Extract the key takeaway / bigger picture
- Enable easy reuse and connection with other notes
- Source material notes
-
Use status (optional but described)
- Status levels:
# bab(early/barely developed)# child(improved, more connected)# adult(mature, well-developed)
- Optional:
#t quotefor notes that contain quotes
- Status levels:
F) Tagging rules (practical guidance)
- Avoid tags that are too vague
- Example: “self-improvement” is too broad to predict content.
- Avoid tags that are overly specific
- Otherwise you may never need them again.
- Use tags that match your interests
- Tags are for navigation and curiosity, not external categories.
- Tag reuse strategy
- Early on, you’ll create many tags.
- Later, reuse existing tags as interests stabilize.
- If you forget tags
- Search similar notes using links/hyperlinking
- Check what those notes are tagged with and reuse tags.
- How many tags
- Guideline: usually keep it below 4–5 tags
- Occasionally as low as one tag
G) Formatting and quality constraints for main notes
- Keep notes short
- Suggested cap: under 500 words
- Goal: tools for learning/writing, not long articles.
- One note = one core idea
- Avoid “mixing too much” inside one note.
- If you have multiple ideas, split into multiple notes and link them.
- Readable formatting
- Add spacing at natural breakpoints.
- Avoid huge unbroken blocks of text.
H) References section (linking)
- At the bottom of the main note, under References:
- Link to:
- Source material where the idea came from
- Other notes with similar ideas
- Link to:
- Linking process mirrors tagging:
- Use
[[...]]-style search to find related notes.
- Use
- If you can’t remember what to link:
- Check keywords in note titles
- Optionally review tag notes for linked notes
Speakers / sources featured
- Speaker / creator: Not explicitly named in the subtitles (the narrator/teacher presenting the setup and workflow).
- Primary book source referenced:
- How to Take Smart Notes by Sönke Ahrens (mentioned as “Sinin now I think that’s how you pronounce it,” i.e., the Zettelkasten author).
- Other cited book used as the example:
- Confessions of a Cartel Hitman (author not named in subtitles).
- Systems/terms referenced:
- Zettelkasten
- Second Brain (as an alternative name people use)
Rate this summary
Your feedback will help improve summaries.
Improve this summary
Reprocess with a stronger model when the summary feels incomplete or inaccurate.
Translate summary in another language
Ask questions to this video
Chat for follow-up questions, clarifications, and source-backed answers.