Decisions, plans, architecture, meeting notes and how-tos, in one place everyone can edit. Run it as a live wiki, or keep it versioned with your code.
Team knowledge tends to live scattered across chat threads, agent context, or a single person’s head. The wiki is out of date because updating it is a chore, and nobody can find the decision from last spring.
We can do better than this. Pick your adventure.
Everyone works in the same space on your SilverBullet Server, from the browser or synced from Desktop. Assign a task with @pete, and it lands in Pete’s Mention Inbox. Reply in a comment, right where the question was asked. Edits from teammates show up as they happen. Everything gets versioned centrally with Git.
Keep your docs as markdown in your repository, versioned together code it describes. Write in SilverBullet, review changes in pull requests, and publish them from CI. Your docs live and change with your code.
Give each component page a few lines of frontmatter saying what it connects to, and the Architecture page draws the diagram live. Add a component, and it shows up in the picture. Decisions, guides and meeting notes sit in their own folders, a click away in the page tree.
Write each decision as a page, tag it #adr and give it a status, owner and date. Every decisions table, like the one on a project page, lists it straight away, and keeps it current when the status changes. Mentions and tasks addressed to you wait in your Mention Inbox.
SilverBullet can keep every change in git automatically, so you can see who changed what, and roll back.
Other editors, scripts and coding agents can edit the same files, SilverBullet merges their changes in.
It’s markdown in a folder. If you ever leave, you take everything with you.