What it's for

The board shows what you're doing. The wiki holds the things a card is a poor home for: how something works, what was decided and why, and runbooks and specs. Each board has one, from the view menu. It follows the board's permissions and is covered by the same API, so an agent can write documentation the same way a person does. Wiki shows every board's wiki at once, each as a top-level folder.

Writing

Pages are Markdown, edited with a live preview, as in Obsidian: each line shows formatted until your cursor is on it. Paste or drop an image to attach it. What's saved is exactly the Markdown you typed.

Every page has a code, such as W-31, that never changes even when the page is renamed. That makes it the right thing to use in a commit message or a link.

Linking and live queries

  • [[Page title]] links to a page. Each page lists the pages that link to it.
  • A card reference shows as a live chip with the card's current state.
  • A ```slipdock block is a live query, such as "open cards tagged docs". It's answered each time the page is read, using the reader's own permissions.
  • Wanted pages lists links to pages nobody has written yet.
  • A page can be pinned to a card, as the page about that card.

Organising

A page has two independent places. Its parent page says what it is part of, such as the rollback section of a runbook. Its folder says where it is kept, such as Design, Contracts or Meetings. You don't have to invent a page just to hold others.

Folders and pages can have an icon and a colour. Pages can start from a template, and stay drafts until they're ready.

History

Every save is kept as a revision, recording who made it, how (the web, the CLI or an agent) and why. You can compare any two revisions, or put a page back to an earlier one. The revert is itself a new revision, so nothing is lost.

Your wiki and your own folder

Your wiki is one folder tree: your Knowledge Base first, then a folder for every board you have, a sub-board in its epic's folder. An archived board is left out; restore it to have its wiki back. slipdock sync mirrors your wiki to a folder on your computer and keeps the two in step, so you can write in Obsidian or any editor that works on a folder of Markdown. An existing Obsidian vault can be imported. See the CLI.

Publishing

A page can be published at a public, read-only link that needs no account. Its live queries are answered at the moment you publish, and its links become plain text, since an anonymous reader has no permissions to follow them. The images it embeds (![[photo.png]]) are shown, through the page's link; other embedded files stay as their names. Publishing again refreshes it, and you can withdraw it at any time.