Personal knowledge management (PKM) is the practice of capturing, organising, and reconnecting the information you care about so it stays useful over years rather than days. There's no single method — there's a family of them.
Why "system" matters
Anyone can save articles or take notes. What differentiates a personal knowledge management system from an ad-hoc habit is that it has explicit rules: what you capture, where it lives, how it connects to existing material, and when you revisit it. Without those rules the archive grows into a pile that gets harder to navigate the larger it gets.
The four main approaches
Zettelkasten (slip-box)
Niklas Luhmann's slip-box method: every idea gets its own card, each card has a unique ID, and cards link to other cards by ID rather than living in hierarchical folders. Modern digital versions (Obsidian, Roam, Logseq) inherit the same atomic-note + bidirectional-link model. Strong on idea synthesis; demanding to maintain at scale.
PARA (Projects, Areas, Resources, Archive)
Tiago Forte's framework. Everything you store fits into one of four high-level buckets keyed to actionability: projects with deadlines, areas you care about long-term, resources you might use later, and archived completed work. Simpler than Zettelkasten, less emphasis on idea synthesis.
Building a Second Brain
Also Tiago Forte. Adds a capture-organise-distil-express pipeline (CODE) on top of PARA. The goal is not just storage but writing output — periodically processing notes into reusable building blocks. Suits people whose work product is writing.
Knowledge graphs
The newest school, and the one this site exists to advocate for. Notes, links, topics and people are stored as linked data — typed relationships in a machine-readable format. Where Zettelkasten links are typed by convention ("see also"), graph links can be typed semantically ("cites", "refutes", "extends") and queried like a database. Compatible with everything above: PARA buckets become topic clusters, Zettelkasten links become typed edges.
Where bookmarks fit
A bookmark archive is the lowest-friction surface area for any personal knowledge management system. You're already saving links — browsers cover the basics. The unlock is treating saved links as first-class nodes in whatever system you're running, not as a parallel pile.
In a Zettelkasten, a bookmark becomes a literature note. In PARA, it slots into a project or resource bucket. In a knowledge graph (primer here), it's a node like any other, with topics and connections.
How to choose
- Output is writing/research? Zettelkasten or Second Brain.
- Output is project delivery? PARA.
- You want to keep the archive across tools and decades? Knowledge graph in linked data, regardless of which method you layer on top.
- You want all three to coexist? Knowledge graph as the storage layer; PARA or Zettelkasten as the discipline you practise on it.
The data-ownership question
Most personal knowledge management tools (Notion, Roam, Evernote, Pocket) store your archive on their servers in a proprietary schema. The discipline you practise is portable; the substrate isn't. When a tool closes or changes pricing, your method survives but your archive may not.
Storing the underlying data as W3C-standard linked data in a Solid pod dissolves the lock-in. Switch tools without re-platforming; let multiple tools read the same graph; archive a working copy in your own backups.
A graph-based knowledge-management system in a pod you own
mnera.io stores your bookmark graph as linked data in your own Solid pod, with topics, collections, and an Atlas view that visualises the shape of your interests over time.