# Mermaid - Generation of diagrams and flowcharts from text in a similar manner as markdown

**URL:** <https://talk.commonmark.org/t/mermaid-generation-of-diagrams-and-flowcharts-from-text-in-a-similar-manner-as-markdown/1882>\
**Category:** Uncategorized\
**Created:** [October 11, 2015, 9:26am UTC](https://talk.commonmark.org/t/mermaid-generation-of-diagrams-and-flowcharts-from-text-in-a-similar-manner-as-markdown/1882 "2015-10-11T09:26:12Z")\
**Posts on this page:** 1\
**Showing post:** 42

<div class="post-metadata">

**Author:** ![martinwoodward](https://talk.commonmark.org/user_avatar/talk.commonmark.org/martinwoodward/32/2380_2.png) [@martinwoodward](https://talk.commonmark.org/u/martinwoodward)\
**Post date:** [February 7, 2022, 2:08pm UTC](https://talk.commonmark.org/t/mermaid-generation-of-diagrams-and-flowcharts-from-text-in-a-similar-manner-as-markdown/1882/42 "2022-02-07T14:08:01Z")

</div>

Regarding

A:

````auto
```mermaid

````

vs B:

````auto
```!mermaid

````

Looks like the consensus is just to stick with A (without the !). Will ensure that GitHub aligns with that as we introduce mermaidjs support.

I was thinking that the `!language` approach helps differentiate between block rendering/execution vs straight syntax highlighting and would also have the advantage of not adjusting any existing examples of folks inlining mermaid code examples, but folks today don’t do `!mermaid` for those examples, they do `javascript`. Similarly even things like inline SVG would be `xml` in syntax highlighting terms.

Let’s kick off a separate thread for math?

---

_[View the full topic](https://talk.commonmark.org/t/mermaid-generation-of-diagrams-and-flowcharts-from-text-in-a-similar-manner-as-markdown/1882)._