Appearance
Links, backlinks and mentions
Making a link
Type [[ and a picker opens, filtered as you type. Choose a page, or create the one you just named — a link to a page that does not exist yet is the most common reason to want a new page, and stopping to make it first is the thing that breaks the sentence you were writing.
The query may contain spaces, because page titles do.
Other names for a page
A page is often called one thing and talked about as another — Kubernetes and k8s. Give it an aliases property and it answers to those names too:
yaml
aliases: [k8s, kube]Typing [[k8s then finds the Kubernetes page, and the link is written over k8s — the word you were typing — rather than swapped for the title. The picker also stops offering to create a page called k8s, since one already answers to it.
aliases is an ordinary page property, so it exports as the frontmatter key Obsidian already reads, and an Obsidian vault's aliases resolve its [[links]] on import. Logseq's alias:: is read too.
Backlinks
The Links tab lists what this page points at and what points back at it. Backlinks are maintained from the block tree as it is written, not crawled later, so they are current rather than nightly.
Unlinked mentions
The other half of the graph: places that say a page's name without linking to it.
In a knowledge base most connections are never made, because people write a name and nothing joins it up. The Links tab lists those mentions, and each is one button away from becoming a real link.
A page's aliases count as its name here too, and the link is made over whichever name was written. A title needs four characters to be looked for, so a page called "Ok" does not claim every "ok"; an alias needs three, because it was declared in order to be matched — k8s, SRE. Two-letter initials are never matched: they stand for several things.
Short references
A workspace can make PROJ-123, #456 or INC-7 links to wherever it keeps those things: its issue tracker, its code host, its incident log. Write the reference as you normally would. It is drawn as a link with a dotted underline, opened in a new tab with Ctrl or ⌘ and a click (any click, on a page you can only read), and written as a link on a published site.
Nothing about the page changes. The words stay exactly as typed, so the Markdown says PROJ-123 and the timeline records nobody as having made a link. When the workspace changes where a reference goes, every page follows at once. Code and existing links are left alone: a reference written as `PROJ-123` stays text.
Which prefixes mean what is set by whoever runs the workspace, in the console under Short references: a prefix such as PROJ- and an address with <num> where the number goes, like https://tracker.example.com/browse/PROJ-<num>.
Exported links do not break
When you export, links become relative .md paths built from slugs. No identifier appears in any link target.
That is a deliberate choice with a cost — a renamed page changes its slug, and the export rewrites every link that pointed at it — and it buys the thing that matters: a folder of Markdown files where every link works in any editor, rather than a folder of files full of UUIDs that work in exactly one tool.
See also
- Block references — pointing at a block, and rendering it.
- Search — finding text rather than following a link.