Aamu.app Docs are for the written parts of team work: internal notes, customer instructions, meeting summaries, policies, project plans, support knowledge, sales notes, technical references, and the structured writing that should stay close to tasks, Helpdesk tickets, emails, meetings, files, and databases.

The important point is that a Doc is not only a text page. In Aamu, a Doc is a collaborative workspace object. It can be edited in a rich editor, linked to other objects, discussed in comments, shared as a public read-only version, restored from snapshots, searched, used by Team Brain, and managed through the API.

Docs in the workspace

Docs live inside projects, and the Docs list can show public documents, the current user's drafts, deleted documents, and project-specific document lists. Docs can be tagged, filtered through search, and surfaced in unread/unseen workflows when they matter to the team.

That makes Docs useful for more than long-form writing. A Doc can be the explanation behind a task, the source material for a support answer, the notes from a customer meeting, the specification behind a database row, or the maintained policy that Team Brain should retrieve later.

Collaborative rich-text editing

The editor is built on a collaborative ProseMirror/TipTap document model. Aamu tracks save state, connection state, document versions, live editing presence, selected word and character counts, and document updates as structured editor steps.

For everyday writing, that means the editor behaves like a modern rich-text document surface: type naturally, select text to format it, drag blocks around, insert media or structured blocks, and keep writing without switching to a separate tool.

SlashMenu: everything you can insert

Typing / opens the Docs SlashMenu. It is the fastest way to add blocks, formatting, media, links, and AI help from inside the editor.

The current SlashMenu includes these insert commands:

  • AI: open the AI dialog with the current selection or document context.

  • Internal link: search Aamu objects and insert an internal workspace link.

  • Blockquote: add a quoted block.

  • Code Block: insert a syntax-highlighted code block.

  • Table: insert a table, starting with a 3 x 3 grid.

  • 2 columns: insert a two-column layout section.

  • Drawing Canvas: add an embedded drawing canvas.

  • Image, audio or video: add a media placeholder and upload or insert media.

  • Share a file: search project files and insert a public file link when shared-file insertion is enabled.

  • YouTube video: paste a YouTube URL and embed the video.

  • JavaScript component: insert a custom browser-side component block.

  • Custom CSS: add custom CSS for richer document rendering.

The same menu also includes formatting commands:

  • Heading 1, Heading 2, and Heading 3.

  • Bold and Italic.

  • Bullet List, Numbered List, and Task List.

The practical effect is that the Doc can become a structured working surface: a policy with tables, a meeting note with task lists, a customer page with linked files, a technical note with code blocks, or a richer internal page with embeds and custom rendering.

Selection tools and keyboard-friendly formatting

When text is selected, the bubble menu provides quick formatting actions: H1, H2, H3, bold, italic, underline, strikethrough, inline code, blockquote, link, and AI help for the selected text.

Common shortcuts are also supported in the toolbar hints, such as Ctrl+B for bold, Ctrl+I for italic, Ctrl+U for underline, Ctrl+L for setting a link, and heading shortcuts for H1-H3.

AI inside Docs

Docs are part of Aamu's AI workspace, not a separate writing island. The SlashMenu AI command and the selection bubble AI action can open an AI dialog with either selected text or the broader document context.

That makes common writing work faster: summarize a section, rewrite selected text, draft a follow-up paragraph, turn notes into a clearer checklist, or ask a question about the content currently in front of you.

Docs also connect to Team Brain. Maintained Docs can become the knowledge that Aamu retrieves later for Helpdesk answers, email drafts, AI commands, and internal questions. That is why writing good Docs improves more than the document itself: it improves the shared context available to the whole workspace.

Internal links and hover context

Aamu Docs can link to internal workspace objects. The internal link command opens a search picker so the writer can connect a Doc to tasks, projects, meetings, support tickets, files, and other workspace context.

When internal links are used, Aamu can show hovercards and embedded context around the editor. This keeps a document connected to the work it describes instead of becoming a disconnected page.

Comments, mentions, tags, and project context

Docs support compact comment sidebars, unread counts, file attachments in comments, and search inside comments. They also support project placement, tags, and mentions when the editor is opened in a project context.

That turns a Doc into a place where the team can discuss the material without moving the conversation to another app. The written content and the discussion around it stay together.

