Internal knowledge base —
stop answering the same questions

Write with a clean, distraction-free editor. Full formatting support: headings (H1–H4), bold, italic, bullet and numbered lists, nested indentation, blockquotes, horizontal dividers, and inline links. The editor is focused — no toolbars cluttering your view — with keyboard shortcuts for all formatting actions. What you write is what the reader sees.

Syntax-highlighted code blocks for 20+ languages — essential for technical documentation, API references, and engineering runbooks. Inline code for short snippets. Command-line examples display correctly with monospace formatting. A one-click copy button on every code block means readers can copy commands without selecting text manually.

Drag images directly into an article — they're uploaded and embedded inline. Tables for comparison charts, configuration references, and structured data. Embed links from YouTube, Loom, Figma, and other services to include video walkthroughs and interactive prototypes directly in your documentation — no "see the linked video" required.

Link between knowledge base articles with @ to create a network of connected documentation. When you rename an article, all internal links update automatically — no broken links from reorganizing your knowledge base. Link to tasks, projects, or documents in your workspace from within any article to connect the knowledge to the work.

Organize articles into categories and subcategories — as many levels deep as you need. A typical structure might have top-level categories for Engineering, HR, Sales, and Product, each with subcategories for specific processes or products. The category tree is shown in the sidebar so readers can navigate the whole knowledge base at a glance, not just search-and-hope.

Search across all articles and categories instantly — including article body content, not just titles. Results are ranked by relevance with matching text highlighted in the snippet. Search is the primary way people navigate a knowledge base once it grows beyond a handful of articles. Type a keyword, not a folder path — the right article appears within two keystrokes.

Every save creates a version checkpoint. See exactly what changed between any two versions with a line-by-line diff view. Restore any previous version with one click — useful when an update introduced incorrect information or when a process reverts to an older approach. Version history is permanent and never expires, creating an auditable record of how your processes evolved.

Mark articles as Draft, Published, or Outdated. Set a review date to remind a designated owner to check if the content is still accurate. Articles approaching their review date appear in a "needs review" queue. Outdated articles are flagged with a banner so readers know to treat the information with caution. Documentation debt is visible — not silent.

Set read and edit permissions per category or per article. Some categories — HR policies, salary bands, confidential processes — should be visible only to specific roles. Others should be editable by anyone on the team. The whole knowledge base is accessible to workspace members by default; restrict only what needs to be restricted.

Leave comments on any article to flag inaccuracies, ask for clarification, or suggest improvements. Comments are shown in a collapsible thread below the article. The article owner is notified of new comments and can update the article in response and then resolve the comment thread. Feedback improves the knowledge base without requiring edit access.

Watch any article or category to get notified when it's updated. Team members who follow a process they work with daily will know immediately when it changes — no more following an outdated procedure because nobody told you the process was updated. Article edit notifications include a summary of what changed and a link to the diff.