Skip to main content

Mind Maps & Hierarchy Diagrams in Confluence with Mermaid (Copy-Paste)

· 5 min read

The kickoff note is 40 lines of indented bullets with three levels of bolded sub-points, and half the room is still asking "so what are we actually deciding today?" The other half is screenshotting a mind map someone whiteboarded in five minutes. The whiteboard died at cleanup; the bullets survived but nobody can navigate them. A mind map is the readable version of nested notes — and when it lives in Confluence as Mermaid text, it survives the meeting.

Quick answer: turn nested notes into a Mermaid mindmap in Confluence, rendered by Mermaid Plus for Confluence. The indented text you already write becomes the branches; for concrete structures — folder layouts, project trees — use treeView; when item size matters and you want area instead of lines, use treemap. This post gives you three copy-paste examples.

Why hierarchy needs a map, not nesting

Nested bullets encode hierarchy, but reading them is work: each level means re-indenting half a line and guessing which parent a sub-point belongs to. A hierarchy diagram removes the guesswork:

  • The root shows the question. One center node (or one root line) names what the whole tree is about — the map's thesis in a word.
  • Branch depth is visible. A fifth-level branch reads as a distraction at a glance, so maps self-report when they are too deep.
  • It renders where it is read. The macro caches SVG at save, so meeting attendees see a fast image and the note-taker edits the indented text.

The winning property of a Mermaid map is that the source is a list: you can generate it from the bullets you already wrote, and editing means moving an indented line — not repositioning boxes in a canvas.

Copy-paste 1: brainstorm as a mindmap

The meeting's output as a radial map. Indentation is the hierarchy — root, then branches, then leaves:

mindmap
root((Q3 Go-to-market))
Positioning
Target segment
Message
Pricing tier
Channels
Atlassian Marketplace
Community posts
Webinars
Assets
Landing page
Docs update
Case study
Launch
Date
Owner list
Rollout

Rendered Mermaid diagram

The root node names the decision ("Q3 go-to-market"), the four branches are the workstreams, and the leaves are the concrete items — the same content as 40 lines of bullets, but navigable in one glance. Add owner names as leaf labels ("Launch → Owner list") and the map doubles as a RACI chart.

Copy-paste 2: a concrete structure as a treeView

When the hierarchy is a real thing — a repo, a folder, a doc tree — treeView draws it as rooted lines that read like a directory listing:

treeView-beta
"order-platform"
"src"
"api"
"routes.ts"
"handlers.ts"
"domain"
"order.ts"
"payment.ts"
"test"
"order.test.ts"
"docs"
"schema.md"
"architecture.md"

Rendered Mermaid diagram

Mindmap's radial layout is wrong for a repo — you want the tree hanging off one root, exactly like a tree command. Keep the treeView beside the repo README in Confluence, updated whenever a directory moves, so onboarding and PR comments reference the same structure.

Copy-paste 3: where size matters — treemap

When each item's magnitude is part of the message, treemap trades lines for area: bigger value, bigger block. Use it for allocation, spend, effort distribution:

treemap
"Budget"
"Infra" : 35
"Engineering" : 40
"Marketing" : 15
"Support" : 10

Rendered Mermaid diagram

The treemap answers "where does the money actually go?" in one block: Engineering and Infra dominate, Support is a sliver. Mindmap would show the same four items as equal-width branches and hide the story. Choose the map by what the hierarchy is: idea (mindmap), structure (treeView), or magnitude (treemap).

Turning notes into maps without a redraw

Because Mermaid maps come from indented text, converting existing notes is mechanical:

  • Reuse your bullets. Each bullet level becomes an indentation level; the map builds itself.
  • Split by domain at five levels. Deeper subtrees get their own map and a link — a map of 25 nodes is read, a map of 60 is wallpaper.
  • Put the owner in the leaf. "Launch → Rollout → Maya" turns the map into an action list that survives the meeting.

The hierarchy's companion diagrams live on the same pages: the process that consumes the decisions as a state machine workflow and the timeline that schedules the work as a release timeline.

FAQ

Does Confluence have a built-in mind map tool? No — Confluence has no native mind mapping. Mermaid Plus for Confluence renders mindmap, treeView and treemap from indented text with a live preview.

Mindmap, treeView or treemap — which fits which job? Mindmap for ideas (radial, branch-first), treeView for concrete hierarchies like a repo or folder tree, treemap when magnitude matters and area beats lines.

How do I turn meeting notes into a mind map? Use the note's bullets as the map's indentation. Root = topic, branches = agenda headings, leaves = action items with owner names.

How many branches is too many? Keep maps to 15–25 nodes; beyond that, split by domain — since it is text, splitting is copy-paste, not redraw.

Render every Mermaid diagram type — mindmap, treeView, treemap, flowchart, ER and 24 more — in Mermaid Plus for Confluence, free for up to 10 users.

Try Mermaid Plus for Confluence

All 29 Mermaid diagram types with live preview and one-click templates — free for up to 10 users.

Get it on the Atlassian Marketplace