Skip to main content
A document in Tatara does not have to be prose. Give it a format and it opens as a board you drag cards across, a checklist with due dates, a grid of typed columns, a live index of your other documents, a dashboard, or a map of branching ideas. The format is a way of showing the document. Underneath, the document is still Markdown text. It lives in a folder, carries tags and a description, turns up in search, and your agents read it as context like any other document.

The six formats

A document with no format is ordinary prose and opens in the normal editor.

Other kinds of document

Some things you might look for here are separate kinds of document, each with its own page in the app. The New document menu does not offer them. Ask your agent for one.

Creating one

In the app. In the sidebar, open a folder’s ⋯ menu or right-click the folder, and choose New document. To create a document at the top level, right-click an empty part of the document list instead. The submenu offers: Type a name and press Enter. The document opens in that view, ready to fill in. The New document button on the Documents header and the + on a folder create a plain prose document in one click. Ask your agent. “Make me a kanban board of the launch tasks”, “a table of our suppliers”, “a view of every competitor profile we have”. Your agent creates the document in the right format and fills it in. Agents can create all six formats, including the two the menu does not offer. Bases and dashboards are built from a question about your workspace rather than drawn by hand, so they are much quicker to describe than to assemble. A document keeps its format through later edits, moves, and renames.

Working with a formatted document

A formatted document opens in its view rather than in a text editor. Drag a card, tick a task, or type in a cell, and the change saves as you make it, the same way typing in a prose document does. The status line at the bottom of the window shows the save. See Getting around. A few things work differently from a prose document:
  • The title is read-only on the page. It sits at the top of the view, but you cannot type into it there. Rename the document from its ⋯ menu in the sidebar. The exception is a mind map, where the title is the centre of the map and you can rename it in place.
  • The details rail starts closed. Owner, type, description, tags, and links are all still there. Open it with Open the rail at the right of the top bar. It stays open for that visit only. See The details rail.
  • There is no width control. Boards, tables, bases, dashboards, and maps fill the whole page. A tracker sits in the normal reading column.
  • Deletes can be undone. Delete a card, task, row, column, or topic and a message names what went, with an Undo button. Deleting something that holds more, such as a column full of cards, asks you to confirm first.
A locked document’s view is read-only for everyone until it is unlocked.
HTML documents are a different thing: a finished, self-contained page rather than a view over a document. See HTML documents.

If a document will not render

Sometimes a document cannot be shown in its format, usually because an edit broke the structure the view depends on. The app falls back to the plain text editor and puts a View card above it that says why:
The document’s content is still there. Ask your agent to put it right. Once the document is valid again, the view comes back on its own.

Kanban boards

Columns and cards, dragged between stages.

Task trackers

Checklists with due dates, priorities, and tags.

Data tables

Typed columns, with formulas.

Base views

Live views over the documents in your workspace.

Dashboards

A homepage of live blocks over your workspace.

Mind maps

Branching topics, laid out and reshaped on a map.