Nexus — Docs & Knowledge Base

• Create a child (sub-page) by right-clicking any page in the sidebar and choosing Add subpage.
• Drag and drop pages in the sidebar to reorder or nest them under a different parent.
• Add an emoji icon and a cover colour to each page for quick visual identification in long lists.
• Use top-level pages inside a Space as index pages — list what lives beneath with short descriptions.

• Technical Specification, API Documentation, Meeting Notes, Product Requirements (PRD), SOP, Release Notes, Project Documentation, Incident Report.
• Each template ships with real section headings, not empty placeholders — fill in the blanks instead of designing a structure from scratch.

A dedicated ADR template follows the standard Decision → Context → Options Considered → Final Decision → Consequences flow. Link an ADR to the Features, Stories, Tasks, and Releases it affects using the same linking tools covered below, so anyone revisiting a past decision can see exactly what shipped as a result of it.

• Predefined templates for the categories every engineering team needs: Architecture, API Reference, Database Schema, Infrastructure, Security, Deployment, Development Guide, Testing Strategy, and Troubleshooting Guide.
• Use these to keep technical documentation consistent across teams instead of everyone inventing their own outline.

• Bold, italic, underline, strikethrough, and inline code.
• Text colour and highlight colour for callouts and emphasis.
• Hyperlinks — paste any URL or type [[ to link to another KnowHub page.
• Mention a teammate with @ to notify them instantly and link to their profile.

Every page's right-hand panel includes an auto-generated Table of Contents, built from your headings. Click any entry to jump straight to that section — handy on long technical specs and runbooks.

Type [[ inside the editor to open the page picker. Start typing the page name and select it to insert an inline link.

• Links are bidirectional — both pages show each other in their Backlinks panel.
• Hover over a link to preview the target page without navigating away.
• Broken links (where the target page has been deleted) are highlighted in red.

• Click Link in the page toolbar and choose Ticket or Test Case.
• Search by ID or title. Multiple items can be linked to a single page.
• Linked tickets and test cases appear in the page's right-hand panel, and the page appears in their detail sidebar — a full bidirectional trace from requirement to code to test.

Every page has a Backlinks tab in the right-hand panel showing every page, ticket, or test case that references it. Use this to understand impact before editing a specification — if ten test cases link to a requirements page, changing the requirement means reviewing those ten tests.

Backlinks are automatic — Dependencies are explicit. Use the Dependencies tab to declare that one document depends on another (for example, an Authentication Architecture page depending on a Security SOP), so the relationship is visible even when the two pages never mention each other inline.

• Assign one or more reviewers to a page from the Properties panel.
• Each reviewer approves, requests changes, or rejects — with an optional comment.
• Turn on Require approval for a page and it cannot move to Published until every assigned reviewer has approved. Attempting to publish early tells you exactly who is still pending.
• Every decision is kept permanently in the page's approval history, even after reviewers are reassigned.

• Every page can have an Owner and a Backup Owner — the people accountable for keeping it accurate.
• Set a Team responsible for broader accountability beyond a single person.
• Owner, backup owner, and team are all set from the Properties panel and shown alongside the page's status, version, and dates.

Set a review interval — for example, "review this document every 90 days" — and Nexus keeps track of it automatically.

• Once the interval elapses without the owner marking the page reviewed, it's automatically flagged as outdated.
• The owner gets notified that a review is due.
• Click Mark as reviewed now on any page to reset the clock the moment you've confirmed it's still accurate.

A page's Impact panel shows the full chain — Documentation → Feature → Stories → Tasks → Test Cases → Release — so anyone reading a technical specification can immediately see what was built from it, not just what was written about it.

Before editing a specification, check its Impact panel for a summary like "Linked to 3 Features, 14 Stories, and 27 Tasks." If any linked work belongs to a release, that release is called out too — so you know exactly how much work is potentially affected before you change a word.

• Click the comment bubble at the top of any page to open the threaded comment panel.
• @mention a teammate to notify them in-app — they can reply directly in the thread.
• Resolve comments to archive the thread without deleting it. Resolved threads remain accessible in the history.
• Highlight any sentence in the editor and choose Comment on selection to anchor feedback directly to that exact text — e.g. "The API timeout should be 30 seconds" — instead of a generic page-level note.

Hover over the page header and click the reaction button to add an emoji. Reactions act as a lightweight approval signal — a thumbs-up from a tech lead can indicate the spec is approved for development without a formal comment thread.

• Every save creates a version snapshot automatically — nothing to configure.
• Open Version History from the page's ⋮ menu to browse all snapshots by date and author.
• Click any version to preview the exact content at that point in time.
• Click Restore to revert — the current version is preserved as a new snapshot, so nothing is permanently lost.

Every page has an Activity tab showing exactly what happened to it, in order — who created it, who commented, who edited which section, who approved it, and when each version was published or restored. A single feed answers "what changed here, and who touched it" without digging through comments and version history separately.