Sharing Docs publicly

A Doc can be shared publicly in read-only mode. Sharing creates a unique hidden URL that can be sent to someone outside the workspace.

The shared version is snapshot-based. When the Doc is shared, Aamu stores the current HTML in a document snapshot and uses that snapshot for the public link. The share dialog shows both HTML and PDF links:

/shared/doc/html/SHARE_ID
/shared/doc/pdf/SHARE_ID/Document-title.pdf

Aamu also tracks how many times the shared document has been viewed. If the original Doc changes after sharing, the UI can show that a new shared version is available. The owner can then publish the new version deliberately instead of changing the public version by accident.

Sharing can also be stopped. When sharing is stopped, the Doc no longer exposes that public read-only version.

Snapshots and recovery

Snapshots are useful beyond public sharing. Aamu can store document snapshots and show them in the File menu. The snapshot dialog lets the user preview stored versions, use a range control when there are multiple snapshots, and select a snapshot to restore.

When a snapshot is selected, Aamu creates a snapshot of the current content before replacing it. That gives the user a way back from the restore operation itself.

The Docs API also uses this safety model. When an API HTML update replaces existing Doc content through the editor step pipeline, Aamu creates a snapshot before applying the new content.

Page setup, print, and shared themes

The File menu includes page setup for documents that need printable or shareable presentation. Page setup supports units, orientation, margins, paper size, and the theme used in the shared document view.

Docs can also be printed directly from the editor. For shared documents, Aamu can render the selected theme and expose the public HTML/PDF version from the shared snapshot.

Drafts, publishing, and deletion

Aamu separates draft and public Docs. A user's draft can remain private to the owner until it is published. Owners can publish a draft, unpublish a public Doc back to draft status, or delete a Doc from the File menu.

This is different from public share links. Publishing controls whether the Doc is part of the team's normal public Docs list inside Aamu. Sharing creates an external read-only link for a specific snapshot.

Docs and databases

Docs are especially useful when paired with Aamu Databases. Database rows can reference one or more Docs, and Docs can explain the context behind structured records such as customers, deals, projects, policies, or product notes.

For example, a CRM row can keep structured fields for stage, value, owner, and next action while linking to Docs for meeting notes, proposals, onboarding instructions, or account plans. The structured row stays scannable, and the Doc carries the richer narrative.

Docs API

Aamu exposes Docs through the Team API. Integrations can list project Docs, create a Doc from a title and HTML, fetch one Doc, and update its title or HTML.

GET   /api/v1/docs/
POST  /api/v1/docs/
GET   /api/v1/docs/DOC_ID
PATCH /api/v1/docs/DOC_ID

Send x-api-key and x-project-id. Write calls can set x-aamu-actor. Use Docs read permission for list/get and Docs write permission for create/update.

POST /api/v1/docs/
x-api-key: YOUR_API_KEY
x-project-id: YOUR_PROJECT_ID
Content-Type: application/json

{
  "title": "Customer onboarding notes",
  "html": "<h1>Onboarding</h1><p>Goals, decisions, and next steps.</p>"
}

API-created Docs are native Aamu Docs, not detached HTML blobs. They remain searchable and linkable and can participate in comments, Team Brain, database document fields, and the normal editor workflow. For images or other uploaded assets, use the Files API to prepare and complete the upload, then place the returned browser URL in the Doc HTML.

When to use Docs

Use Docs when the team needs maintained context, not only a quick message. Good examples include:

  • Support policies and answer templates that Team Brain should retrieve.

  • Meeting notes that should stay linked to follow-up tasks or CRM rows.

  • Project plans, implementation notes, onboarding material, and internal guides.

  • Customer-specific notes, proposals, and account plans.

  • Technical references with code blocks, tables, embedded media, and linked files.

  • Public read-only documents that need a stable shared HTML or PDF version.

The bottom line

Aamu.app Docs are the workspace's maintained writing layer. They combine collaborative editing, slash-command blocks, AI help, internal links, comments, tags, sharing, snapshots, page setup, and API access.

That combination matters because knowledge is only useful when it stays connected to the work around it. A Doc can explain the task, support the ticket, document the meeting, enrich the CRM row, feed Team Brain, and still be shared externally as a controlled snapshot when needed.