Personal Handbooks

Personal knowledge bases allow compound learning and make it easier to discover new abstractions or connections between concepts. Some interesting properties that a good personal knowledge base should have:

• Simple, open source and multi-platform. Works offline, uses plain text files, and has a backup mechanism similar to Git.
• Focus on capturing ideas and content as fast as possible.
• Should be managed as a graph:
  • Nodes are notes or smaller graphs. Notes should be atomic, concept-oriented and densely linked.
  • Bidirectional links connecting nodes.
  • Nodes can have several parents (concepts).
  • Users can remix and connect ideas in multiple overlapping hierarchies.
• Each concept can be linked to external content (video, book, audio).
  • Content can have tags (related concepts).
• Can be made public.
• Personal knowledge bases can be personal ontologies with similar core components (individuals, classes, attributes, relations, …).

Open Source Projects

• Logseq.
• Dendron.
• Foam.
• Noosphere.

Handbooks

• Nikita Voloboev
• Daryll Santos
• Daniel Schildt
• Julian Shapiro
• Gordon Brander
• h0p3
• Karlicoss
• Victoriano Izquierdo
• Piotr Stojanow
• Sergio Gasquez
• Paul Copplestone
• Hiran Venugopalan
• Liz Code
• Simon Späti
• Jonathan Porter
• Jacky Zhao
• Pelayo Arbués
• Tom Critchlow
• Mario López
• Alex Turner
• Aditya Chandel
• Faint Signal

Compilations

• Meta Knowledge GitHub repository
• Second Brain Collection.
• Best of Digital Gardens.