Build the mental model
Obsidian is a local-first knowledge system — each note is a plain markdown file stored inside a folder on your own computer, called a vault.
The core idea is linked thinking: Note A links to Note B, Note B to Note C, and Note C can link back to Note A — three notes become a connected network. Typing `[[Note Title]]` creates a link, and Obsidian automatically tracks backlinks.
- Daily note - written each day
- Atomic note - one note per single idea
- Reference note - stores facts or quotes
- Permanent note - an idea written in your own words
Plugins Are Optional
The plugin community adds extra features, but none are required to start — plain linking and backlinks alone are enough to begin.
- Markdown
- A lightweight plain-text formatting syntax (like **bold** or [[links]]) that stays readable even without special software.
- Vault
- Obsidian's term for a folder of markdown files that make up your entire local notebook.
- Backlink
- An automatic, reverse link showing which notes point to the note you're currently viewing.
LINKED THINKING
---------------
LINKED THINKING
-----
+--------+
| NOTE A |
+--------+
^ ^
| |
v v
+--------+ +--------+
| NOTE B |<>| NOTE C |
+--------+ +--------+
Note A <-> Note B <-> Note C <-> Note A
every link also creates an automatic backlinkConnect it to a real scenario
Create a vault
Write one note per topic, following the atomic-note idea.
Link with [[brackets]]
Instead of retyping, reference related topics with `[[Note Title]]`.
Check the backlinks panel
After linking, see backlinks appear automatically.
Don't overcomplicate the folder structure — links themselves act as navigation, so a deep folder hierarchy isn't necessary.
Use plain markdown and linking for about a week before installing plugins — figure out which features you actually need first.
Don't Force Structure Too Early
If a note is hard to categorize, link it loosely for now and organize later — forcing perfect structure too early is a common reason beginners abandon their vault.
Try the working example
function buildBacklinks(notes) {
const backlinks = {};
for (const title of Object.keys(notes)) {
backlinks[title] = [];
}
const linkPattern = /\[\[([^\]]+)\]\]/g;
for (const [title, content] of Object.entries(notes)) {
let match;
while ((match = linkPattern.exec(content)) !== null) {
const target = match[1];
if (backlinks[target]) {
backlinks[target].push(title);
}
}
}
return backlinks;
}
const notes = {
"Note A": "This links to [[Note B]] about productivity.",
"Note B": "This connects back to [[Note A]] and also to [[Note C]].",
"Note C": "Referenced from [[Note B]], no outgoing links here."
};
console.log(buildBacklinks(notes));{
'Note A': [ 'Note B' ],
'Note B': [ 'Note A', 'Note C' ],
'Note C': [ 'Note B' ]
}
(Note A gets 'Note B' because Note B links to it. Note B gets two backlinks because both Note A and Note C link to it.)5-minute try-it
Write three or five plain markdown note strings containing `[[links]]` yourself and run this lesson's buildBacklinks function on them. Check the result against a backlink map you worked out by hand.
One important caution
Installing a large stack of plugins before understanding plain linking and backlinks first
Never linking notes to each other, which turns the vault into disconnected files — the exact opposite of linked thinking
Create a Vault - Obsidian Help — Productivity Systems