Documents: your studio's knowledge base
Your studio's knowledge base: specs, meeting notes, procedures, release notes.
No integration to connect. Documents are collaborative in real time: several people write in the same document, each seeing the others' cursors.
The tree
Left-hand column. A document can contain other documents, which replaces folders.
This is the product's important structural choice. No empty folders, no hierarchy to maintain alongside the content: an "Onboarding" page contains the pages that detail it, and reads just as well on its own.
Scope
| Scope | What it groups |
|---|---|
| Studio | What depends on no app: team process, HR, methods |
| App | What belongs to one app: specs, product decisions, release notes |
The selector at the top of the tree filters the display. All documents shows everything.
Archiving
A document goes to the bin from its menu. Its sub-documents go with it - the interface reminds you before you confirm, because it is the kind of action whose reach is easy to misjudge when the tree is collapsed.
The editor
Type / to insert a block.
| Block | What it is |
|---|---|
| Text | Paragraph |
| Heading 1, 2, 3 | Page structure |
| Bulleted list, numbered list | Enumerations |
| Checklist | Tick boxes |
| Quote | Indented passage |
| Code | Monospace block |
| Table | Editable grid |
| Divider | Horizontal rule |
Inline formatting (bold, italic, strikethrough) goes through the floating bar that appears on selection, or through the usual shortcuts.
Every document carries an emoji and a title. The emoji matters more than you would think: in a tree of forty pages, it is what makes a page recognisable at a glance.
Collaboration
Simultaneous editing is handled by a real-time synchronisation layer:
- everyone's changes arrive live for the others;
- collaborators' cursors are visible, with their names;
- there is no conflict to resolve - concurrent changes merge.
The undo history is shared by the same layer: Cmd+Z undoes your changes,
not those of the person next to you.
There is no "Save" button. What is written is saved.
Tutorial - a knowledge base that holds up
- Create one root document per broad area, in Studio scope: "Methods", "Team onboarding".
- Create one root document per app, in App scope: it becomes the entry point for everything about it.
- Nest rather than piling up at the root. A root with thirty entries stops being readable.
- Give every page an emoji. It takes five seconds and it changes navigation.
- Put a table of links at the top of root documents: the tree shows the structure, the table of links shows the intent.