Skip to content
Log in Sign up

Module 06

The Library

Documentation lives beside the work rather than in a second product with a second permission model.

What it does

A Library collection with nested articles
A Library collection with nested articles
Markdown is the storage format
One renderer and one cross-site-scripting story. History is a readable text diff, export is the file itself, and nothing is trapped in a proprietary document format.
One login, one permission model, one audit trail
An article obeys the same permission catalogue as a work item. Nobody administers a second product to decide who reads what.
Revisions, comments and templates
Every article keeps its revision history. Comments use the same renderer as descriptions, and starter templates give a collection a shape on the day it is created.
Export it and leave
A collection exports as markdown files in a zip, and markdown imports back. An exit route that works is the only version of that promise worth making.

What it is not

Naming the ceiling is what makes everything above it credible. The roadmap says which of these are deferred and why.

  • Real-time collaborative editing.
  • Public publishing of an article outside the organization.
  • Whiteboards or diagramming.

The rest of the product

Try it against your own week

Log a real week of your own hours and put it through approval. That is a better test than any feature list, and it takes an afternoon.
Sign up See pricing