The modules
Knowledge base
Optional, per project. For the things people ask twice — conventions, runbooks, how a particular integration behaves.
- The contents. Articles nested under groups, so reference material has a shape rather than being a flat pile.
- An article. Written like a document, but meant to be looked up later rather than read once.
How it differs from Docs
A document records something — a brief, a decision, a specification. An article answers something, and expects to be found months later by someone who was not in the conversation.
In practice: if it has a date and a moment it belonged to, it is a document. If it should still be true next year, it is an article.
Structure
Articles sit under groups, and can nest one level further. That is deliberately shallow — deep hierarchies are where reference material goes to be forgotten.
Staying true
An article can carry a review cadence. When that lapses it is flagged as stale, which is the honest state for reference material nobody has checked in a year — better than quietly presenting it as current.