Knowledge Bases
This hub is for tools and methods that treat notes as working memory rather than as a single final document. The useful distinction is not just "editor" versus "not editor." It is whether the system supports retrieval, cross-reference, staged drafting, and long-lived accumulation in a way that changes how you think and write.
Obsidian is one current product example because it keeps local files, links, metadata, and plugins in view. But the category is broader than one company: wiki-like systems, linked-note software, research archives, and other local-first authoring tools belong here too.
Knowledge Base Value Model
Knowledge bases matter when they reduce rediscovery cost. A good one turns scattered work into durable recall, gives future collaborators a route into the material, and keeps private notes close enough to become public artifacts when the time is right.
Retrieval
Search, backlinks, tags, and stable file names help a thought survive beyond the week it was written.
Publication
Notes become useful outside the notebook when they can project into guides, service pages, books, documentation, or route maps.
Codebase curriculum
The same habit applies to software: events, page data, component rationales, and architecture notes should make a codebase easier to learn.
What this page should help answer
Use this route when the question is practical: what makes a tool a knowledge base, which kinds of structure matter, and where the category overlaps with writing, research, and publication. The point is not generic productivity advice. It is to understand which properties actually change author workflow.
- Which features move a tool from plain editing into knowledge-base behavior.
- How local files, links, tags, metadata, and search affect long-lived writing projects.
- How private note systems later feed essays, books, documentation, or worldbuilding surfaces.
Starting references
Obsidian Help
A clear current reference for how one popular product describes the overlap between Markdown editing and knowledge-base behavior.
CommonMark
Useful when the question becomes "what exactly is the Markdown substrate?" rather than "what does this app add on top?"
Markdown
The original Markdown project page is still a helpful anchor for the older, lighter-weight file-format side of the ecosystem.
Text editing
Use the adjacent text-editing route when you need the broader editor lineage rather than only the knowledge-base category.