How I Take SMART Notes in Obsidian MD 🔗 **Source:** [How I Take SMART Notes in Obsidian MD](https://www.youtube.com/watch?v=pmcAjMf5JoE) > [!note]+ Document Notes > tags: [obsidian, note-taking, zettelkasten] > author: John Maverick > source: YouTube > reference: https://www.youtube.com/watch?v=pmcAjMf5JoE > date created: 2024-12-19 14:30 > > # 🏷️ Title: How I Take SMART Notes in Obsidian MD > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Set up four main note types (fleeting, literature, permanent, project) — core system architecture/00:00 #obsidian - [H2] Implement Evergreen note status system — note development tracking/03:45 #workflow - [H3] Create inbox system with workbench and reminders — capture and organize workflow/08:30 #productivity ## 🧭 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 - [How I Take SMART Notes in Obsidian MD](https://www.youtube.com/watch?v=pmcAjMf5JoE) - [Andy Matuschak's Evergreen Notes](https://notes.andymatuschak.org/Evergreen_notes) ## 📝 Summary - John Maverick demonstrates a comprehensive Obsidian note-taking system based on the four main types from "How to Take Smart Notes" - System includes fleeting notes for quick capture, literature notes for consuming content, permanent notes for developed ideas, and project notes for planning - Uses Evergreen note status system, inbox workflows, and various plugins (Templater, Reminders, Dataview) to automate and organize - Key benefit is easy information recall and connection-making compared to traditional hierarchical systems - Emphasizes flexibility over rigid folder structures ## 📖 Main Content The video presents a structured approach to implementing Niklas Luhmann's Zettelkasten method in Obsidian, adapted from the popular "How to Take Smart Notes" book. The system revolves around four core note types that serve different purposes in knowledge management. Fleeting notes capture temporary ideas and are categorized as either informational or actionable. The author uses prefixes and templates to automate note creation, with personal ideas getting reflection prompts and objective ideas using standard templates. An Evergreen note status system tracks development stages from "seedling" (bare bones) to "evergreen" (fully developed). Literature notes track consumption of various inputs like books, articles, and podcasts, with different templates for different media types. The system includes progress tracking, highlights import from Kindle, and organization through Dataview queries and Kanban boards. The organization structure centers around multiple inbox systems: a workbench for notes needing development, reminders for vault-related tasks, external tools like Pocket for content capture, and project hubs for tracking initiatives across different timeframes. ## 🗒️ Notes #### ⏱️ [00:00](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=0) — [H1] Four main note types from Smart Notes book - Key idea: System based on fleeting, literature, permanent, and project notes - Evidence: "In the book there's four main kinds of notes discussed fleeting notes literature notes permanent notes and project notes" #### ⏱️ [01:15](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=75) — [H2] Fleeting notes for temporary idea capture - Key idea: Categorize fleeting ideas as informational or actionable with quick capture workflow - Evidence: "Fleeting ideas are temporary reminders of information and i categorize these notes i take for these ideas as either informational or actionable" #### ⏱️ [02:30](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=150) — [H2] Personal idea prefix system with templates - Key idea: Use equal sign prefix for personal ideas to trigger reflection templates - Evidence: "If it's a personal idea i prefixed the title with an equal sign to automatically import a template with extra prompts to spark reflection and elaboration" #### ⏱️ [03:45](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=225) — [H3] Evergreen note status system for development tracking - Key idea: Track note development with seedling, herb, sun, and evergreen status tags - Evidence: "I set the tag to a seedling if it's a bare bones idea a herb if i could still use some expansion a sun if it's developed but is lacking connections to other ideas or an evergreen note if it's finally finished" #### ⏱️ [05:15](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=315) — [H3] Tags vs links distinction for organization - Key idea: Tags for general topics, links for hierarchical relations like file structure - Evidence: "Tags are for general topics it's related to while links are for its hierarchical relations to bigger ideas like a traditional file structure" #### ⏱️ [06:00](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=360) — [H2] Reminders plugin for actionable items - Key idea: Use reminders plugin for vault-related tasks with date syntax and notifications - Evidence: "I've recently downloaded a reminders plugin to help me easily see some things i need to keep note of" #### ⏱️ [07:30](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=450) — [H2] Literature notes with different templates by media type - Key idea: Different templates for books, articles, podcasts based on consumption patterns - Evidence: "Books shouldn't really be consumed in the same way as short articles or podcasts so my prompts and fields are a bit different for the different templates" #### ⏱️ [08:30](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=510) — [H1] Multiple inbox system for organization - Key idea: Separate inboxes for seedling notes, inputs, vault tasks, and general tasks - Evidence: "I have different inboxes for seedling notes inputs i need to consume things to act upon within my vault and tasks" #### ⏱️ [09:45](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=585) — [H3] Workbench plugin for note development tracking - Key idea: Workbench queries search for notes needing development and links current note for reference - Evidence: "I use a workbench note to see what notes i need to work on it has queries to search for seedling herb or sun notes that may need future development" #### ⏱️ [10:30](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=630) — [H3] External tools integration for content capture - Key idea: Use Pocket (switching to Raindrop.io) for saving content with folder organization - Evidence: "I usually use pocket to easily save any things i want to consume but i'm planning on switching to raindrop io as it has folders you can do some organizing with" #### ⏱️ [11:15](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=675) — [H3] Dataview kanban lists for literature tracking - Key idea: Main input note with dataview queries creating kanban boards for status tracking - Evidence: "To keep track of all my literature notes i use kanban lists using dataview queries to keep track of everything in the note" #### ⏱️ [12:00](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=720) — [H3] Kindle highlights plugin integration - Key idea: Import Kindle selections automatically, exploring Caliber for more annotation depth - Evidence: "I've been reading on my kindle so i use the kindle highlights plugin to import all my selections into obsidian which are all then stored in a single note" #### ⏱️ [13:30](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=810) — [H2] Project hub with time-based organization - Key idea: Project notes organized by timeframes with current project overview - Evidence: "I have a project hub for seeing my current projects which are then sorted by their time frames" #### ⏱️ [14:45](https://www.youtube.com/watch?v=pmcAjMf5JoE&t=885) — [H1] Benefits of interconnected system over traditional methods - Key idea: Easy information recall without mental retrieval, quick content discovery for writing - Evidence: "The main benefit i've noticed in comparison to other note-taking systems is how easy it is to recall and access information by taking note of virtually all your ideas and forming connections" ## 📚 References - [How I Take SMART Notes in Obsidian MD](https://www.youtube.com/watch?v=pmcAjMf5JoE) - [Templater Plugin](https://github.com/SilentVoid13/Templater) - [Dataview Plugin](https://github.com/blacksmithgu/obsidian-dataview) - [Brian Jenks Workflow](https://www.youtube.com/channel/UCfhSB16X9MXhzSFe_H7XbHg) ## 🗣️ Paraphrase - The system organizes notes into four types: fleeting (quick captures), literature (content consumption), permanent (developed ideas), and project (planning) with automated templates and status tracking - Organization relies on multiple inbox systems including a workbench for note development, reminders for tasks, and external tools for content capture, all integrated through plugins - The key advantage is creating an interconnected knowledge network that makes information retrieval effortless compared to traditional hierarchical folder systems ## 📰 Newsletter **Transform Your Note-Taking with This Obsidian Workflow** Looking to level up your knowledge management? John Maverick shares a comprehensive Obsidian system that turns scattered thoughts into an interconnected knowledge base. The approach uses four note types from "How to Take Smart Notes": fleeting notes for quick captures, literature notes for content consumption, permanent notes for developed ideas, and project notes for planning. What makes this special is the automation - templates that trigger based on prefixes, status systems that track note development, and plugins that handle the heavy lifting. Key tools include the Templater plugin for automation, Dataview for dynamic organization, and the Reminders plugin for task management. The real game-changer? Multiple inbox systems that capture everything from random thoughts to reading lists, all organized through queries and kanban boards. Ready to try it? Start with the basic four note types and gradually add the plugin ecosystem. Your future self will thank you when finding that perfect piece of information takes seconds instead of hours. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### Community - Maintainers: Create note-taking workflow documentation for project contributors - Contributors: Establish shared templates for documentation and issue tracking - Sponsors: Implement knowledge management system for tracking project impacts #### WordPress - Documentation: Develop Obsidian-based workflow for DevHub content creation - Community: Create note-taking guides for WordCamp organizers and speakers - Training: Build lesson plans using interconnected note structure ## 🧪 Hypotheses - Automated template systems reduce cognitive load in note creation compared to manual formatting - Status-based note development (seedling→evergreen) improves knowledge retention over unstructured approaches - Multiple inbox systems prevent information loss better than single capture points - Plugin-based automation increases long-term system adoption rates ### 📊 Methodology - A/B testing manual vs automated template insertion measuring creation speed and consistency - Longitudinal study tracking note development progression through status stages - Comparative analysis of single vs multiple inbox capture rates and processing efficiency ### ❓ Questions - How does plugin complexity affect long-term system maintenance and user adoption? - What's the optimal balance between automation and manual control in note-taking workflows? - How do interconnected note systems compare to traditional hierarchical structures for creative work? ### 🔮 Future Research - Integration patterns between Obsidian workflows and team collaboration tools - Effectiveness of visual status systems (seedling→evergreen) across different learning styles - Automated knowledge graph analysis for identifying gaps in personal knowledge systems ### 💡 Implications - Practice: Structured workflows can transform chaotic information capture into systematic knowledge building - Education: Template-driven approaches could standardize student note-taking and improve retention - Funding: Investment in personal knowledge management tools shows measurable productivity returns - Security: Centralized note systems require backup strategies and data portability considerations ### 🧠 Learning Styles Assessment Reading level estimate: 8th grade #### 👀 Visual learners - Present: Status progression diagrams, workflow screenshots, plugin interface examples - Improve: Note connection visualizations, template structure diagrams, system architecture overviews #### 🔊 Aural learners - Present: Full video walkthrough with verbal explanations and plugin demonstrations - Improve: Audio-only summary of workflow steps, podcast-style discussion of benefits #### 🗣️ Verbal learners - Present: Clear terminology definitions, step-by-step explanations, naming conventions - Improve: Analogies comparing to traditional filing systems, story-driven examples #### 🧩 Kinesthetic learners - Present: Hands-on plugin setup, template creation exercises, actual note demonstrations - Improve: Practice challenges, workflow checklists, interactive setup guides #### 🧠 Logical learners - Present: Clear workflow sequences, plugin relationships, systematic organization - Improve: Decision trees for note type selection, performance metrics, efficiency comparisons #### 🧑‍🤝‍🧑 Social learners - Present: References to community workflows, shared template systems - Improve: Collaborative note-taking examples, team workflow adaptations #### 🧘‍♀️ Solitary learners - Present: Personal reflection prompts, individual workflow customization - Improve: Self-assessment guides for system effectiveness, private journaling integration #### 🌿 Naturalistic learners - Present: Organic note development metaphors (seedling→evergreen) - Improve: Ecosystem analogies for note interconnections, growth-based thinking ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive plugin names - Improve: Alt text for workflow diagrams, ARIA labels for interface elements #### Keyboard navigation - Present: Obsidian's built-in keyboard shortcuts, quick switcher access - Improve: Custom hotkey documentation, keyboard-only workflow paths #### Contrast and readability - Present: Standard video quality, clear interface screenshots - Improve: High-contrast theme examples, font size recommendations #### Text resizing and reflow - Present: Responsive Obsidian interface, scalable note content - Improve: Mobile workflow adaptations, tablet-specific guidance #### Media and captions - Present: Full transcript available for video content - Improve: Chapter markers for video sections, downloadable workflow summaries #### Forms and interactions - Present: Clear plugin installation steps, template setup instructions - Improve: Error handling documentation, troubleshooting guides ### 🌍 DEIB Assessment #### Cultural breadth - Present: Universal knowledge management concepts, platform-agnostic principles - Improve: Multi-language note-taking examples, international workflow variations #### Inclusive language - Present: Gender-neutral terminology, accessible technical explanations - Improve: Plain-language alternatives for technical terms, glossary of concepts #### Neurodiversity support - Present: Multiple organization systems, flexible workflow structures - Improve: ADHD-friendly capture methods, autism-friendly systematic approaches #### Representation - Present: Individual workflow focus, personal productivity emphasis - <!-- deep-read:sections end -->