Team Documents and Wiki — Self-Hosted Knowledge Base
Rich-text editor, version history, attachments, and cross-references. A team wiki that connects to your chat and tasks.
Documentation tools have a habit of becoming information silos. You write a spec in Notion, discuss it in Slack, create tasks in Asana, and six months later nobody can find the original spec because it is buried under 200 other pages in a tool half the team forgot they have access to.
Zioan's documents live in the same workspace as your chat and task boards. When you write a project spec, you can link it to the relevant kanban board tasks. When someone asks a question in chat about the document, both the question and the answer are searchable from the same search bar.
Your documents stay on your server. Version history, attachments, notes: all stored on infrastructure you control. No export needed because there is nothing to export from.
What's included
- Rich-text editor with full formatting toolbar
- Font sizes, text colors, and highlighting
- Tables with background colors and formatting
- Code blocks with syntax highlighting
- Version control with named versions
- Visual diff for version comparison
- Collaborative notes and annotations
- File attachments (images, PDFs, DOCX, any type)
- Internal cross-references to docs, snippets, and boards
- Import from Markdown, PDF, DOCX, HTML, and URL
- Nested folder organization with emoji icons
- Published and draft document states
- Global search integration (Cmd+K)
How documents work in Zioan
Rich-text editor
The editor supports headings, bold, italic, underline, strikethrough, code blocks, blockquotes, tables with background colors, ordered and unordered lists, images, links, and page breaks. Font sizes and text colors are configurable. It is a real editor, not a stripped-down text field.
Version control
Save named versions of any document. Compare versions side by side with a visual diff that highlights additions, deletions, and changes in color. Restore a previous version with one click. This is version control designed for documents, not code, but with the same precision.
Collaborative notes
Add notes to any document for review comments, questions, or annotations. Notes are separate from the document content itself, keeping the published version clean while preserving discussion context.
Attachments
Upload images, PDFs, spreadsheets, or any file type directly to a document. Attachments stay with the document, so when you share the page, the supporting files come along.
Internal cross-references
Link documents to other documents, code snippets, or kanban boards. These are structured links within Zioan, not just URLs. When you rename a linked resource, the reference stays valid.
Import from external formats
Bring existing content into Zioan by importing Markdown files, PDFs, DOCX documents, HTML, or even content from a URL. Useful for migrating from Notion, Confluence, or Google Docs without manually reformatting everything.
Folders and organization
Organize documents into folders within spaces. Folders support nesting, so you can create hierarchies like Company Wiki > Engineering > Architecture Decisions. Each folder can have its own emoji icon for quick visual identification.
Why teams choose Zioan for documentation
Documents that connect to the work
A project spec linked to its kanban board tasks. A meeting note that references the calendar event and the chat thread where follow-ups were discussed. In Zioan, documents are not isolated pages. They are connected to everything else in the workspace, and the connections are navigable.
Replace Notion without per-seat pricing
Notion charges $10 per user per month. For a 15-person team, that is $1,800 per year for a documentation tool. Zioan includes its full document editor, version history, and wiki capabilities in the one-time license. Add team members without cost calculations.
Version history you can trust
Visual diffs show exactly what changed between two versions of a document. Named versions let you mark stable points (like "v2.0 approved by client") and restore them later. This is not a vague "last edited by" timestamp. It is a real history of your document's evolution.
Your knowledge base stays on your server
Company wikis often contain sensitive information: internal processes, client-specific procedures, security documentation. With Zioan, none of this leaves your infrastructure. No third-party vendor can access your knowledge base, and you control who sees what through space-level permissions.