My simple note-taking setup | Zettelkasten in Obsidian | Step-by-step guide 🔗 **Source:** [My simple note-taking setup | Zettelkasten in Obsidian | Step-by-step guide](https://www.youtube.com/watch?v=E6ySG7xYgjY) > [!note]+ Document Notes > tags: [zettelkasten, obsidian, note-taking] > author: Artem Kirsanov > source: YouTube > reference: https://www.youtube.com/watch?v=E6ySG7xYgjY > date created: 2024-12-19 09:15 > > # 🏷️ Title: My simple note-taking setup | Zettelkasten in Obsidian | Step-by-step guide > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Set up four core folders in Obsidian vault — 02:29 #setup - [H2] Configure templates for atomic notes and maps of content — 06:32 #templates - [H3] Start simple and let structure emerge organically — 10:45 #philosophy ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [My simple note-taking setup | Zettelkasten in Obsidian | Step-by-step guide](https://www.youtube.com/watch?v=E6ySG7xYgjY) ## 📝 Summary - Artem Kirsanov demonstrates a simplified Zettelkasten implementation in Obsidian using just four folders and minimal plugins - The system emphasizes starting simple rather than getting lost in complex setups with dozens of tags, folders, and plugins - Key components include atomic idea notes, emergent structure through linking, and maps of content that develop naturally - The approach prioritizes capturing and connecting ideas over perfecting organizational systems - Bottom line: Complexity doesn't improve benefits; simple systems that encourage consistent note-taking and linking are more effective ## 📖 Main Content The video addresses the common overwhelm newcomers face when exploring Zettelkasten note-taking systems online. Many tutorials present overly complex setups with numerous plugins, tags, and organizational schemes that can distract from the core purpose: capturing ideas and finding connections. Artem presents a minimalist approach using Obsidian with just four folders (Zettelkasten, Reference Notes, Files, Templates) and two main plugins (Sliding Panes and Admonition). The system relies on Obsidian's linking capabilities to create emergent structure rather than imposing rigid hierarchies upfront. The core principle follows Niklas Luhmann's original paper-based system: put everything in one place and let structure emerge through interconnections. Ghost nodes (links to non-existent notes) serve as tags initially, eventually becoming Maps of Content (MOCs) when clusters of related notes develop around them. ## 🗒️ Notes #### ⏱️ [00:00](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=0) — [H1] The complexity trap in note-taking systems - Key idea: Complex setups with many plugins and tags often decrease rather than increase system effectiveness - Evidence: "Benefits of the system don't increase with its complexity, in fact most often quite the opposite" #### ⏱️ [01:15](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=75) — [H2] Tinkering vs. actual note-taking - Key idea: Spending time on system organization can distract from the fundamental purpose of absorbing and connecting ideas - Evidence: "Tinkering with tags and thinking how to best structure your notes can distract you from what actually matters" #### ⏱️ [01:45](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=105) — [H3] Original Zettelkasten was paper-based - Key idea: Luhmann's system worked effectively with simple paper cards, proving digital complexity isn't necessary - Evidence: "The original zettelkasten system pioneered by Nicolas Luhmann was built using paper cards" #### ⏱️ [02:29](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=149) — [H1] Four-folder system structure - Key idea: Simple folder organization with Zettelkasten, Reference Notes, Files, and Templates covers all needs - Evidence: "My quite simple and elegant solution... consists of just four folders and two main tags" #### ⏱️ [03:12](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=192) — [H2] Obsidian vault as local file system - Key idea: Understanding that Obsidian wraps local markdown files helps users avoid vendor lock-in - Evidence: "Each node is actually just a single markdown document on your hard drive which can be opened and edited in any software" #### ⏱️ [04:15](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=255) — [H2] Single Zettelkasten folder approach - Key idea: All atomic ideas go in one folder regardless of topic, allowing structure to emerge through links - Evidence: "You don't impose an artificial structure on the system... instead you put everything into one place" #### ⏱️ [05:20](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=320) — [H3] Essential Obsidian configuration - Key idea: Default locations for notes and attachments should be set to maintain organization automatically - Evidence: Settings configuration for folder defaults prevents scattered files #### ⏱️ [06:32](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=392) — [H2] Template system setup - Key idea: Templates save time and ensure consistency in note creation without adding complexity - Evidence: "Templates is an amazing function that lets you save time and effort when creating a new note" #### ⏱️ [07:45](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=465) — [H3] Plugin minimalism warning - Key idea: Too many plugins can become procrastination disguised as productivity - Evidence: "Be careful not to get lost in this rabbit hole... it's just another form of procrastination" #### ⏱️ [08:30](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=510) — [H2] Core idea template structure - Key idea: Standardized template with status, tags, title, and references maintains consistency - Evidence: Template includes date/time, classification fields, and source tracking #### ⏱️ [09:15](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=555) — [H2] Ghost nodes as emergent tags - Key idea: Links to non-existent notes serve as tags initially, becoming actual notes when clusters form - Evidence: "Single nodes can function as tags and these non-existent ghost nodes will be displayed on the graph view" #### ⏱️ [10:12](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=612) — [H1] Maps of Content emergence - Key idea: When many notes cluster around a topic, create a Map of Content to organize that domain - Evidence: "Eventually in the graph view you will see the emerging structure... this is the next level of organization" #### ⏱️ [10:45](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=645) — [H1] Dynamic system evolution - Key idea: The system should adapt and change as your knowledge base grows rather than remaining static - Evidence: "The system is dynamic new mocks appear some get split some merge don't be afraid to change the architecture" #### ⏱️ [11:30](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=690) — [H2] Personal adaptation advice - Key idea: Don't completely restructure working systems; only adapt elements that resonate - Evidence: "If you have a system that's already working for you... don't go and spend a week completely restructuring your vault" #### ⏱️ [12:15](https://www.youtube.com/watch?v=E6ySG7xYgjY?t=735) — [H3] Start simple principle - Key idea: Begin with basic structure and let the system tell you what it needs as it matures - Evidence: "Start simple go with the flow and then adjust your system one step at a time" ## 📚 References - [My simple note-taking setup | Zettelkasten in Obsidian | Step-by-step guide](https://www.youtube.com/watch?v=E6ySG7xYgjY) - [Obsidian](https://obsidian.md/) - [Niklas Luhmann's Zettelkasten](https://niklas-luhmann-archiv.de/) ## 🗣️ Paraphrase - Complex note-taking systems with many plugins and organizational layers often hinder rather than help the core purpose of capturing and connecting ideas - A simple four-folder Obsidian setup (Zettelkasten, Reference Notes, Files, Templates) with minimal plugins can effectively implement Zettelkasten principles - Structure should emerge organically through linking rather than being imposed upfront, with Maps of Content developing naturally around clustered topics ## 📰 Newsletter **Simple Zettelkasten: Less Complexity, More Connection** Feeling overwhelmed by complex note-taking setups? This streamlined Obsidian approach might be exactly what you need. The key insight: system complexity rarely correlates with effectiveness. Instead of managing dozens of plugins and tags, focus on consistently capturing ideas and linking them together. A simple four-folder structure with templates and emergent organization through linking can be more powerful than elaborate hierarchies. This approach mirrors how we naturally build knowledge - starting with individual insights and gradually seeing patterns emerge. Your digital notes can work the same way. **Getting Started:** - Set up four folders: notes, references, files, templates - Use ghost links as tags that become real notes when needed - Let Maps of Content emerge around topic clusters Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### DevRel - Developer education: Create workshop on knowledge management systems for developer learning - Documentation: Apply emergent structure principles to API documentation organization - Community management: Use simple tagging systems rather than complex categorization for forum topics #### OSPO - Policy & Governance: Document decision-making processes using linked atomic decisions rather than monolithic policies - Knowledge Management: Implement lightweight knowledge base using similar linking principles - Community Engagement: Track project relationships through emergent mapping rather than rigid hierarchies #### Community - Contributors: Create simple onboarding templates that evolve based on actual contributor paths - Knowledge Sharing: Implement community wiki using emergent structure principles #### WordPress - Documentation: Apply atomic note principles to DevHub organization - small, linked topics rather than monolithic guides - Training: Develop lesson plan templates that allow for emergent curriculum development - Support: Use linking between related support topics instead of rigid category hierarchies ## 🧪 Hypotheses - Simple organizational systems with fewer rules lead to more consistent note-taking behavior than complex systems - Emergent structure through linking creates more useful knowledge organization than predetermined hierarchies - Template-based consistency reduces cognitive load while maintaining flexibility in knowledge capture - Visual feedback through graph views motivates continued linking and knowledge development ### 📊 Methodology - A/B test simple vs. complex note-taking system adoption rates among new users - Track linking behavior patterns between template-based and freeform note creation - Measure knowledge retrieval effectiveness in emergent vs. hierarchical organization systems ### ❓ Questions - How do we balance structure with flexibility in evolving knowledge systems? - What minimal features are essential for effective digital knowledge management? - How can we design systems that encourage linking and connection-making? ### 🔮 Future Research - Comparative study of note-taking system complexity vs. long-term usage patterns - Analysis of emergent topic clusters in community knowledge bases - Investigation of template standardization effects on knowledge quality ### 💡 Implications - Practice: Prioritize simple, consistent systems over complex organizational schemes - Education: Focus on teaching linking and connection skills rather than categorization - Tool Design: Build tools that encourage emergence rather than imposing structure - Knowledge Management: Allow organizational systems to evolve with content rather than remain static ### 🧠 Learning Styles Assessment Reading level estimate: 10th grade #### 👀 Visual learners - Present: Graph view demonstrations, folder structure diagrams, template examples - Improve: More visual comparisons between simple and complex system layouts #### 🔊 Aural learners - Present: Narrated video walkthrough with clear explanations - Improve: Audio summary of key principles and setup steps #### 🗣️ Verbal learners - Present: Clear definitions of terms like "ghost nodes" and "maps of content" - Improve: More analogies comparing digital to physical organization systems #### 🧩 Kinesthetic learners - Present: Step-by-step setup demonstration, hands-on template creation - Improve: Interactive checklist for system implementation #### 🧠 Logical learners - Present: Clear progression from simple to complex, cause-effect reasoning - Improve: Decision trees for when to create maps of content #### 🧑‍🤝‍🧑 Social learners - Present: Community terminology and shared practices - Improve: Examples of collaborative knowledge building #### 🧘‍♀️ Solitary learners - Present: Personal knowledge management focus, individual workflow - Improve: Self-assessment questions for system effectiveness #### 🌿 Naturalistic learners - Present: Organic emergence metaphors, natural structure development - Improve: More ecological analogies for knowledge system evolution ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive video narration - Improve: Transcript with proper heading markup for navigation #### Keyboard navigation - Present: Video demonstrates keyboard shortcuts for Obsidian - Improve: Complete keyboard shortcut reference list #### Contrast and readability - Present: Clear visual demonstrations in video - Improve: High-contrast screenshots for better visibility #### Text resizing and reflow - Present: Video content scales appropriately - Improve: Responsive text-based summary alongside video #### Media and captions - Present: Clear narration throughout - Improve: Closed captions with technical term clarification #### Forms and interactions - Present: Clear software setup instructions - Improve: Alternative text descriptions for interface elements ### 🌍 DEIB Assessment #### Cultural breadth - Present: Universal note-taking challenges addressed - Improve: Examples from different academic and professional contexts #### Inclusive language - Present: Gender-neutral language throughout - Improve: Define technical jargon more consistently #### Neurodiversity support - Present: Chunked information, consistent template structure - Improve: More explicit organization of sequential steps #### Representation - Present: Single presenter limits representation - Improve: Examples from diverse knowledge domains and use cases #### Psychological safety - Present: Encouraging tone about adapting existing systems - Improve: More explicit validation of different organizational preferences ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Clear progression from complexity problems to simple solutions - Inductive strength: Uses Luhmann's historical success as evidence for approach - Causal reasoning: Links system complexity to reduced effectiveness through distraction - Analogical strength: Paper card system analogy supports digital minimalism argument #### Fallacies - Appeal to tradition: Using Luhmann's paper system to justify digital approach may not account for digital-specific benefits - False dichotomy: Presents complex vs. simple as only two options, missing middle-ground approaches #### Tone of voice - Overall tone: Encouraging and practical, with personal experience to support recommendations ### 🛡️ DARVO Analysis - Deny: <!-- deep-read:sections end -->