Wiki & Knowledge Base

Klority's Wiki isn't just a place for docs—it's a **living knowledge hub** tied to your technical context. No more outdated Notion pages trailing your sprint progress.

Hierarchical Documentation

Organize your knowledge with an infinitely nestable page tree. Create parent/child relationships that make sense for your team's architecture.

Rich Editor (TipTap)

A beautiful, block-based editing experience that supports everything engineers need:

💻 Code Blocks: Syntax highlighting for dozens of languages.
📋 Tables: Inline table editing for API specs and schemas.
🔗 Cross-Linking: Refer to tasks, users, or modules within your docs.
🖼️ Media Embeds: Drag and drop images and diagrams.

ℹ️

Version History

Klority maintains a full, granular version history for every page. See exactly who changed what, and restore any previous version with a single click.

Global vs. Project Wikis

You can choose where your knowledge lives depending on its scope:

Project Wiki: Scoped to a specific project. Perfect for feature specs, API docs, and release notes.
Global Wiki: Scoped to the entire workspace. Ideal for company policies, onboarding guides, and architecture overviews.

Traceability Linkage

Bring your documentation into the sprint. You can link Wiki pages to specific projects and test cases, creating a "Trusted Source of Truth" that developers can refer to directly from their active task cards.