Back to Blog
team@tinypod.app

Self-Hosting BookStack: Team Wiki and Documentation

BookStack is a simple, self-hosted wiki platform. Organize documentation in Books, Chapters, and Pages with WYSIWYG editing.

bookstackwikidocumentationknowledge-base

Why a Wiki?


Team knowledge scattered across Slack messages, Google Docs, and people's heads is a recipe for repeated questions and lost context. A wiki centralizes knowledge.


Why BookStack?


Simple Mental Model

Content is organized in a book metaphor:

  • Shelves: Group related books
  • Books: Top-level topics
  • Chapters: Sections within a book
  • Pages: Individual documents

    • Everyone understands books. No training needed.


    WYSIWYG Editor

    Rich text editor with:

  • Formatting toolbar
  • Image upload and embedding
  • Code blocks with syntax highlighting
  • Tables
  • Diagrams (with draw.io integration)

    • Markdown editor also available for those who prefer it.


    Search

    Full-text search across all content. Find anything instantly.


    Permissions

  • Role-based access control
  • Per-shelf, per-book, per-chapter permissions
  • View, edit, create, delete permissions separately

    • BookStack vs Alternatives


    BookStack vs Outline

  • BookStack: Simpler, book metaphor, WYSIWYG
  • Outline: More modern, real-time collab, Markdown-native
  • BookStack for traditional documentation, Outline for team knowledge bases

    • BookStack vs MediaWiki

  • BookStack: Easy to use, beautiful
  • MediaWiki: Wikipedia's engine, complex, powerful
  • BookStack for teams, MediaWiki for public wikis

    • BookStack vs Confluence

  • BookStack: Free, self-hosted, simple
  • Confluence: $6/user/month, complex, enterprise features
  • BookStack replaces Confluence for 90% of teams

    • Deployment


    1. Deploy BookStack on TinyPod

    2. Create admin account

    3. Set up shelves and books for your organization

    4. Start documenting


    Resources: 1 CPU, 512 MB RAM.


    Documentation Structure Tips


    Engineering

  • Architecture: System design decisions
  • Runbooks: How to handle incidents
  • Onboarding: New developer setup
  • APIs: Internal API documentation

    • Company

  • Processes: How we do things
  • Policies: Rules and guidelines
  • Templates: Document templates

    • Product

  • Features: How features work
  • FAQ: Common questions
  • Release Notes: What changed and when

    • The key to a useful wiki: someone must be responsible for keeping it current.