Note Name
Note name is how you reference other notes using wiki links and how you establish note hierarchies.
Note name is hierarchy
Note names establish the hierarchy of notes, with dot (.) as the delimiter between a parent and child note.
For example, consider these files:
workspace/.thorg
workspace/vault-1/grandparent.parent.child.md
workspace/vault-1/grandparent.parent.md
File grandparent.parent.child.md has the note name grandparent.parent.child and its parent note name is grandparent.parent.
Note linking
You have a note file some.note-1.md
Regular wiki link
To reference it as a link from your current note, use the note name:
[[some.note-1]]
Transclusion (Embedding Notes)
Transclusion lets you pull the content of one note directly into another. Instead of just linking to a note, the referenced note's content appears inline—as if you'd copy-pasted it, but it stays in sync with the source.
Example
Say you have a note called some.note-1.md with useful content you want to reuse.
To embed it in another note, use the ![[...]] syntax:
![[some.note-1]]
When you view the note, the full content of some.note-1 will appear right there.
Linking vs. Transclusion
| Syntax | What it does |
|---|---|
[[some.note-1]] | Creates a link to the note (click to navigate) |
![[some.note-1]] | Embeds the note's content inline |
Think of the ! as "inject this here."
Further notes
Hierarchies and Cross vault Hierarchy support
Note names are most important for hierarchy support and cross vault hierarchies.
For example let's say you have public-vault with notes
grandparent.parent.child-1.md
grandparent.parent.child-2.md
And you want to attach a personal note to this hierarchy in a personal-vault, you can do so as follows:
grandparent.parent.private-child-1.md
and grandparent.parent.private-child-1.md will become a sibling of grandparent.parent.child-1 and grandparent.parent.child-2.
Children
Backlinks