Diagram types

Vellnar Diagrams draws 30 types of diagram from Mermaid code; each page says when to use the type and gives code to start from.

Last updated

The types are in the same five groups as the template gallery of the app. New to Mermaid? Start from Mermaid in Confluence.

Core engineering

  • Flowcharts: A flowchart shows the steps and decisions of a process, from the first step to every possible end.
  • Sequence diagrams: A sequence diagram shows the messages that people and systems exchange, in the order they happen.
  • Class diagrams: A class diagram shows the types of a system, their fields and methods, and how they relate.
  • State diagrams: A state diagram shows the states one thing can be in and the events that move it from one state to the next.
  • ER diagrams: An entity relationship diagram shows the tables of a database, their columns and how the tables are linked.
  • Git graphs: A Git graph shows commits, branches and merges, so a team can agree on how code moves to a release.

Cloud & system design

  • Architecture diagrams: An architecture diagram shows the services and resources of a system and the connections between them.
  • C4 diagrams: ‘A C4 diagram describes software at a chosen level of detail: context, containers, components or deployment.’
  • Block diagrams: A block diagram places blocks on a grid that you control, column by column.
  • Packet diagrams: A packet diagram shows the layout of a binary message, bit by bit.
  • Tree views: A tree view shows a hierarchy of folders and files as an indented tree.

Flows & modelling

  • Swimlane diagrams: A swimlane diagram is a process split into lanes, one lane for each person or system that does the work.
  • Event models: An event model tells the story of a system as a timeline of screens, commands, events and read models.
  • Use case diagrams: A use case diagram shows who uses a system and what each of them can do with it.
  • Requirement diagrams: A requirement diagram links each requirement to the parts that satisfy it and the tests that verify it.

Delivery, metrics & data

  • Gantt charts: A Gantt chart shows tasks as bars on a calendar, with their order, length and milestones.
  • Sankey diagrams: A Sankey diagram shows how a quantity flows from sources to destinations; the width of each band is the amount.
  • XY charts: An XY chart draws bars and lines on two axes, from numbers typed in the code.
  • Treemaps: A treemap shows parts of a whole as nested rectangles; the area of each rectangle is its value.
  • Timelines: A timeline places events in order under the period they belong to.
  • Pie charts: A pie chart shows how one total splits into a few shares.
  • Kanban boards: A Kanban board shows work items as cards in columns, one column for each stage.

Analysis, UX & strategy

  • Ishikawa diagrams: An Ishikawa diagram, also called a fishbone diagram, sorts the possible causes of a problem into categories.
  • Mind maps: A mind map spreads ideas around one central topic, branch by branch.
  • Quadrant charts: A quadrant chart places items on two axes, so four groups appear.
  • User journeys: A user journey lists the steps a person takes to reach a goal and scores how each step feels.
  • Radar charts: A radar chart compares a few options on several criteria at once.
  • Wardley maps: A Wardley map places the parts of a service by how visible they are to the user and how mature they are.
  • Cynefin diagrams: A Cynefin diagram sorts situations into five domains, each with its own way to respond.
  • Venn diagrams: A Venn diagram shows sets as circles and what they share where the circles overlap.