Vanilla knowledge management

A personal wiki can begin with four files and a few map headings, before you install a single graph package.

Vanilla Org already supplies file links, heading links, IDs, search, Agenda, capture, and exports. A personal wiki can therefore begin with four files and a few map headings rather than a database:

* Maps
** Distributed systems
- [[id:...][Consensus notes]]
- [[id:...][Failure testing]]

Four note kinds cover most work, and they are conventions rather than mutually exclusive Org object types. Reference notes preserve sourced facts. Project notes support an outcome. Daily notes preserve chronology. Evergreen notes express a durable idea in your own words. A single heading can shift between these roles as your understanding changes.

The discipline is intellectual, not mechanical. Create stable IDs for heavily referenced headings so links survive renaming. Keep titles descriptive. Record sources at capture time, while you still remember them. Periodically synthesize scattered notes into maps or project decisions. A graph visualization cannot substitute for that synthesis work; it only draws the links you already made.

org-roam and Denote in 2026

org-roam models a network of nodes backed by Org files and headings plus an SQLite database that provides backlinks and queries. The repository is active and mature: v2.3.1 shipped 26 June 2025, with commits into April 2026, under GPL-3.0-or-later. It suits people who genuinely navigate by backlinks and node relationships. Its costs are real: database maintenance, extra concepts, and a workflow that can overwhelm beginners.

Denote emphasizes predictable filenames, file types, identifiers, signatures, and keywords without requiring a central database for its core model. It is very actively maintained. GNU ELPA carried 4.2.x in May 2026, the repository was active in August 2026, GPL-3.0-or-later. It suits file-oriented users who want disciplined naming and linking across Org and other text formats.

Vanilla Org is enough when search, IDs, and a modest file tree answer your retrieval needs. Choose org-roam for graph-shaped node workflows; choose Denote for file-naming and portable notes. Do not install either before you can articulate the retrieval failure it solves.

Digital gardens and transclusion

A digital garden is a publishing convention: evolving linked notes exposed to readers, which org-publish can implement. org-transclusion displays referenced content in place without copying it; its repository was active in April 2026, though its latest formal GitHub release is still v1.3.0 from 2022 while the source declares 1.4.0. Treat it as active but release-irregular, GPL-3.0-or-later, and situational.

Summary. Vanilla Org already supplies links, IDs, search, Agenda, capture, and export: enough for most retrieval needs. org-roam and Denote solve specific failures you should be able to name before adopting them.