Wiki / Docs

Docs that stay connected to the work they explain.

Nodetra is not a detached document shelf. It is a docs layer for launch briefs, runbooks, decisions, formulas, code notes, and policies that still know which task, project, sprint, and person they belong to.

Request early access → View product
API v2 Launch Brief
Draft synced 28s ago v18

API v2 Launch Brief

The gateway cutover is tracked against #API Gateway Redesign with @Emily Nakamura owning QA and Sprint 14 signing off readiness.

Keep this page as the single launch narrative for screenshots, customer updates, and cross-functional status.

Current focus

  • Gateway owners confirmed for shared API contract review.
  • Risk register attached to Sprint 14 exit criteria.
const owner = resolveOwner("gateway"); await publishBrief({ notify: true });
Risk model risk = impact x likelihood
Table PDF Callout Versioned
4Page permission roles
6Mention target types
12+Rich editor block types
1Audit trail behind every published page

Docs platform

Write the decision once. Keep the trail alive.

Rich editor

Slash commands, tables, callouts, code blocks, embeds, PDFs, toggles, and math blocks.

Linked work

Pages can mention tasks, projects, sprints, meetings, users, and other pages with backlinks.

Draft to publish

Autosave protects work in progress while publish keeps the official record intentional.

Inline comments

Anchored threads keep review next to the paragraph, table, or decision being discussed.

History restore

Compare versions and restore older decisions without erasing the audit trail.

Access control

Page-level roles, departments, password links, and private mention scrubbing are built in.

Version history

When a decision changes, the old one does not disappear.

Teams can compare versions, restore a previous page, and keep the recovered state as a new auditable version. That is the difference between knowledge that can be trusted and a folder full of stale files.

Page history
Compare v17 -> v18 +8 -3

API gateway owners confirmed for shared contract review.

- Customer FAQ blocked by release copy.

+ Customer FAQ linked to published release notes.

+ Sprint 14 exit criteria attached to the handoff.

QA owner remains @Emily Nakamura.

Comparison

What changes when docs and work live together.

Without connected docs

  • Decisions scatter across files, chats, and meeting notes.
  • Tasks reference documents nobody knows how to find.
  • Reviews happen away from the exact paragraph being changed.
  • Rollback depends on memory instead of version evidence.

With Nodetra Wiki/Docs

  • Every page can point to the task, project, sprint, and owner it supports.
  • Inline comments, mentions, and backlinks keep follow-up close to context.
  • Access is denied by default for private pages and mentions.
  • History compare and restore make decisions recoverable.

How it stacks up

Built for operational documentation, not just nice pages.

Feature Nodetra Wiki/Docs Others
Page-level permissions Viewer, commenter, editor, admin Space or team level only
Department sharing Built in with member context Manual group setup
Draft / publish flow Autosave plus explicit publish Autosave only
Inline comments Anchored threads Detached comment stream
Cross-system mentions 6 entity types Pages only
Version history Compare and restore Limited rollback
Code and math blocks Native editor blocks Plugin dependent
Public shares Password and expiry support Basic link sharing
Integrated PM tool Same workspace as tasks Separate product

Connected knowledge

The document becomes part of the workflow, not a file beside it.

Request early access → Review security Contact support