Wiki & docs
Two flavors of long-form writing inside SynStacks — a quick-and-easy wiki channel for team notes, and a heavier documentation channel backed by BookStack for reference docs that need real structure.
Overview
Chat is great for the moment, boards are great for the work — but some things need to live longer. Onboarding guides, architectural decisions, runbooks, internal API references. That's what the wiki and documentation channels are for.
- Wiki (
wikichannel type) — lightweight per-server pages. Markdown editor, instant save. Best for team notes that don't need a heavy structure. - Documentation (
documentationchannel type) — embeds a BookStack instance. Full-featured CMS with shelves, books, chapters, and pages. Best for reference docs you want to organize like a manual.
Wiki channels
Add a wiki-type channel from the sidebar quick-create or Server Settings → Channels. The wiki view is a single editable surface — write in Markdown, save with ⌘S / Ctrl+S or the Save button.
Common uses:
- Team standup notes
- Quick onboarding checklist for new members
- Project goals and milestones
- Meeting agendas and notes
- Shared lists (links, tools, accounts)
Wiki content supports the same markdown subset as chat messages — headings, lists, code blocks with language hints, links, bold/italic. No image uploads in v0.1.1 (planned for v0.2).
One page per channel. In v0.1.1, each wiki channel holds a single page. If you need multi-page hierarchy, create a documentation channel instead.
Documentation channels (BookStack)
If your project needs proper documentation — API references, architecture decision records, support knowledge bases — add a documentation-type channel. SynStacks embeds a hosted BookStack instance directly into the channel pane.
BookStack gives you a full content-management hierarchy:
| Level | Purpose |
|---|---|
| Shelf | Top-level grouping of related books. Optional. |
| Book | A documentation set — e.g. "Engineering Handbook", "Customer-facing API". |
| Chapter | Grouping of related pages inside a book. |
| Page | An individual document. WYSIWYG or Markdown editor, with image uploads, attachments, and revision history. |
Each documentation channel can host its own BookStack instance, or point at a shared one — useful when you want all your servers to read from a single corpus of docs.
Wiki vs documentation
| Wiki | Documentation | |
|---|---|---|
| Pages per channel | One | Unlimited |
| Hierarchy | Flat | Shelf → Book → Chapter → Page |
| Editor | Markdown | WYSIWYG or Markdown |
| Images / attachments | Not yet | Yes |
| Revision history | No | Yes |
| Best for | Quick team notes, onboarding, agendas | API docs, architecture, manuals |
Permissions
Anyone in the server can read wiki and documentation channels. Editing is available to all members in v0.1.1 — fine-grained edit permissions are on the v0.2 roadmap.
For BookStack documentation channels, the BookStack instance has its own role system (admin, editor, viewer). Set that up inside BookStack — SynStacks just embeds the iframe.