How to build a team wiki people actually use
Why most wikis die, and a simple structure that keeps yours alive, with docs and search next to your chat.
The short answer
Wikis die because they are far from where people work and nobody owns them. A wiki that survives sits next to chat, has a clear owner for each section, and is easy to search. Start with five pages, not fifty.
A simple setup
Pick five pages
How we work, who does what, onboarding, tools and logins policy, and decisions.
Name an owner
One person per page, with a review date.
Link from chat
When someone answers the same question twice, write it down and link it.
Review monthly
Delete or fix pages that are out of date.
What makes a wiki searchable
Plain titles
Name pages for what people type, not internal jargon.
One topic per page
Short pages beat long ones.
Search across everything
Messages, docs and files in one search.
Recent edits visible
Show when a page was last updated.
Wiki in Dock
Dock has a wiki and real-time co-editing docs with comments and suggestion mode, share links with password and expiry, and one search across messages, docs and files, fast on large history and in any language. A decision in a channel can become a page in two clicks, and AI agents can read the page over MCP.
See the docs page and the search page.
What makes Dock different: it connects to your tools
Dock connects the places your team already works. Notion: connect your Notion pages, then type @notionpage_ in any chat to tag a page; everyone gets a preview card and your AI agents can read it. GitHub: link GitHub read-only, pin repositories to a chat, tag them with @github_ and ask the AI about them. Claude and Codex: use your own Claude or Codex plan inside Dock chats, or connect any MCP agent to your workspace with a token.
All of this sits next to chat, video meetings (with recording, transcripts and AI summaries), docs, tables, calendar, tasks and a drive, in a self-hosted app with no per-seat licence. You run the server yourself, and some integrations are young, so check the setup guides for what each one covers.
Questions
Wiki or docs?
A wiki is a linked, owned set of pages. Docs are single documents. Many teams use both.
How big should it be?
Start small. Grow only when people ask the same question twice.
Can AI help?
An agent can summarise and search pages, but a human should own the content.