# Mind map view

A mind map draws your items as a tree on a canvas, and every mark on the canvas is real data.

## The drawing is the data

- Every node on the canvas is a real item, drawn with the same card the board uses.
- Every branch between two nodes is the real parent link, so dragging a node under a different parent reparents the item.
- Every arrow is a real dependency, the same one the Gantt view draws.

The view's filters, the view's type scope and your permissions apply here exactly as they apply in a list.

There are no sticky notes, no free-drawn shapes and no nodes that are not items.

## Breaking work down

Add a child from a node, and the child becomes a real child item. The child takes the child type that its parent's type allows.

Collapse a branch at the joint where the children leave the node.

To make one item wait for another, drag from a node's link handle onto the node that should wait. A dependency that would repeat a dependency you already have, or that would make a loop, is refused while you are still dragging.

## Where the nodes sit

The layout is automatic until you move something. A node you drag keeps the offset you gave it and takes its subtree with it. **Fit to view** brings the whole map back on screen after you have panned away.

## Next

- [Types, fields, views and hierarchy](../../get-started/types-fields-views-hierarchy/)
- [How dependency scheduling works](../../how-it-works/dependency-scheduling/)
