The Two-Tool Problem
Most teams use two separate systems: a task tracker for work and a wiki for documentation. On paper, this makes sense — different types of content, different workflows. In practice, the separation creates friction.
Specs live in Confluence, implementation tasks in Jira. The spec evolves but the linked tasks don’t update. The task gets done but the spec doesn’t reflect the change. Six months later, someone reads the spec and implements the wrong behavior because documentation drifted from reality.
The documentation-as-a-separate-product model creates a constant maintenance burden that teams eventually stop paying.
Documentation That Lives Next to Work
FlowEra’s knowledge base is integrated directly into the workspace. Documents aren’t in a separate tool — they’re pages you create inside the same environment where your tasks, boards, and channels live.
When a spec changes, it’s in the same system as the tasks that implement it. When a task references a design decision, it links to the KB page that explains the context. When a team onboards a new member, the runbook is in the same tool they use to pick up their first task.
The Editor
FlowEra’s KB editor supports rich content: headings, lists, code blocks with syntax highlighting, tables, images, embedded task references, LaTeX math blocks, Mermaid diagrams, and Kanban widget embeds.
For technical teams this means you can write a design doc that includes a system diagram (Mermaid), a mathematical model (LaTeX), and an embedded task board showing the implementation status — all in one document, all in sync with live data.
Collaborative Editing
Multiple team members can edit the same KB page simultaneously. Changes merge automatically using operational transformation — the same technology used by collaborative document editors. There’s no “check out” pattern, no version conflicts to resolve manually.
Version history is maintained automatically. You can see who changed what and when, and restore any previous version.
Organizing Knowledge
FlowEra organizes knowledge in a tree structure with drag-and-drop reordering. Pages can be nested arbitrarily deep. You can create a page structure that mirrors your team’s mental model — by project, by domain, by role — rather than fitting into a predefined hierarchy.
Search across all KB content is available from the global search bar, and results are ranked by relevance alongside tasks and other entities.
Linking Tasks and Docs Bidirectionally
When you reference a KB page from a task, FlowEra creates a bidirectional link. Open the KB page and you’ll see which tasks reference it. Open the task and you’ll see the linked documentation. This keeps the relationship between work and knowledge visible without requiring manual upkeep.