Mermaid Mindmap Syntax

Brainstorming

Capture and structure ideas during planning sessions as fast as you can type — indentation is the only syntax. The outline becomes a picture, and the picture stays editable text.

System architecture

Sketch the components and sub-systems of an architecture radially from a central root. Mindmaps trade precision for speed, which makes them ideal for the first conversation about a system.

Knowledge base

Document topic hierarchies, technology stacks, and learning paths in README files. Each indent level is a branch, so restructuring knowledge is just re-indenting lines.

Open FlowViz and type mindmap.

Define the root node on the next line: root((My Topic)) for a circle shape.

Add first-level children by indenting with 2 spaces: child topic.

Add deeper levels by indenting further — each indent level is a child of the line above.

Use ((text)) for circles, [text] for rectangles, (text) for rounded rectangles on any node.

Export your mindmap as SVG.

Can I turn a markdown outline into a mindmap?

Almost directly. Mermaid mindmaps take their entire structure from indentation, exactly as a nested markdown list does, so an outline usually only needs its `-` bullets stripped to become valid. Paste the result under a `mindmap` line, keep the indentation as it was, and the hierarchy renders unchanged — which makes it a quick way to see the shape of notes you have already written.

What is a Mermaid mindmap used for?

Brainstorms, topic hierarchies, and outlines — the structure comes entirely from indentation, so you can write one as fast as you think.

How is the hierarchy defined?

By indentation: each line indented deeper becomes a child of the line above it.

Can I change node shapes in a mindmap?

Yes — root((circle)), [square], and (rounded) render different shapes per node.