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.
Driftwood is a made-up open source photo library app, built by six people. Their decisions used to be buried in chat threads, and the wiki was always out of date.
Now their wiki is a SilverBullet space. Decisions are pages with a status and an owner, the architecture is drawn from the component pages, meeting notes and comments hand out work with @mentions, and the home page shows where the current sprint stands.
Let’s walk through the Driftwood team wiki and see what it looks like; its files are on GitHub. It’s just one example of how a space could be set up. Yours will likely look nothing like it, and that’s exactly the point: you make SilverBullet work the way you want.
The home page shows the current sprint and who owns each task, open tasks per team member, and which decisions still need one.
Built with: Space Lua · Space Style · Recipients
function team.header()
local open = query[[
from t = index.tasks()
where not t.done and t.recipients
select t
]]
local waiting = query[[
from p = index.contentPages "adr"
where p.status == "proposed"
select p
]]
-- ...
endFrom Library/Team Home.
Each component page says what it connects to in its frontmatter, and the Architecture page draws the diagram live. Add a component, and it shows up in the picture.
Built with: Frontmatter · Mermaid diagrams
${mermaid.diagram(mermaid.relationGraph {
pages = query[[from index.contentPages "component"]],
direction = "LR",
})}From Architecture.
Decisions are pages with a status, owner and date. This page counts them by status, lists the active and the superseded ones, and draws how they relate.
Built with: Queries · Frontmatter
${query[[
from p = index.contentPages "adr"
where p.status ~= "superseded" and p.status ~= "deprecated"
order by p.date desc
select {
ADR = "[[" .. p.name .. "]]",
Status = p.status,
Owner = p.owner,
Decided = p.date,
}
]]}From ADR.
Write @hana in a task and it lands in Hana’s open tasks and in her Mention Inbox, whether it’s in the sprint, a project or the weekly sync. One view puts those open tasks at the top of every person page.
Built with: At-mentions · Recipients · Views
view.define {
name = "team.openTasks",
dock = "page-top",
frame = "minimal",
refreshOn = { "navigate", "index" },
content = function()
local id = (editor.getCurrentPageMeta() or {}).identity
if not id then return nil end
local tasks = team.openTasks(id)
if #tasks == 0 then return nil end
return "**Open tasks for @" .. id .. "**\n" .. table.concat(tasks)
end,
}From Library/Team Home.
Questions go in a comment next to what they’re about. Jane asks Pete about a proposed decision with @pete, Pete signs his reply and answers back to @jane, and each mention lands in that person’s Mention Inbox. Once it’s settled, resolve the comment.
Built with: Comments · At-mentions · Signatures · Frontmatter live previews
Two ways to collaborate, at two speeds: pick the one that fits your team, or use both.
This is how Driftwood works. 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.
The slower, more deliberate way. Keep your docs as markdown in your repository, versioned together with the code they describe. Everyone writes in SilverBullet on their own checkout, and changes are proposed, reviewed and merged in pull requests, like the code. More on docs as code →
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.