Wiki & Docs

Confluence is a graveyard. Notion is a search problem. Azora's Wiki lives with the work.

Documents, Guidelines, Wiki, Task Dump, Releases — versioned, searchable, and in the same database as the tasks they describe. The spec for Sprint 12 stays linked to Sprint 12 forever.

Wiki page showing a versioned document with bidirectional links to the tasks it describes
What's in Wiki

Docs that update because the work updates.

Every doc surfaces in every related task; every task can spawn an inline doc. Bidirectional linking means a doc that references Sprint 12 also shows up *on* Sprint 12. People update docs because the link is one click from the work they're closing.

Documents

Versioned with approval workflow. Read-receipts. Periodic-review cadence. Markdown + rich-text editor.

Guidelines

Lighter-weight than documents — for team norms, runbooks, decision rationales.

Wiki

Hierarchical pages with internal-link auto-complete. Searchable. Embed tasks/units/anything.

Task dump

Brain-dump bulk text → parse to tasks. Useful for retros, planning sessions, transcribed meetings.

Cross-module links

Reference any record from any document. Bidirectional — the task page shows linked docs, the doc shows linked tasks.

Release notes

Compose release notes alongside the sprint that shipped. Tasks closed in the sprint are one click to insert. Publish to the changelog when ready.

"Our docs used to live in three different tools. Now they live with the work. People actually update them because the link is a click away from the task they're closing."

Bhaumik · AI/Software Engineer at Azora Optical Solutions — the team that built Azora

1 search

Replaces 3 different tool searches

100%

Docs linked to work

0

Lost in the wiki

Ready when you are

Stop hunting through Confluence.

Trial seeds sample docs, wiki pages, and shows you cross-module linking from day one.