> ## Documentation Index > Fetch the complete documentation index at: https://docs.tatara.app/llms.txt > Use this file to discover all available pages before exploring further. # Mind maps > The mindmap format: branching topics on a canvas, with the document's title at the centre. A mindmap document is a map. The document's **title is the centre**, main branches radiate from it, and topics nest underneath. Reach for it when the shape of the thinking matters as much as the words: a strategy you are pulling apart, a customer you are profiling, an offering you are scoping. ## Creating a map In the sidebar, open the `⋮` menu on `Documents` or on a folder, choose `New document`, then `Mindmap`. Name it — that name becomes the centre of the map — and start adding branches. Or ask your agent: *"Turn our positioning notes into a mind map — the pillars as branches, the proof points underneath each."* Because a map is branches and nestable topics, an existing [board](/formats/kanban) or [tracker](/formats/tracker) can become one without rewriting the content. Ask your agent to convert it. ## Working with a map The map opens two levels deep and is fully editable. * **Add topics.** Hover a node and click `+`, or press Tab for a child and Shift+Enter for a sibling. The new node opens ready to be named. * **Edit a topic.** Double-click a node, or select it and press Enter, to edit its title and its note — the small print under it — in place. Enter commits, Escape reverts. Double-clicking the centre renames the document itself. * **Move topics.** Alt+↑ and Alt+↓ move a node among its siblings; Alt+→ makes it a child of the node above, and Alt+← promotes it back out. The whole branch travels with it. * **Drag to reparent.** Drag a node onto another and it becomes that node's last child. A collapsed target opens on drop. Dropping a node inside its own branch is refused. * **Tick a topic done.** Topics can carry a checkbox, so a map can double as a plan. Done topics dim. * **Delete a topic.** Select it and press Delete. A topic with sub-topics or hidden detail asks you to confirm, and says how many go with it. * **Collapse and expand.** Every node with children has a pip on its right edge, showing how many descendants are hidden when collapsed. Click it or press Space. The depth buttons (1 / 2 / 3 / All) collapse the whole map at once. * **Find a topic.** The search box dims everything that does not match, opens the branches that do, and counts the matches. `/` jumps to it, Escape clears it. * **Move around.** Drag empty space to pan, scroll to zoom, `Fit` to frame the whole map again. Arrow keys walk the map — left to the parent, right into the first child, up and down between siblings. A topic title can link to another document in your brain, and the link is clickable on the map. A branch with nothing under it is fine, and so is a map with no branches at all — topics simply hang straight off the centre. Panning, zooming, collapsing, searching, and changing depth only change what you are looking at. They are never saved, so opening a map and exploring it writes nothing. ## Seeing what your agents see The `Canonical markdown` toggle opens a live panel showing the document exactly as it is stored and exactly as an agent reads it, flashing the lines your last edit changed. You never need it — but it is there, because you should always be able to check what your agents are actually working from. `Edit` in that panel lets you make changes there directly; `Apply` stays disabled until the draft is a valid map, and tells you what is wrong when it is not. The map is read-only wherever the rest of Tatara is: without edit access you can still pan, zoom, collapse, and search, but nodes cannot be changed. A mindmap document has no properties rail and no width control — the map is the page, and the title is the centre node. The same content, rendered as a board you drag cards across. All six formats, and which to pick. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.