Obsidian knowledge management

{{whyLabel}}: Without a clear goal, your vault will become a digital graveyard of random notes.

{{howLabel}}:

• Decide if your focus is on project management (PARA), academic research (Zettelkasten), or creative writing.
• Write down three primary questions you want your system to answer (e.g., 'What did I learn about AI this month?').
• Identify your main information sources (Books, Podcasts, Web Articles).

{{doneWhenLabel}}: You have a written 'Mission Statement' for your vault in a simple text file.

{{whyLabel}}: A framework prevents 'folder fatigue' and provides a logical home for every piece of information.

{{howLabel}}:

• Use the PARA Method (Projects, Areas, Resources, Archives) if you are action-oriented.
• Use the Zettelkasten Method (Inbox, Literature, Permanent) if you focus on long-term learning and connecting ideas.
• Adopt a 'Folder-Light' approach, relying on links and tags rather than deep hierarchies.

{{doneWhenLabel}}: A decision is made between PARA, Zettelkasten, or a hybrid model.

{{whyLabel}}: Analyzing existing workflows prevents you from carrying over bad habits into the new system.

{{howLabel}}:

• List where your notes currently live (Apple Notes, Notion, Paper).
• Identify the biggest pain point (e.g., 'I can't find anything' or 'I never revisit my notes').
• Commit to a 'Capture' method that takes less than 10 seconds.

{{doneWhenLabel}}: You have a list of 3 friction points to solve with Obsidian.

{{whyLabel}}: Obsidian stores files locally in Markdown, ensuring your data remains yours forever.

{{howLabel}}:

• Download the installer from the official website.
• Create a new folder on your hard drive named 'MyKnowledgeVault'.
• Open this folder as a 'Vault' in Obsidian.

{{doneWhenLabel}}: Obsidian is open and showing an empty vault.

{{whyLabel}}: Proper settings ensure a distraction-free writing environment and consistent file linking.

{{howLabel}}:

• Enable 'Properties' in the editor view for metadata management.
• Set 'Default location for new notes' to a specific 'Inbox' folder.
• Enable 'WikiLinks' format for easier internal linking (e.g., [[Note Name]]).

{{doneWhenLabel}}: Settings are adjusted to support a linked-note workflow.

{{whyLabel}}: Folders should be broad categories, while links handle the specific connections.

{{howLabel}}:

• Create an '00_Inbox' folder for unprocessed notes.
• Create a '10_Sources' folder for literature and meeting notes.
• Create a '20_Notes' folder for your own processed thoughts.
• Create an '80_Templates' folder for automation.

{{doneWhenLabel}}: Your sidebar shows a clean, top-level folder structure.

{{whyLabel}}: Automation via templates saves time and ensures consistent metadata (Properties) across notes.

{{howLabel}}:

• Go to Settings > Community Plugins > Browse.
• Search for and install 'Templater'.
• Enable the plugin and set the 'Template folder location' to your '80_Templates' folder.

{{doneWhenLabel}}: Templater is active and pointed to your templates folder.

{{whyLabel}}: Dataview turns your vault into a database, allowing you to create automated lists and tables.

{{howLabel}}:

• Install 'Dataview' from the Community Plugins gallery.
• Enable 'JavaScript Queries' in the Dataview settings for advanced functionality.
• This will later allow you to see 'All notes tagged with #research' automatically.

{{doneWhenLabel}}: Dataview is installed and enabled.

{{whyLabel}}: Literature notes capture external information while keeping it separate from your own original ideas.

{{howLabel}}:

• Create a new file in '80_Templates' called 'T_LiteratureNote'.
• Add Properties: 'Author', 'Source_URL', 'Topic', 'Date_Captured'.
• Add a section for 'Key Takeaways' and 'Quotes'.

{{doneWhenLabel}}: A reusable template for external content exists.

{{whyLabel}}: Permanent notes are 'atomic'—one idea per note—which makes them easier to link and reuse.

{{howLabel}}:

• Create 'T_PermanentNote' in your templates folder.
• Include a 'Links' property to connect it to broader topics.
• Add a 'References' section at the bottom to link back to the original Literature Note.

{{doneWhenLabel}}: A template for your own synthesized ideas is ready.

{{whyLabel}}: Over-tagging leads to clutter; linking creates a neural network of knowledge.

{{howLabel}}:

• Use Tags for status (e.g., #to-process, #draft) or high-level categories.
• Use Links ([[Note]]) for concepts and relationships.
• Avoid using tags for topics that could be their own notes.

{{doneWhenLabel}}: You have a 1-page 'Style Guide' note in your vault.

{{whyLabel}}: Testing with real data reveals if your templates and folders actually work in practice.

{{howLabel}}:

• Pick 5 articles or book highlights you've recently read.
• Use your 'Literature Note' template to summarize them.
• Extract at least one 'Permanent Note' (original thought) from each.

{{doneWhenLabel}}: Your vault contains at least 10 interconnected notes.

{{whyLabel}}: Linking is the core of a PKM; it allows for the emergence of new insights.

{{howLabel}}:

• Open a Permanent Note.
• Find a concept that relates to another note.
• Type '[[' and select the related note to create a bidirectional link.

{{doneWhenLabel}}: You can navigate between three notes without using the file explorer.

{{whyLabel}}: A system only works if it survives daily life.

{{howLabel}}:

• Use Obsidian exclusively for all new notes for one week.
• Do not change the structure during this week; just take notes.
• Note down every time you feel 'stuck' or don't know where to put something.

{{doneWhenLabel}}: You have a list of 'Friction Points' after 7 days of active use.

{{whyLabel}}: MOCs act as entry points or 'hubs' for complex topics, preventing you from getting lost in the graph.

{{howLabel}}:

• Create a note named 'MOC [Your Topic]'.
• Use Dataview or manual links to list all notes related to this topic.
• Organize the links logically (e.g., by sub-topic or importance).

{{doneWhenLabel}}: You have one central hub note that organizes at least 5 related notes.

{{whyLabel}}: Regular maintenance prevents the 'Inbox' from overflowing and ensures links are maintained.

{{howLabel}}:

• Set a recurring calendar event for 30 minutes every Sunday.
• Empty the '00_Inbox' by processing notes into 'Sources' or 'Permanent'.
• Check the 'Graph View' for isolated notes (orphans) and link them.

{{doneWhenLabel}}: A recurring 'Review' task is added to your calendar.

{{whyLabel}}: Local files are vulnerable to hardware failure or accidental deletion.

{{howLabel}}:

• Use a generic cloud sync service (like a private cloud folder) to keep files synced across devices.
• Alternatively, use a Git-based backup (e.g., 'Obsidian Git' plugin) for version control.
• Ensure the backup is automated and runs at least daily.

{{doneWhenLabel}}: Your vault is synced to at least one external location.