Creating diagrams and charts using mermaid code is simple. mermaid allows you to dynamically code and modify diagrams. when called, mermaid renders code definitions into a diagram in SVG format.
The live editor is enough for most general uses of mermaid
Absolute beginners are recommended to view the video tutorials on the Live Editor at theTutorialspage.
- Using the mermaid live editor.
- Using one of the many mermaid plugins.
- Hosting mermaid on a webpage, with an absolute link.
- Downloading mermaid and hosting it on your Web Page.
Notes: More in depth information can be found on Usage.
Following any of these examples, you can get started with creating your own diagrams using mermaid code.
A great way to get started with mermaid is to visit The mermaid live editor.
In the Code
section one can write or edit raw mermaid code, and instantly Preview
the rendered result on the panel beside it.
This is a great way to learn how to define a mermaid diagram.
For some popular video tutorials on the live editor go to Overview.
Saving a Diagram: Downloading the image may be a ideal for a majority uses.
The Links and the markdown code can be referenced to display the diagram.
The Mermaid configuration is for configuring the appearance and behavior of mermaid diagrams. An easy introduction to mermaid configuration is found in the Advanced usage section. A complete configuration reference cataloguing default values is found on the mermaidAPI page.
Thanks to the growing popularity of mermaid, many plugins already allow the generation of mermaid diagrams from within popular applications. An extensive list of applications the support mermaid plugins can be found here.
This is covered in greater detail in the Usage section
This method can be used with any common web server. Apache, IIS, nginx, node express [...], you pick your favourite.
We do not need to install anything on the server, apart from a program (like Notepad++) that can generate an html file, which is then deployed by a web browser (such as Firefox, Chrome, Safari, but not Internet Explorer).
So if you want to really simplify things when testing this out, don't use a web server at all but just create an HTML file locally and drag it into your browser window. The browser will do the work of rendering the mermaid diagrams according to the descriptions you've given!
When writing the html file, we give the web browser three instructions inside the html code:
a. A reference for fetching the online mermaid renderer, which is written in Javascript.
b. The mermaid code for the diagram we want to create.
c. The mermaid.initialize()
call to start the rendering process.
This is what needs to go into the html file (and all of them are important), for the mermaidAPI to render the diagrams:
a. A reference to the address of the mermaid.js
or the mermaid.min.js
file has to be contained in a <script src>
tag like so:
<body>
<script src="https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js"></script>
</body>
b. The embedded mermaid diagram definition needs to be contained inside a <div>
tag that signifies that it is a mermaid diagram:
<body>
Here is a mermaid diagram:
<div class="mermaid">
graph TD
A[Client] --> B[Load Balancer]
B --> C[Server01]
B --> D[Server02]
</div>
</body>
Notes: every mermaid chart/graph/diagram definition, has to have separate <div>
tags.
mermaid.initialize()
calls take all the definitions contained in <div class="mermaid">
tags it can find in the html body and starts to render them one by one. It is called this way:
<body>
<script>mermaid.initialize({startOnLoad:true});</script>
</body>
Notes: It is good practice to keep the mermaid.initialize()
API call right next the mermaid.min.js
script
tag.
startOnLoad
is a parameter that can optionally be changed to false, this would then prevent mermaid from immediately rendering upon loading.
<html>
<body>
<script src="https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js"></script>
<script>mermaid.initialize({startOnLoad:true});</script>
Here is one mermaid diagram:
<div class="mermaid">
graph TD
A[Client] --> B[Load Balancer]
B --> C[Server1]
B --> D[Server2]
</div>
And here is another:
<div class="mermaid">
graph TD
A[Client] -->|tcp_123| B(Load Balancer)
B -->|tcp_456| C[Server1]
B -->|tcp_456| D[Server2]
</div>
</body>
</html>
Notes: This has to be saved in an HTML
file and opened with a browser.
This method is similar to 3, if only a little more involved. The difference may be very subtle even, but it offers its own advantages, mainly in speed.
-
install node v10 or 12, which would have npm
-
download yarn using npm by entering the command below: npm install -g yarn
-
After yarn installs, enter the following command: yarn add mermaid
-
After downloading mermaid, you can then open the mermaid file you’ve downloaded and go to the
dist
folder. -
Find the
mermaid.min.js
file, a. select the file. b. press the shift key and right click on it c. select copy as path from the options. -
Paste it within the
script
tag as thesrc
.
<script src="Paste the mermaid.min.js file address here"></script>
<script>mermaid.initialize({startOnLoad:true});</script>
- It should look something like this
<script src="C:\Users\myPC\mermaid\dist\mermaid.js"></script>
<script>mermaid.initialize({startOnLoad:true});</script>
-
Add the graph and diagram definitions as you would in number 3. a. be mindful of the
div
tags. -
Save, load/edit your HTML file to your liking.
Note placing the HTML file on the same folder the mermaid
file you've downloaded is a good practice and allows you to shorten the address on the src
section.
As seen here, in this full example:
<html lang="en">
<head>
<meta charset="utf-8">
</head>
<body>
<div class="mermaid">
graph LR
A --- B
B-->C[fa:fa-ban forbidden]
B-->D(fa:fa-spinner);
</div>
<div class="mermaid">
graph TD
A[Client] --> B[Load Balancer]
B --> C[Server1]
B --> D[Server2]
</div>
<script src="C:\Users\MyPC\mermaid\dist\mermaid.js"></script>
<script>mermaid.initialize({startOnLoad:true});</script>
</body>
</html>
Three additional comments from Knut Sveidqvist, creator of mermaid:
-
In early versions of mermaid, the
<script src>
tag was invoked in the<head>
part of the web page. Nowadays we can place it directly in<body>
as seen above. However, older parts of the documentation frequently reflects the previous way which still works. -
We initialize the mermaid rendering with
mermaid.initialize()
directly in the html code. In principle this could be done through placingmermaid.initialize()
inside ofmermaid.min.js
. We would then eliminate the need for this explicit line in the html. However, there are use cases where we do want to separate the two steps. Sometimes we want full control over when we start looking for<div>
tags inside the web page withmermaid.initialize()
, for example when we think that all<div>
tags may not have been loaded by the timemermaid.min.js
runs. -
In the third method,
mermaid.min.js
is called using an absolute path. Even worse, the example includes the mermaid version number which of course will change as time goes by. However, the example makes it easy to understand what is going on - even though it is perhaps doomed in a way we do not want in a production environment. When going from testing mermaid out to getting serious with it, I would suggest one of the following approaches for callingmermaid.min.js
:- If you do not enter a specific version, you automatically get the latest one.
- If you really need a specific version, hard code it (this is rare but it happens).
- If you need to know the current mermaid version, replace a mermaid code block with the word
info
and the version will be returned like this