Obsidian for Knowledge Management
A hands-on course that takes you from a folder of disconnected notes to a living knowledge base in Obsidian. You will master Markdown notes stored as plain files, link ideas with the [[wikilink]] and backlink system, read the graph view, automate daily notes and templates, and adopt a capture-to-connect workflow drawn from PARA and Zettelkasten. You leave with a working vault, a template set, and a daily routine you can sustain.
For students, researchers, writers, consultants, and lifelong learners who take a lot of notes and want a free, future-proof system that connects ideas instead of burying them.
Course content
Workbook & downloads
Put the course into practice — a printable workbook plus editable templates you can fill in and reuse.
Preview the workbook
Getting Started with Obsidian and Your First Vault
- Download and install Obsidian from obsidian.md
- Create one main vault named durably (Brain or Knowledge, not Test)
- Place the vault in a folder that syncs or backs up (Dropbox, iCloud, or Git)
- Create top-level folders: 00 Inbox, 10 Notes, 20 Daily, 90 Attachments
- In Settings, Files and links, set the default attachment folder to 90 Attachments
- Create your first note with Ctrl or Cmd plus N and give it a real title
- Pin the Command Palette shortcut Ctrl or Cmd plus P to memory
- Write an H2 heading with three bullet points, plus one bold word and one italic word
- Add three checkbox tasks using - [ ] and tick one
- Write a one-line quote using the greater-than sign
- Add a wikilink to a note that does not exist yet, then click it to create it
- Number of times you used Quick Switcher (Ctrl or Cmd plus O)
- A phrase you found with Global Search (Ctrl or Cmd plus Shift plus F)
- One command you ran from the Command Palette you did not know existed
- Number of times you opened a note in split view (Ctrl or Cmd plus click)
- One shortcut you want to assign or rebind to fit your hands
Linking Ideas: Wikilinks, Backlinks, and the Graph
- Identify three distinct ideas buried in the source note
- Create three notes whose titles are claims, not topics (e.g. Short feedback loops reduce rework)
- Link the three notes to each other where the ideas genuinely relate
- Open one of them and confirm the Backlinks pane now shows the others
- Note title being audited
- Number of backlinks shown in the Backlinks pane
- Number of outgoing links in the Outgoing Links pane
- Unlinked mentions found, and how many you converted to real links
- One block reference you could create to cite a specific paragraph
- The MOC or Home note this should be linked from (or none yet)
- Open the global graph and identify at least two orphan notes
- Connect or delete each orphan you found
- Add a filter to hide attachments, e.g. -path:90 Attachments
- Create a colored group for tag:#moc so maps stand out
- Open a Local Graph beside an active note and set depth to 1 or 2
- Pin the local graph in a side pane for your next writing session
Automating with Daily Notes and Templates
- Enable the Daily notes core plugin and set date format YYYY-MM-DD
- Point new daily notes at the 20 Daily folder
- Assign a hotkey to Open today's daily note
- Enable the Templates core plugin and create a 99 Templates folder
- Build at least a Meeting and a Permanent note template
- Install and enable the Templater community plugin
- Acknowledge the third-party plugin safety warning knowingly
- Note type this template is for (meeting, book, project, person)
- The four to six headings the template should contain
- Which heading uses checkboxes for follow-ups
- A Related line listing what kinds of notes it should link to
- Whether a date token in double curly braces is needed, and where
- One Templater prompt you want (e.g. ask for a title and rename the file)
- For one day, dump every stray thought and task into today's daily note only
- The next day, reread it and mark which items are keepers
- Promote one keeper into a permanent atomic note in 10 Notes, linked back to the source day
- Leave the non-keepers in the log and confirm search can still find them
Organizing for Retrieval: PARA, MOCs, and Zettelkasten
- Projects — efforts with a deadline and an outcome (list 3 to 5)
- Areas — ongoing responsibilities with no end date (list 3 to 5)
- Resources — topics of interest you collect on (list 3 to 5)
- Archive — finished or inactive items to move out of the way
- One note currently in the wrong bucket and where it should go
- Name a topic you now have at least five notes about
- Create a note titled [Topic] MOC, tag it #moc, and add grouping headings (Core ideas, Techniques, Open questions)
- Link the relevant notes under each heading
- Link this MOC from a single Home note so it is two clicks from anywhere
- Open the graph and link or delete every orphan note you find
- Reread the week's daily notes and promote keepers to permanent notes
- Update active project MOCs with any new notes
- Move finished projects and stale items into Archive
- Empty 00 Inbox to zero so capture stays trustworthy
- Write one open question to pull on next week
- Capture a fleeting note from something you read today, in your daily note
- Write a literature note: the source's idea in your own words, plus a citation
- Distill one durable insight into a permanent atomic note and link it to two or three related notes
- Add it to the relevant MOC so it is reachable, not orphaned
Your Action Plan
- Install Obsidian and create one main vault with folders 00 Inbox, 10 Notes, 20 Daily, and 90 Attachments
- Learn the four key shortcuts: Command Palette, Quick Switcher, Global Search, and toggle edit/read
- Convert one messy note into three atomic notes whose titles are claims, and link them together
- Open the backlinks and local graph panes daily so connections surface while you write
- Enable Daily Notes and assign a hotkey so capture is always one keystroke away
- Build a 99 Templates folder with a Meeting template and a Permanent note template
- Install Templater and set up one prompt-and-rename template so notes file themselves
- Sort your commitments into PARA and build one Map of Content linked from a Home note
- Adopt the capture-process-connect-retrieve loop and promote keepers out of daily notes
- Run a 15 to 30 minute weekly review to clear orphans, update MOCs, and empty the inbox to zero
Pairs well with
Courses members commonly take alongside this one.