Diagrams · Mermaid macro
Diagrams anyone on the team can fix, reviewed like code
With the Mermaid macro your diagrams are text - they diff, they review, and whoever spots the mistake corrects them. The text renders on the Confluence page, so a diagram stops being a file only its author can edit, and stops rotting because fixing it was too much bother.
Anyone on your team fixes the diagram in a minute
Nobody needs a drawing tool, a licence or an eye for layout - they add a line. The arrows arrange themselves, so a diagram that would take twenty minutes to redraw takes one to correct, and your diagrams stop rotting because fixing them was too much bother.
Your team learns one syntax for most of what it draws
Flowcharts, sequence and class diagrams, state machines, ER models, user journeys, Gantt charts, pie and XY charts, mindmaps, timelines, C4 and gitgraph - all from the same markdown-like language your team learns once. Dense graphs switch to the ELK layout engine when the default arrangement runs out of room.
Your readers recognise the system at a glance
Switch on custom icons and an architecture diagram pulls in any of Iconify's
270,000-plus icons with a (prefix:icon-name) reference, so a box stops
being a box: it is visibly Postgres, Kafka or S3. Readers recognise the system
instead of decoding labels.
Your diagram lives where it belongs, and renders where you write
Type it into the macro, or point it at the definition your repository already keeps
- a URL, an attachment, Google Drive, or a credentialed S3, SFTP or database
connection. Inside a Markdown document a fenced mermaid block renders
in place, so one page holds the explanation and the picture, and readers download
the source to reuse it.
What the other Mermaid apps leave you keeping in step
A dozen apps render Mermaid in Confluence, and most of them do it one way: you paste
the definition into the macro, and that becomes the copy of record you keep in step
by hand. A few can read a URL or a Git repository; none reaches Google Drive, an S3
bucket, an SFTP server or a database. But Mermaid's whole argument is that diagrams
live next to the code they describe, wherever that is. Point this macro at the
.mmd where it already sits - repository, Drive, bucket or SFTP - and
your page renders whatever is there today, with no paste to maintain and the same
connection available to every other macro in the pack.
Mermaid is one of 31 macros in Macro Pack
One app to install, one licence to renew, one place your team learns - and 30 more formats it already reads, from spreadsheets and diagrams to API specs and documents.
See every macro in the pack