Skip to content

3 min read

Wikilinks

Summary

Wikilinks are the double-bracket Markdown extension (two open-brackets, a slug, two close-brackets) used throughout this wiki to cross-reference other pages; the wiki resolves them at build time to relative links inside Wiki/ or Wiki/sources/ [source: commons-library]. Wikilinks were originally an Obsidian convention and are now the dominant linking syntax in personal-knowledge and community-wiki tooling.

Body

A wikilink takes the form of double-bracketed slugs. The wiki treats the slug minus .md as the target file in Wiki/ or Wiki/sources/. The bare form (e.g. [[power-mapping]]) renders the page title; the piped form (e.g. [[power-mapping|the mapping step]]) controls the visible text. The wiki’s link checker (scripts_build/link_check.py) flags any wikilink that does not resolve to an existing file in the tree.

Tools that support wikilinks natively include Obsidian (with autocomplete and graph view), Quartz (the static-site generator the wiki’s published version uses), and a small set of other Markdown renderers [source: beautiful-trouble]. Tools that do not support them natively — vanilla GitHub Markdown, MediaWiki, generic Markdown viewers — need a pre-processor that converts the double-bracket syntax to a relative Markdown link before rendering.

The wiki’s editorial discipline treats wikilinks as the primary mechanism for building the concept graph: every concept page cross-links to its neighbours in ## Related, and case studies cite the methods they used with the same syntax. CONVENTIONS.md sets the rules; the link-checker enforces them.

Use it for

Cross-referencing concepts and source stubs; building the link graph that powers the wiki’s browse and search experience; keeping edits inside one Markdown file without managing relative .md paths by hand.

FAQ

Wikilinks is the double-bracket Markdown extension (two open-brackets, a slug, two close-brackets) used throughout this wiki to cross-reference other pages. The wiki resolves them at build time to relative links inside Wiki/ or Wiki/sources/ [source: commons-library]. Wikilinks were originally an Obsidian convention and are now the dominant linking syntax in personal-knowledge and community-wiki tooling.

What is the syntax?

A wikilink takes the form of double-bracketed slugs. The wiki treats the slug minus .md as the target file in Wiki/ or Wiki/sources/. The bare form (e.g. [[power-mapping]]) renders the page title; the piped form (e.g. [[power-mapping|the mapping step]]) controls the visible text. The wiki’s link checker (scripts_build/link_check.py) flags any wikilink that does not resolve to an existing file in the tree.

Tools that support wikilinks natively include Obsidian (with autocomplete and graph view), Quartz (the static-site generator the wiki’s published version uses), and a small set of other Markdown renderers [source: beautiful-trouble]. Tools that do not support them natively — vanilla GitHub Markdown, MediaWiki, generic Markdown viewers — need a pre-processor that converts the double-bracket syntax to a relative Markdown link before rendering.

The wiki’s editorial discipline treats wikilinks as the primary mechanism for building the concept graph: every concept page cross-links to its neighbours in ## Related, and case studies cite the methods they used with the same syntax. CONVENTIONS.md sets the rules; the link-checker enforces them. Use wikilinks for cross-referencing concepts and source stubs, building the link graph that powers the wiki’s browse and search experience, and keeping edits inside one Markdown file without managing relative .md paths by hand.

Sources & verification