diff --git a/.vite/server.ts b/.vite/server.ts
index 50be3908da..c62b6236ab 100644
--- a/.vite/server.ts
+++ b/.vite/server.ts
@@ -12,10 +12,10 @@ async function createServer() {
appType: 'custom', // don't include Vite's default HTML handling middlewares
});
- app.use(vite.middlewares);
app.use(express.static('./packages/mermaid/dist'));
app.use(express.static('./packages/mermaid-example-diagram/dist'));
app.use(express.static('./packages/mermaid-mindmap/dist'));
+ app.use(vite.middlewares);
app.use(express.static('demos'));
app.use(express.static('cypress/platform'));
diff --git a/cypress/platform/knsv.html b/cypress/platform/knsv.html
index 11340c4dbc..d4ffa0c0c7 100644
--- a/cypress/platform/knsv.html
+++ b/cypress/platform/knsv.html
@@ -6,6 +6,10 @@
rel="stylesheet"
href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css"
/>
+
+
mindmap
root
+ A
+ B
+ C
+ D
+ E
+ A2
+ B2
+ C2
+ D2
+ E2
child1((Circle))
grandchild 1
grandchild 2
@@ -63,8 +83,10 @@
::icon(mdi mdi-fire)
gc6((grand child 6))
::icon(mdi mdi-fire)
+ gc7((grand grand child 8))
-
+
+
+```
+
+[1]: Setup.md?id=render
+[2]: 8.6.0_docs.md
+[3]: #mermaidapi-configuration-defaults
+[4]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/String
+[5]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Statements/function
+[6]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Boolean
+[7]: https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Object
+[8]: https://developer.mozilla.org/docs/Web/API/Element
diff --git a/vdocs/config/Tutorials.md b/vdocs/config/Tutorials.md
new file mode 100644
index 0000000000..bfaa4facf9
--- /dev/null
+++ b/vdocs/config/Tutorials.md
@@ -0,0 +1,72 @@
+# Tutorials
+
+This is list of publicly available Tutorials for using Mermaid.JS . This is intended as a basic introduction for the use of the Live Editor for generating diagrams, and deploying Mermaid.JS through HTML.
+
+**Note that these tutorials might display an older interface, but the usage of the live-editor will largely be the same.**
+
+For most purposes, you can use the [Live Editor](https://mermaid-js.github.io/mermaid-live-editor), to quickly and easily render a diagram.
+
+## Live-Editor Tutorials
+
+The definitions that can be generated the Live-Editor are also backwards-compatible as of version 8.7.0.
+
+[Chris Chinchilla: Hands on - Text-based diagrams with Mermaid](https://www.youtube.com/watch?v=4_LdV1cs2sA)
+
+[GitLab Unfiltered: How to Create Mermaid Diagrams](https://www.youtube.com/watch?v=SQ9QmuTHuSI&t=438s)
+
+[GitLab Unfiltered: Emilie adds a mermaid diagram to the handbook](https://www.youtube.com/watch?v=5RQqht3NNSE)
+
+[World of Zero: I Learn How To Build Flowcharts and Signal Diagram's in Mermaid.JS](https://www.youtube.com/watch?v=7_2IroEs6Is&t=207s)
+
+[Eddie Jaoude: Can you code your diagrams?](https://www.youtube.com/watch?v=9HZzKkAqrX8)
+
+## Mermaid with HTML
+
+Examples are provided in [Getting Started](../intro/n00b-gettingStarted)
+
+**CodePen Examples:**
+
+https://codepen.io/CarlBoneri/pen/BQwZzq
+
+https://codepen.io/tdkn/pen/vZxQzd
+
+https://codepen.io/janzeteachesit/pen/OWWZKN
+
+## Mermaid with Text Area
+
+https://codepen.io/Ryuno-Ki/pen/LNxwgR
+
+## Mermaid in open source docs
+
+[K8s.io Diagram Guide](https://kubernetes.io/docs/contribute/style/diagram-guide/)
+
+[K8s.dev blog: Improve your documentation with Mermaid.js diagrams](https://www.kubernetes.dev/blog/2021/12/01/improve-your-documentation-with-mermaid.js-diagrams/)
+
+## Jupyter Integration with mermaid-js
+
+Here's an example of Python integration with mermaid-js which uses the mermaid.ink service, that displays the graph in a Jupyter notebook.
+
+```python
+import base64
+from IPython.display import Image, display
+import matplotlib.pyplot as plt
+
+def mm(graph):
+ graphbytes = graph.encode("ascii")
+ base64_bytes = base64.b64encode(graphbytes)
+ base64_string = base64_bytes.decode("ascii")
+ display(Image(url="https://mermaid.ink/img/" + base64_string))
+
+mm("""
+graph LR;
+ A--> B & C & D;
+ B--> A & E;
+ C--> A & E;
+ D--> A & E;
+ E--> B & C & D;
+""")
+```
+
+**Output**
+
+
diff --git a/vdocs/config/accessibility.md b/vdocs/config/accessibility.md
new file mode 100644
index 0000000000..387871de42
--- /dev/null
+++ b/vdocs/config/accessibility.md
@@ -0,0 +1,208 @@
+# Accessibility Options
+
+## Accessibility
+
+Now with Mermaid library in much wider use, we have started to work towards more accessible features, based on the feedback from the community.
+
+To begin with, we have added a new feature to Mermaid library, which is to support accessibility options, **Accessibility Title** and **Accessibility Description**.
+
+This support for accessibility options is available for all the diagrams/chart types. Also, we have tired to keep the same format for the accessibility options, so that it is easy to understand and maintain.
+
+## Defining Accessibility Options
+
+### Single line accessibility values
+
+The diagram authors can now add the accessibility options in the diagram definition, using the `accTitle` and `accDescr` keywords, where each keyword is followed by `:` and the string value for title and description like:
+
+- `accTitle: "Your Accessibility Title"` or
+- `accDescr: "Your Accessibility Description"`
+
+**When these two options are defined, they will add a coressponding `` and `<desc>` tag in the SVG.**
+
+Let us take a look at the following example with a flowchart diagram:
+
+```mermaid-example
+ graph LR
+ accTitle: Big decisions
+ accDescr: Flow chart of the decision making process
+ A[Hard] -->|Text| B(Round)
+ B --> C{Decision}
+ C -->|One| D[Result 1]
+
+```
+
+See in the code snippet above, the `accTitle` and `accDescr` are defined in the diagram definition. They result in the following tags in SVG code:
+
+
+
+### Multi-line Accessibility title/description
+
+You can also define the accessibility options in a multi-line format, where the keyword is followed by opening curly bracket `{` and then multiple lines, followed by a closing `}`.
+
+`accTitle: My single line title value` (**_single line format_**)
+
+vs
+
+`accDescr: { My multi-line description of the diagram }` (**_multi-line format_**)
+
+Let us look at it in the following example, with same flowchart:
+
+```mermaid-example
+ graph LR
+ accTitle: Big decisions
+
+ accDescr {
+ My multi-line description
+ of the diagram
+ }
+
+ A[Hard] -->|Text| B(Round)
+ B --> C{Decision}
+ C -->|One| D[Result 1]
+
+```
+
+See in the code snippet above, the `accTitle` and `accDescr` are defined in the diagram definition. They result in the following tags in SVG code:
+
+
+
+### Sample Code Snippet for other diagram types
+
+#### Sequence Diagram
+
+```mermaid-example
+ sequenceDiagram
+ accTitle: My Sequence Diagram
+ accDescr: My Sequence Diagram Description
+
+ Alice->>John: Hello John, how are you?
+ John-->>Alice: Great!
+ Alice-)John: See you later!
+```
+
+#### Class Diagram
+
+```mermaid-example
+ classDiagram
+ accTitle: My Class Diagram
+ accDescr: My Class Diagram Description
+
+ Vehicle <|-- Car
+```
+
+#### State Diagram
+
+```mermaid-example
+ stateDiagram
+ accTitle: My State Diagram
+ accDescr: My State Diagram Description
+
+ s1 --> s2
+
+```
+
+#### Entity Relationship Diagram
+
+```mermaid-example
+ erDiagram
+ accTitle: My Entity Relationship Diagram
+ accDescr: My Entity Relationship Diagram Description
+
+ CUSTOMER ||--o{ ORDER : places
+ ORDER ||--|{ LINE-ITEM : contains
+ CUSTOMER }|..|{ DELIVERY-ADDRESS : uses
+
+```
+
+#### User Journey Diagram
+
+```mermaid-example
+ journey
+ accTitle: My User Journey Diagram
+ accDescr: My User Journey Diagram Description
+
+ title My working day
+ section Go to work
+ Make tea: 5: Me
+ Go upstairs: 3: Me
+ Do work: 1: Me, Cat
+ section Go home
+ Go downstairs: 5: Me
+ Sit down: 5: Me
+
+```
+
+#### Gantt Chart
+
+```mermaid-example
+ gantt
+ accTitle: My Gantt Chart Accessibility Title
+ accDescr: My Gantt Chart Accessibility Description
+
+ title A Gantt Diagram
+ dateFormat YYYY-MM-DD
+ section Section
+ A task :a1, 2014-01-01, 30d
+ Another task :after a1 , 20d
+ section Another
+ Task in sec :2014-01-12 , 12d
+ another task : 24d
+
+```
+
+#### Pie Chart
+
+```mermaid-example
+ pie
+ accTitle: My Pie Chart Accessibility Title
+ accDescr: My Pie Chart Accessibility Description
+
+ title Key elements in Product X
+ "Calcium" : 42.96
+ "Potassium" : 50.05
+ "Magnesium" : 10.01
+ "Iron" : 5
+
+```
+
+#### Requirement Diagram
+
+```mermaid-example
+ requirementDiagram
+ accTitle: My Requirement Diagram
+ accDescr: My Requirement Diagram Description
+
+ requirement test_req {
+ id: 1
+ text: the test text.
+ risk: high
+ verifymethod: test
+ }
+
+ element test_entity {
+ type: simulation
+ }
+
+ test_entity - satisfies -> test_req
+
+```
+
+#### Gitgraph
+
+```mermaid-example
+ gitGraph
+ accTitle: My Gitgraph Accessibility Title
+ accDescr: My Gitgraph Accessibility Description
+
+ commit
+ commit
+ branch develop
+ checkout develop
+ commit
+ commit
+ checkout main
+ merge develop
+ commit
+ commit
+
+```
diff --git a/vdocs/config/directives.md b/vdocs/config/directives.md
new file mode 100644
index 0000000000..9060afdcfc
--- /dev/null
+++ b/vdocs/config/directives.md
@@ -0,0 +1,255 @@
+# Directives
+
+## Directives
+
+Directives gives a diagram author the capability to alter the appearance of a diagram before rendering by changing the applied configuration.
+
+The significance of having directives is that you have them available while writing the diagram, and can modify the default global and diagram specific configurations. So, directives are applied on top of the default configurations. The beauty of directives is that you can use them to alter configuration settings for a specific diagram, i.e. at an individual level.
+
+While directives allow you to change most of the default configuration settings, there are some that are not available, that too for security reasons. Also, you do have the _option to define the set of configurations_ that you would allow to be available to the diagram author for overriding with help of directives.
+
+## Types of Directives options
+
+Mermaid basically supports two types of configuration options to be overridden by directives.
+
+1. _General/Top Level configurations_ : These are the configurations that are available and applied to all the diagram. **Some of the most important top-level** configurations are:
+
+- theme
+- fontFamily
+- logLevel
+- securityLevel
+- startOnLoad
+- secure
+
+2. _Diagram specific configurations_ : These are the configurations that are available and applied to a specific diagram. For each diagram there are specific configuration that will alter how that particular diagram looks and behaves.
+ For example, `mirrorActors` is a configuration that is specific to the `SequenceDiagram` and alter whether the actors are mirrored or not. So this config is available only for the `SequenceDiagram` type.
+
+**NOTE:** These options listed here are not all the configuration options. To get hold of all the configuration options, please refer to the [defaultConfig.js](https://github.com/mermaid-js/mermaid/blob/develop/src/defaultConfig.js) in the source code.
+
+```
+Soon we plan to publish a complete list of top-level configurations & all the diagram specific configurations, with their possible values in the docs
+```
+
+## Declaring directives
+
+Now that we have defined the types of configurations that are available, we can learn how to declare directives.
+A directive always starts and end `%%` sign with directive text in between, like `%% {directive_text} %%`.
+
+Here the structure of a directive text is like a nested key-value pair map or a JSON object with root being _init_. Where all the general configurations are defined in the top level, and all the diagram specific configurations are defined one level deeper with diagram type as key/root for that section.
+
+Following code snippet shows the structure of a directive:
+
+```
+%%{
+ init: {
+ "theme": "dark",
+ "fontFamily": "monospace",
+ "logLevel": "info",
+ "flowchart": {
+ "htmlLabels": true,
+ "curve": "linear"
+ },
+ "sequence": {
+ "mirrorActors": true
+ }
+ }
+}%%
+```
+
+You can also define the directives in a single line, like this:
+
+```
+%%{init: { **insert argument here**}}%%
+```
+
+For example, the following code snippet:
+
+```
+%%{init: { "sequence": { "mirrorActors":false }}}%%
+```
+
+**Notes:**
+The json object that is passed as {**argument** } must be valid key value pairs and encased in quotation marks or it will be ignored.
+Valid Key Value pairs can be found in config.
+
+Example with a simple graph:
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'dark' } }%%
+graph LR
+A-->B
+```
+
+Here the directive declaration will set the `logLevel` to `debug` and the `theme` to `dark` for a rendered mermaid diagram, changing the appearance of the diagram itself.
+
+Note: You can use 'init' or 'initialize' as both acceptable as init directives. Also note that `%%init%%` and `%%initialize%%` directives will be grouped together after they are parsed. This means:
+
+```mmd
+%%{init: { 'logLevel': 'debug', 'theme': 'forest' } }%%
+%%{initialize: { 'logLevel': 'fatal', "theme":'dark', 'startOnLoad': true } }%%
+...
+```
+
+parsing the above generates a single `%%init%%` JSON object below, combining the two directives and carrying over the last value given for `loglevel`:
+
+```json
+{
+ "logLevel": "fatal",
+ "theme": "dark",
+ "startOnLoad": true
+}
+```
+
+This will then be sent to `mermaid.initialize(...)` for rendering.
+
+## Directive Examples
+
+More directive examples for diagram specific configuration overrides
+Now that the concept of directives has been explained, Let us see some more examples for directives usage:
+
+### Changing Theme via directive
+
+The following code snippet changes theme to forest:
+
+`%%{init: { "theme": "forest" } }%%`
+
+Possible themes value are: `default`,`base`, `dark`, `forest` and `neutral`.
+Default Value is `default`.
+
+Example:
+
+```mermaid-example
+%%{init: { "theme": "forest" } }%%
+graph TD
+A(Forest) --> B[/Another/]
+A --> C[End]
+ subgraph section
+ B
+ C
+ end
+
+```
+
+### Changing fontFamily via directive
+
+The following code snippet changes fontFamily to rebuchet MS, Verdana, Arial, Sans-Serif:
+
+`%%{init: { "fontFamily": "Trebuchet MS, Verdana, Arial, Sans-Serif" } }%%`
+
+Example:
+
+```mermaid-example
+%%{init: { "fontFamily": "Trebuchet MS, Verdana, Arial, Sans-Serif" } }%%
+graph TD
+A(Forest) --> B[/Another/]
+A --> C[End]
+ subgraph section
+ B
+ C
+ end
+
+```
+
+### Changing logLevel via directive
+
+The following code snippet changes logLevel to 2:
+
+`%%{init: { "logLevel": 2 } }%%`
+
+Possible logLevel values are:
+
+- `1` for _debug_,
+- `2` for _info_
+- `3` for _warn_
+- `4` for _error_
+- `5` for _only fatal errors_
+
+Default Value is `5`.
+
+Example:
+
+```mermaid-example
+%%{init: { "logLevel": 2 } }%%
+graph TD
+A(Forest) --> B[/Another/]
+A --> C[End]
+ subgraph section
+ B
+ C
+ end
+```
+
+### Changing flowchart config via directive
+
+Some common flowchart configurations are:
+
+- _htmlLabels_: true/false
+- _curve_: linear/curve
+- _diagramPadding_: number
+- _useMaxWidth_: number
+
+For complete list of flowchart configurations, see [defaultConfig.js](https://github.com/mermaid-js/mermaid/blob/develop/src/defaultConfig.js) in the source code.
+_Soon we plan to publish a complete list all diagram specific configurations updated in the docs_
+
+The following code snippet changes flowchart config:
+
+`%%{init: { "flowchart": { "htmlLabels": true, "curve": "linear" } } }%%`
+
+Here were are overriding only the flowchart config, and not the general config, where HtmlLabels is set to true and curve is set to linear.
+
+```mermaid-example
+%%{init: { "flowchart": { "htmlLabels": true, "curve": "linear" } } }%%
+graph TD
+A(Forest) --> B[/Another/]
+A --> C[End]
+ subgraph section
+ B
+ C
+ end
+```
+
+### Changing Sequence diagram config via directive
+
+Some common sequence configurations are:
+
+- _width_: number
+- _height_: number
+- _messageAlign_: left, center, right
+- _mirrorActors_: boolean
+- _useMaxWidth_: boolean
+- _rightAngles_: boolean
+- _showSequenceNumbers_: boolean
+- _wrap_: boolean
+
+For complete list of sequence diagram configurations, see _defaultConfig.js_ in the source code.
+_Soon we plan to publish a complete list all diagram specific configurations updated in the docs_
+
+So, `wrap` by default has a value of `false` for sequence diagrams.
+
+Let us see an example:
+
+```mermaid-example
+sequenceDiagram
+
+Alice->Bob: Hello Bob, how are you?
+Bob->Alice: Fine, How did you mother like the book I suggested? And did you catch with the new book about alien invasion?
+Alice->Bob: Good.
+Bob->Alice: Cool
+```
+
+Now let us enable wrap for sequence diagrams.
+
+The following code snippet changes sequence diagram config for `wrap` to `true`:
+
+`%%{init: { "sequence": { "wrap": true} } }%%`
+
+Using in the diagram above, the wrap will be enabled.
+
+```mermaid-example
+%%{init: { "sequence": { "wrap": true, "width":300 } } }%%
+sequenceDiagram
+Alice->Bob: Hello Bob, how are you?
+Bob->Alice: Fine, How did you mother like the book I suggested? And did you catch with the new book about alien invasion?
+Alice->Bob: Good.
+Bob->Alice: Cool
+```
diff --git a/vdocs/config/img/accessibility-div-example-2.png b/vdocs/config/img/accessibility-div-example-2.png
new file mode 100644
index 0000000000..b257edbd03
Binary files /dev/null and b/vdocs/config/img/accessibility-div-example-2.png differ
diff --git a/vdocs/config/img/accessibility-div-example.png b/vdocs/config/img/accessibility-div-example.png
new file mode 100644
index 0000000000..2b3478f0bd
Binary files /dev/null and b/vdocs/config/img/accessibility-div-example.png differ
diff --git a/vdocs/config/img/assignWithDepth.png b/vdocs/config/img/assignWithDepth.png
new file mode 100644
index 0000000000..d00e8eb7c9
Binary files /dev/null and b/vdocs/config/img/assignWithDepth.png differ
diff --git a/vdocs/config/img/object.assign without depth.png b/vdocs/config/img/object.assign without depth.png
new file mode 100644
index 0000000000..c87505c1c1
Binary files /dev/null and b/vdocs/config/img/object.assign without depth.png differ
diff --git a/vdocs/config/img/python-mermaid-integration.png b/vdocs/config/img/python-mermaid-integration.png
new file mode 100644
index 0000000000..d54a0e97d5
Binary files /dev/null and b/vdocs/config/img/python-mermaid-integration.png differ
diff --git a/vdocs/config/img/wrapped text.png b/vdocs/config/img/wrapped text.png
new file mode 100644
index 0000000000..cf8dd12386
Binary files /dev/null and b/vdocs/config/img/wrapped text.png differ
diff --git a/vdocs/config/mermaidCLI.md b/vdocs/config/mermaidCLI.md
new file mode 100644
index 0000000000..f9473f1dd3
--- /dev/null
+++ b/vdocs/config/mermaidCLI.md
@@ -0,0 +1,3 @@
+# mermaid CLI
+
+mermaid CLI has been moved to [mermaid-cli](https://github.com/mermaid-js/mermaid-cli). Please read its documentation instead.
diff --git a/vdocs/config/n00b-advanced.md b/vdocs/config/n00b-advanced.md
new file mode 100644
index 0000000000..1e6546f5cf
--- /dev/null
+++ b/vdocs/config/n00b-advanced.md
@@ -0,0 +1,24 @@
+# Advanced n00b mermaid (Coming soon..)
+
+## splitting mermaid code from html
+
+A more condensed html code can be achieved by embedding the mermaid code in its own .js file, which is referenced like so:
+
+```
+stuff stuff
+ </div>
+ </body>
+</html>
+```
+
+The actual mermaid file could for example look like this:
+
+```
+mermaid content...
+```
+
+---
+
+## mermaid configuration options
+
+...
diff --git a/vdocs/config/n00b-syntaxReference.md b/vdocs/config/n00b-syntaxReference.md
new file mode 100644
index 0000000000..7db4de5b7a
--- /dev/null
+++ b/vdocs/config/n00b-syntaxReference.md
@@ -0,0 +1,67 @@
+# Diagram Syntax
+
+Mermaid's syntax is used to create diagrams. You'll find that it is not too tricky and can be learned in a day. The next sections dive deep into the syntax of each diagram type.
+
+Syntax, together with Deployment and Configuration constitute the whole of Mermaid.
+
+Diagram Examples can be found in the [Mermaid Live Editor](https://mermaid-js.github.io/mermaid-live-editor), it is also a great practice area.
+
+## Syntax Structure
+
+One would notice that all **Diagrams definitions begin** with a declaration of the **diagram type**, followed by the definitions of the diagram and its contents. This declaration notifies the parser which kind of diagram the code is supposed to generate.
+
+**Example** : The code below is for an Entity Relationship Diagram, specified by the `erDiagram` declaration. What follows is the definition of the different `Entities` represented in it.
+
+```mermaid-example
+erDiagram
+ CUSTOMER }|..|{ DELIVERY-ADDRESS : has
+ CUSTOMER ||--o{ ORDER : places
+ CUSTOMER ||--o{ INVOICE : "liable for"
+ DELIVERY-ADDRESS ||--o{ ORDER : receives
+ INVOICE ||--|{ ORDER : covers
+ ORDER ||--|{ ORDER-ITEM : includes
+ PRODUCT-CATEGORY ||--|{ PRODUCT : contains
+ PRODUCT ||--o{ ORDER-ITEM : "ordered in"
+```
+
+The [Getting Started](../intro/n00b-gettingStarted.md) section can also provide some practical examples of mermaid syntax.
+
+## Diagram Breaking
+
+One should **beware the use of some words or symbols** that can break diagrams. These words or symbols are few and often only affect specific types of diagrams. The table below will continuously be updated.
+
+| Diagram Breakers | Reason | Solution |
+| -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------- |
+| **Comments** | | |
+| [` %%{``}%% `](https://github.com/mermaid-js/mermaid/issues/1968) | Similar to [Directives](./directives.md) confuses the renderer. | In comments using `%%`, avoid using "{}". |
+| **Flow-Charts** | | |
+| 'end' | The word "End" can cause Flowcharts and Sequence diagrams to break | Wrap them in quotation marks to prevent breakage. |
+| [Nodes inside Nodes](https://mermaid-js.github.io/mermaid/#/flowchart?id=special-characters-that-break-syntax) | Mermaid gets confused with nested shapes | wrap them in quotation marks to prevent breaking |
+
+### Mermaid Live Editor
+
+Now, that you've seen what you should not add to your diagrams, you can play around with them in the [Mermaid Live Editor](https://mermaid-js.github.io/mermaid-live-editor).
+
+# Configuration
+
+Configuration is the third part of Mermaid, after deployment and syntax. It deals with the different ways that Mermaid can be customized across different deployments.
+
+If you are interested in altering and customizing your Mermaid Diagrams, you will find the methods and values available for [Configuration](../config/Setup.md) here. It includes themes.
+This section will introduce the different methods of configuring the behaviors and appearances of Mermaid Diagrams.
+The following are the most commonly used methods, and they are all tied to Mermaid [Deployment](../intro/n00b-gettingStarted.md) methods.
+
+### Configuration Section in the [Live Editor](https://mermaid-js.github.io/mermaid-live-editor).
+
+Here you can edit certain values to change the behavior and appearance of the diagram.
+
+### [The initialize() call](../intro/n00b-gettingStarted?id=_3-calling-the-javascript-api),
+
+Used when Mermaid is called via an API, or through a `<script>` tag.
+
+### [Directives](../config/directives.md),
+
+Allows for the limited reconfiguration of a diagram just before it is rendered. It can alter the font style, color and other aesthetic aspects of the diagram. You can pass a directive alongside your definition inside `%%{ }%%`. It can be done either above or below your diagram definition.
+
+### [Theme Manipulation](../config/theming.md):
+
+An application of using Directives to change [Themes](../config/theming.md). `Theme` is a value within Mermaid's configuration that dictates the color scheme for diagrams.
diff --git a/vdocs/config/theming.md b/vdocs/config/theming.md
new file mode 100644
index 0000000000..16bb2ef953
--- /dev/null
+++ b/vdocs/config/theming.md
@@ -0,0 +1,484 @@
+# Theme Configuration
+
+With Version 8.7.0 Mermaid comes out with a system for dynamic and integrated configuration of themes. The intent is to increase the customizability and ease of styling for mermaid diagrams.
+
+The theme can be altered by changing the root level variable `theme` variable in the configuration. To change it for the whole site you must use the `initialize` call. To do it for just for a single diagram you can use the `%%init%%` directive
+
+Themes follow and build upon the Levels of Configuration, and employ `directives` to modify and create custom configurations, as they were introduced in Version [8.6.0](./8.6.0_docs.md).
+
+## Deployable Themes
+
+The following are a list of **Deployable themes**, sample `%%init%%` directives and `initialize` calls.
+
+1. **base**- Designed to be modified, as the name implies it is supposed to be used as the base for making custom themes.
+
+2. **forest**- A theme full of light greens that is easy on the eyes.
+
+3. **dark**- A theme that would go well with other dark-colored elements.
+
+4. **default**- The default theme for all diagrams.
+
+5. **neutral**- The theme to be used for black and white printing.
+
+## Site-wide Themes
+
+Site-wide themes are declared via `initialize` by site owners.
+
+Example of `Initialize` call setting `theme` to `base`:
+
+```javascript
+mermaidAPI.initialize({
+ securityLevel: 'loose',
+ theme: 'base',
+});
+```
+
+**Notes**: Only site owners can use the `mermaidAPI.initialize` call, to set values. Site-Users will have to use `%%init%%` to modify or create the theme for their diagrams.
+
+## Themes at the Local or Current Level
+
+When Generating a diagram using on a webpage that supports mermaid. It is also possible to override site-wide theme settings locally, for a specific diagram, using directives, as long as it is not prohibited by the `secure` array.
+
+```mmd
+%%{init: {'theme':'neutral'}}%%
+ graph TD
+ a --> b
+```
+
+Here is an example of how `%%init%%` can set the theme to 'neutral', this assumes that `themeVariables` are set to default:
+
+```mermaid-example
+%%{init: {'theme':'neutral'}}%%
+ graph TD
+ A[Christmas] -->|Get money| B(Go shopping)
+ B --> C{Let me think}
+ B --> G[/Another/]
+ C ==>|One| D[Laptop]
+ C -->|Two| E[iPhone]
+ C -->|Three| F[fa:fa-car Car]
+ subgraph section
+ C
+ D
+ E
+ F
+ G
+ end
+```
+
+# List of Themes
+
+# Customizing Themes with `themeVariables`
+
+The easiest way to make a custom theme is to start with the base theme, and just modify theme variables through `themeVariables`, via `%%init%%`.
+
+| Parameter | Description | Type | Required | Objects contained |
+| -------------- | ------------------------------------------------------------------ | ----- | -------- | ---------------------------------- |
+| themeVariables | Array containing objects, modifiable with the `%%init%%` directive | Array | Required | primaryColor, lineColor, textColor |
+
+**Here is an example of overriding `primaryColor` through `themeVariables` and giving everything a different look, using `%%init%%`.**
+
+```mermaid-example
+%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#ff0000'}}}%%
+ graph TD
+ A[Christmas] -->|Get money| B(Go shopping)
+ B --> C{Let me think}
+ B --> G[/Another/]
+ C ==>|One| D[Laptop]
+ C -->|Two| E[iPhone]
+ C -->|Three| F[fa:fa-car Car]
+ subgraph section
+ C
+ D
+ E
+ F
+ G
+ end
+```
+
+**Notes:**
+Leaving it empty will set all variable values to default.
+
+## Color and Color Calculation:
+
+Color definitions have certain interactions in mermaid, this is in order to ensure visibility for diagrams. Mermaid will adjust some variables automatically, when colors are changed in order to compensate and maintain readability.
+
+**The Default Value Column** to the right of the Variable column will denote the Variable paired/associated with the Variable on the left and the nature of this pairing or association. If it for instance says primaryColor it means that it gets primaryColor as default value. If it says "based on primaryColor" it means that it is calculated/ derived from primaryColor. This calculation can be primary color inversion, a change of hue, darkening or lightening by 10%, etc.
+
+You can create your own themes, by changing any of the given variables below. If you are using a dark background, set dark mode to true to adjust the colors. It is possible to override the calculations using the variable names below, with `%%init%%` if you wish to style it differently.
+
+## Theme Variables Reference Table
+
+::: tip
+Variables that are unique to some diagrams can be affected by changes in Theme Variables
+:::
+
+| Variable | Default/Base/Factor value | Calc | Description |
+| -------------------- | ------------------------------ | ---- | -------------------------------------------------------------------------------------------------------------------------------- |
+| darkMode | false | | Boolean Value that dictates how to calculate colors. "true" will activate darkmode. |
+| background | #f4f4f4 | | Used to calculate color for items that should either be background colored or contrasting to the background. |
+| fontFamily | "trebuchet ms", verdana, arial | | |
+| fontSize | 16px | | Font Size, in pixels |
+| primaryColor | #fff4dd | | Color to be used as background in nodes, other colors will be derived from this |
+| primaryBorderColor | based on primaryColor | \* | Color to be used as border in nodes using primaryColor |
+| primaryTextColor | based on darkMode #ddd/#333 | \* | Color to be used as text color in nodes using primaryColor |
+| secondaryColor | based on primaryColor | \* | |
+| secondaryBorderColor | based on secondaryColor | \* | Color to be used as border in nodes using secondaryColor |
+| secondaryTextColor | based on secondaryColor | \* | Color to be used as text color in nodes using secondaryColor |
+| tertiaryColor | based on primaryColor | \* | |
+| tertiaryBorderColor | based on tertiaryColor | \* | Color to be used as border in nodes using tertiaryColor |
+| tertiaryTextColor | based on tertiaryColor | \* | Color to be used as text color in nodes using tertiaryColor |
+| noteBkgColor | #fff5ad | | Color used as background in notes |
+| noteTextColor | #333 | | Text color in note rectangles. |
+| noteBorderColor | based on noteBkgColor | \* | Border color in note rectangles. |
+| lineColor | based on background | \* | |
+| textColor | based on primaryTextColor | \* | Text in diagram over the background for instance text on labels and on signals in sequence diagram or the title in gantt diagram |
+| mainBkg | based on primaryColor | \* | Background in flowchart objects like rects/circles, class diagram classes, sequence diagram etc |
+| errorBkgColor | tertiaryColor | \* | Color for syntax error message |
+| errorTextColor | tertiaryTextColor | \* | Color for syntax error message |
+
+# What follows are Variables, specific to different diagrams and charts.
+
+## Some Theme Variables serve as, or affect the Default Values for Specific Diagram Variables, unless changed using `%%init%%` .
+
+## Flowchart
+
+| Variable | Default/ Associated Value | Calc | Description |
+| ------------------- | ------------------------- | ---- | ---------------------------- |
+| nodeBorder | primaryBorderColor | \* | Node Border Color |
+| clusterBkg | tertiaryColor | \* | Background in subgraphs |
+| clusterBorder | tertiaryBorderColor | \* | Cluster Border Color |
+| defaultLinkColor | lineColor | \* | Link Color |
+| titleColor | tertiaryTextColor | \* | Title Color |
+| edgeLabelBackground | based on secondaryColor | \* | |
+| nodeTextColor | primaryTextColor | \* | Color for text inside Nodes. |
+
+# sequence diagram
+
+| name | Default value | Calc | Description |
+| --------------------- | ----------------------- | ---- | --------------------------- |
+| actorBorder | primaryBorderColor | \* | Actor Border Color |
+| actorBkg | mainBkg | \* | Actor Background Color |
+| actorTextColor | primaryTextColor | \* | Actor Text Color |
+| actorLineColor | grey | \* | Actor Line Color |
+| signalColor | textColor | \* | Signal Color |
+| signalTextColor | textColor | \* | Signal Text Color |
+| labelBoxBkgColor | actorBkg | \* | Label Box Background Color |
+| labelBoxBorderColor | actorBorder | \* | Label Box Border Color |
+| labelTextColor | actorTextColor | \* | Label Text Color |
+| loopTextColor | actorTextColor | \* | Loop ext Color |
+| activationBorderColor | based on secondaryColor | \* | Activation Border Color |
+| activationBkgColor | secondaryColor | \* | Activation Background Color |
+| sequenceNumberColor | based on lineColor | \* | Sequence Number Color |
+
+# state colors
+
+| name | Default value | Calc | Description |
+| ------------- | ---------------- | ---- | -------------------------------------------- |
+| labelColor | primaryTextColor | \* | |
+| altBackground | tertiaryColor | \* | Used for background in deep composite states |
+
+# class colors
+
+| name | Default value | Calc | Description |
+| --------- | ------------- | ---- | ------------------------------- |
+| classText | textColor | \* | Color of Text in class diagrams |
+
+# User journey colors
+
+| name | Default value | Calc | Description |
+| --------- | ----------------------- | ---- | --------------------------------------- |
+| fillType0 | primaryColor | \* | Fill for 1st section in journey diagram |
+| fillType1 | secondaryColor | \* | Fill for 2nd section in journey diagram |
+| fillType2 | based on primaryColor | \* | Fill for 3rd section in journey diagram |
+| fillType3 | based on secondaryColor | \* | Fill for 4th section in journey diagram |
+| fillType4 | based on primaryColor | \* | Fill for 5th section in journey diagram |
+| fillType5 | based on secondaryColor | \* | Fill for 6th section in journey diagram |
+| fillType6 | based on primaryColor | \* | Fill for 7th section in journey diagram |
+| fillType7 | based on secondaryColor | \* | Fill for 8th section in journey diagram |
+
+\*\*Notes: Values are meant to create an alternating look.
+
+# Here is an example of overriding `primaryColor` and giving everything a different look, using `%%init%%`.
+
+```mermaid-example
+%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#ff0000'}}}%%
+ graph TD
+ A[Christmas] -->|Get money| B(Go shopping)
+ B --> C{Let me think}
+ B --> G[/Another/]
+ C ==>|One| D[Laptop]
+ C -->|Two| E[iPhone]
+ C -->|Three| F[fa:fa-car Car]
+ subgraph section
+ C
+ D
+ E
+ F
+ G
+ end
+```
+
+\*\*This got a bit too dark and bit too colorful. With some easy steps this can be fixed:
+
+- Make the primary color a little lighter
+- set the tertiary color to a reddish shade as well
+- make the edge label background differ from the subgraph by setting the edgeLabelBackground
+
+```mermaid-example
+%%{init: {'theme': 'base', 'themeVariables': { 'primaryColor': '#ffcccc', 'edgeLabelBackground':'#ffffee', 'tertiaryColor': '#fff0f0'}}}%%
+ graph TD
+ A[Christmas] -->|Get money| B(Go shopping)
+ B --> C{Let me think}
+ B --> G[/Another/]
+ C ==>|One| D[Laptop]
+ C -->|Two| E[iPhone]
+ C -->|Three| F[fa:fa-car Car]
+ subgraph section
+ C
+ D
+ E
+ F
+ G
+ end
+```
+
+The Theming Engine does not admit color codes and will only accept proper color values. Color Names is not supported so for instance, the color value 'red' will not work, but '#ff0000' will work.
+
+# Common theming activities
+
+## How to change the color of the arrows
+
+# Examples:
+
+When adjusting a theme it might be helpful to look at how your preferred theme goes with the diagrams, to evaluate whether everything is visible and looks good.
+In the following examples, the directive `init` is used, with the `theme` being declared as `neutral`. For more information on using directives, read the documentation for [Version 8.6.0](/8.6.0_docs.md)
+
+### Flowchart
+
+```mmd
+%%{init: {'securityLevel': 'loose', 'theme':'neutral'}}%%
+ graph TD
+ A[Christmas] -->|Get money| B(Go shopping)
+ B --> C{Let me think}
+ B --> G[/Another/]
+ C ==>|One| D[Laptop]
+ C -->|Two| E[iPhone]
+ C -->|Three| F[fa:fa-car Car]
+ subgraph section
+ C
+ D
+ E
+ F
+ G
+ end
+```
+
+```mermaid
+%%{init: {'securityLevel': 'loose', 'theme':'neutral'}}%%
+ graph TD
+ A[Christmas] -->|Get money| B(Go shopping)
+ B --> C{Let me think}
+ B --> G[/Another/]
+ C ==>|One| D[Laptop]
+ C -->|Two| E[iPhone]
+ C -->|Three| F[fa:fa-car Car]
+ subgraph section
+ C
+ D
+ E
+ F
+ G
+ end
+```
+
+### Flowchart (beta)
+
+```mermaid-example
+%%{init: {'securityLevel': 'loose', 'theme':'neutral'}}%%
+ flowchart TD
+ A[Christmas] -->|Get money| B(Go shopping)
+ B --> C{Let me think}
+ B --> G[Another]
+ C ==>|One| D[Laptop]
+ C x--x|Two| E[iPhone]
+ C o--o|Three| F[fa:fa-car Car]
+ subgraph section
+ C
+ D
+ E
+ F
+ G
+ end
+```
+
+### Sequence diagram
+
+```mermaid-example
+%%{init: {'securityLevel': 'loose', 'theme':'neutral'}}%%
+ sequenceDiagram
+ autonumber
+ par Action 1
+ Alice->>John: Hello John, how are you?
+ and Action 2
+ Alice->>Bob: Hello Bob, how are you?
+ end
+ Alice->>+John: Hello John, how are you?
+ Alice->>+John: John, can you hear me?
+ John-->>-Alice: Hi Alice, I can hear you!
+ Note right of John: John is perceptive
+ John-->>-Alice: I feel great!
+ loop Every minute
+ John-->Alice: Great!
+ end
+```
+
+### Class diagram
+
+```mermaid-example
+%%{init: {'securityLevel': 'loose', 'theme':'neutral'}}%%
+
+classDiagram
+ Animal "1" <|-- Duck
+ Animal <|-- Fish
+ Animal <--o Zebra
+ Animal : +int age
+ Animal : +String gender
+ Animal: +isMammal()
+ Animal: +mate()
+ class Duck{
+ +String beakColor
+ +swim()
+ +quack()
+ }
+ class Fish{
+ -int sizeInFeet
+ -canEat()
+ }
+ class Zebra{
+ +bool is_wild
+ +run()
+ }
+```
+
+### Gantt
+
+```mermaid-example
+gantt
+ dateFormat YYYY-MM-DD
+ title Adding GANTT diagram functionality to mermaid
+ excludes :excludes the named dates/days from being included in a charted task..
+ section A section
+ Completed task :done, des1, 2014-01-06,2014-01-08
+ Active task :active, des2, 2014-01-09, 3d
+ Future task : des3, after des2, 5d
+ Future task2 : des4, after des3, 5d
+
+ section Critical tasks
+ Completed task in the critical line :crit, done, 2014-01-06,24h
+ Implement parser and jison :crit, done, after des1, 2d
+ Create tests for parser :crit, active, 3d
+ Future task in critical line :crit, 5d
+ Create tests for renderer :2d
+ Add to mermaid :1d
+
+ section Documentation
+ Describe gantt syntax :active, a1, after des1, 3d
+ Add gantt diagram to demo page :after a1 , 20h
+ Add another diagram to demo page :doc1, after a1 , 48h
+
+ section Last section
+ Describe gantt syntax :after doc1, 3d
+ Add gantt diagram to demo page :20h
+ Add another diagram to demo page :48h
+```
+
+### State diagram
+
+```mermaid-example
+%%{init: {'securityLevel': 'loose', 'theme':'neutral'}}%%
+ stateDiagram
+ [*] --> Active
+
+ state Active {
+ [*] --> NumLockOff
+ NumLockOff --> NumLockOn : EvNumLockPressed
+ NumLockOn --> NumLockOff : EvNumLockPressed
+ --
+ [*] --> CapsLockOff
+ CapsLockOff --> CapsLockOn : EvCapsLockPressed
+ CapsLockOn --> CapsLockOff : EvCapsLockPressed
+ --
+ [*] --> ScrollLockOff
+ ScrollLockOff --> ScrollLockOn : EvCapsLockPressed
+ ScrollLockOn --> ScrollLockOff : EvCapsLockPressed
+ }
+ state SomethingElse {
+ A --> B
+ B --> A
+ }
+
+ Active --> SomethingElse
+ note right of SomethingElse : This is the note to the right.
+
+ SomethingElse --> [*]
+
+```
+
+### State diagram (beta)
+
+```mermaid-example
+%%{init: {'securityLevel': 'loose', 'theme':'neutral'}}%%
+stateDiagram-v2
+ [*] --> Active
+
+ state Active {
+ [*] --> NumLockOff
+ NumLockOff --> NumLockOn : EvNumLockPressed
+ NumLockOn --> NumLockOff : EvNumLockPressed
+ --
+ [*] --> CapsLockOff
+ CapsLockOff --> CapsLockOn : EvCapsLockPressed
+ CapsLockOn --> CapsLockOff : EvCapsLockPressed
+ --
+ [*] --> ScrollLockOff
+ ScrollLockOff --> ScrollLockOn : EvCapsLockPressed
+ ScrollLockOn --> ScrollLockOff : EvCapsLockPressed
+ }
+ state SomethingElse {
+ A --> B
+ B --> A
+ }
+
+ Active --> SomethingElse2
+ note right of SomethingElse2 : This is the note to the right.
+
+ SomethingElse2 --> [*]
+```
+
+### Entity Relations diagram
+
+```mermaid-example
+ erDiagram
+ CUSTOMER }|..|{ DELIVERY-ADDRESS : has
+ CUSTOMER ||--o{ ORDER : places
+ CUSTOMER ||--o{ INVOICE : "liable for"
+ DELIVERY-ADDRESS ||--o{ ORDER : receives
+ INVOICE ||--|{ ORDER : covers
+ ORDER ||--|{ ORDER-ITEM : includes
+ PRODUCT-CATEGORY ||--|{ PRODUCT : contains
+ PRODUCT ||--o{ ORDER-ITEM : "ordered in"
+```
+
+### User journey diagram
+
+```mermaid-example
+journey
+ title My working day
+ section Go to work
+ Make tea: 5: Me
+ Go upstairs: 3: Me
+ Do work: 1: Me, Cat
+ section Go home
+ Go downstairs: 5: Me
+ Sit down: 5: Me
+```
diff --git a/vdocs/config/usage.md b/vdocs/config/usage.md
new file mode 100644
index 0000000000..10b3b72389
--- /dev/null
+++ b/vdocs/config/usage.md
@@ -0,0 +1,398 @@
+# Usage
+
+Mermaid is a JavaScript tool that makes use of a Markdown based syntax to render customizable diagrams, charts and visualizations.
+
+Diagrams can be re-rendered/modified by modifying their descriptions.
+
+### CDN
+
+[https://unpkg.com/mermaid/](https://unpkg.com/mermaid/)
+
+Please note that you can switch versions through the dropdown box at the top right.
+
+## Using mermaid
+
+For the majority of users, Using the [Live Editor](https://mermaid.live/) would be sufficient, however you may also opt to deploy mermaid as a dependency or using the [Mermaid API](./Setup.md).
+
+We have compiled some Video [Tutorials](./Tutorials.md) on how to use the mermaid Live Editor.
+
+**Installing and Hosting Mermaid on a Webpage**
+
+**Using the npm package**
+
+```
+1. You will need to install node v16, which would have npm.
+
+2. download yarn using npm.
+
+3. enter the following command:
+ yarn add mermaid
+
+4. At this point, you can add mermaid as a dev dependency using this command:
+ yarn add --dev mermaid
+
+5. Alternatively, you can also deploy mermaid using the script tag in an HTML file with mermaid diagram descriptions.
+ as is shown in the example below
+```
+
+**Hosting mermaid on a web page.**
+
+> Note:This topic explored in greater depth in the [User Guide for Beginners](../intro/n00b-gettingStarted.md)
+
+The easiest way to integrate mermaid on a web page requires three elements:
+
+1. Inclusion of the mermaid address in the html page using a `script` tag, in the `src` section.Example:
+
+ ```html
+ <script src="https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js"></script>
+ ```
+
+2. The `mermaidAPI` call, in a separate `script` tag. Example:
+
+ ```html
+ <script>
+ mermaid.initialize({ startOnLoad: true });
+ </script>
+ ```
+
+3. A graph definition, inside `<div>` tags labeled `class=mermaid`. Example:
+
+```html
+<pre class="mermaid">
+ graph LR
+ A --- B
+ B-->C[fa:fa-ban forbidden]
+ B-->D(fa:fa-spinner);
+</pre>
+```
+
+**Following these directions, mermaid starts at page load and (when the page has loaded) it will
+locate the graph definitions inside the `div` tags with `class="mermaid"` and return diagrams in SVG form, following given definitions.**
+
+## Simple full example:
+
+```html
+<!DOCTYPE html>
+<html lang="en">
+ <head>
+ <meta charset="utf-8" />
+ </head>
+ <body>
+ <pre class="mermaid">
+ graph LR
+ A --- B
+ B-->C[fa:fa-ban forbidden]
+ B-->D(fa:fa-spinner);
+ </pre>
+ <script src="https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js"></script>
+ <script>
+ mermaid.initialize({ startOnLoad: true });
+ </script>
+ </body>
+</html>
+```
+
+## Notes:
+
+An id attribute is also added to mermaid tags without one.
+
+Mermaid can load multiple diagrams, in the same page.
+
+> Try it out, save this code as HTML and load it using any browser.(Except Internet Explorer, please don't use Internet Explorer.)
+
+## Enabling Click Event and Tags in Nodes
+
+A `securityLevel` configuration has to first be cleared, `securityLevel` sets the level of trust for the parsed diagrams and limits click functionality. This was introduce in version 8.2 as a security improvement, aimed at preventing malicious use.
+
+**It is the site owner's responsibility to discriminate between trustworthy and untrustworthy user-bases and we encourage the use of discretion.**
+
+## securityLevel
+
+| Parameter | Description | Type | Required | Values |
+| ------------- | --------------------------------- | ------ | -------- | ------------------------------------------ |
+| securityLevel | Level of trust for parsed diagram | String | Required | 'sandbox', 'strict', 'loose', 'antiscript' |
+
+Values:
+
+- **strict**: (**default**) tags in text are encoded, click functionality is disabled
+- **loose**: tags in text are allowed, click functionality is enabled
+- **antiscript**: html tags in text are allowed, (only script element is removed), click functionality is enabled
+- **sandbox**: With this security level all rendering takes place in a sandboxed iframe. This prevent any JavaScript running in the context. This may hinder interactive functionality of the diagram like scripts, popups in sequence diagram or links to other tabs/targets etc.
+
+::: warning
+This changes the default behaviour of mermaid so that after upgrade to 8.2, unless the `securityLevel` is not changed, tags in flowcharts are encoded as tags and clicking is disabled.
+**sandbox** security level is still in the beta version.
+:::
+
+**If you are taking responsibility for the diagram source security you can set the `securityLevel` to a value of your choosing . This allows clicks and tags are allowed.**
+
+**To change `securityLevel`, you have to call `mermaidAPI.initialize`:**
+
+```javascript
+mermaidAPI.initialize({
+ securityLevel: 'loose',
+});
+```
+
+### Labels out of bounds
+
+If you use dynamically loaded fonts that are loaded through CSS, such as Google fonts, mermaid should wait for the
+whole page to load (dom + assets, particularly the fonts file).
+
+```javascript
+$(document).load(function () {
+ mermaid.initialize();
+});
+```
+
+or
+
+```javascript
+$(document).ready(function () {
+ mermaid.initialize();
+});
+```
+
+Not doing so will most likely result in mermaid rendering graphs that have labels out of bounds. The default integration in mermaid uses the window.load event to start rendering.
+
+If your page has other fonts in its body those might be used instead of the mermaid font. Specifying the font in your styling is a workaround for this.
+
+```css
+div.mermaid {
+ font-family: 'trebuchet ms', verdana, arial;
+}
+```
+
+### Calling `mermaid.init`
+
+By default, `mermaid.init` will be called when the document is ready, finding all elements with
+`class="mermaid"`. If you are adding content after mermaid is loaded, or otherwise need
+finer-grained control of this behavior, you can call `init` yourself with:
+
+- a configuration object
+- some nodes, as
+ - a node
+ - an array-like of nodes
+ - or W3C selector that will find your nodes
+
+Example:
+
+```javascript
+mermaid.init({ noteMargin: 10 }, '.someOtherClass');
+```
+
+Or with no config object, and a jQuery selection:
+
+```javascript
+mermaid.init(undefined, $('#someId .yetAnotherClass'));
+```
+
+::: warning
+This type of integration is deprecated. Instead the preferred way of handling more complex integration is to use the mermaidAPI instead.
+:::
+
+## Usage with webpack
+
+mermaid fully supports webpack. Here is a [working demo](https://github.com/mermaidjs/mermaid-webpack-demo).
+
+## API usage
+
+The main idea of the API is to be able to call a render function with the graph definition as a string. The render function
+will render the graph and call a callback with the resulting SVG code. With this approach it is up to the site creator to
+fetch the graph definition from the site (perhaps from a textarea), render it and place the graph somewhere in the site.
+
+The example below show an outline of how this could be used. The example just logs the resulting SVG to the JavaScript console.
+
+```html
+<script src="mermaid.js"></script>
+
+<script>
+ mermaid.mermaidAPI.initialize({ startOnLoad: false });
+ $(function () {
+ // Example of using the API var
+ element = document.querySelector('#graphDiv');
+ var insertSvg = function (svgCode, bindFunctions) {
+ element.innerHTML = svgCode;
+ };
+ var graphDefinition = 'graph TB\na-->b';
+ var graph = mermaid.mermaidAPI.render('graphDiv', graphDefinition, insertSvg);
+ });
+</script>
+```
+
+### Binding events
+
+Sometimes the generated graph also has defined interactions like tooltip and click events. When using the API one must
+add those events after the graph has been inserted into the DOM.
+
+The example code below is an extract of what mermaid does when using the API. The example shows how it is possible to
+bind events to an SVG when using the API for rendering.
+
+```javascript
+var insertSvg = function (svgCode, bindFunctions) {
+ element.innerHTML = svgCode;
+ if (typeof callback !== 'undefined') {
+ callback(id);
+ }
+ bindFunctions(element);
+};
+
+var id = 'theGraph';
+
+mermaidAPI.render(id, txt, insertSvg, element);
+```
+
+1. The graph is generated using the render call.
+2. After generation the render function calls the provided callback function, in this case it's called insertSvg.
+3. The callback function is called with two parameters, the SVG code of the generated graph and a function. This function binds events to the SVG **after** it is inserted into the DOM.
+4. Insert the SVG code into the DOM for presentation.
+5. Call the binding function that binds the events.
+
+## Example of a marked renderer
+
+This is the renderer used for transforming the documentation from Markdown to html with mermaid diagrams in the html.
+
+```javascript
+var renderer = new marked.Renderer();
+renderer.code = function (code, language) {
+ if (code.match(/^sequenceDiagram/) || code.match(/^graph/)) {
+ return '<pre class="mermaid">' + code + '</pre>';
+ } else {
+ return '<pre><code>' + code + '</code></pre>';
+ }
+};
+```
+
+Another example in CoffeeScript that also includes the mermaid script tag in the generated markup.
+
+```coffee
+marked = require 'marked'
+
+module.exports = (options) ->
+ hasMermaid = false
+ renderer = new marked.Renderer()
+ renderer.defaultCode = renderer.code
+ renderer.code = (code, language) ->
+ if language is 'mermaid'
+ html = ''
+ if not hasMermaid
+ hasMermaid = true
+ html += '<script src="'+options.mermaidPath+'"></script>'
+ html + '<pre class="mermaid">'+code+'</pre>'
+ else
+ @defaultCode(code, language)
+
+ renderer
+```
+
+## Advanced usage
+
+**Syntax validation without rendering (Work in Progress)**
+
+The **mermaid.parse(txt)** function validates graph definitions without rendering a graph. **[This function is still a work in progress](https://github.com/mermaid-js/mermaid/issues/1066), find alternatives below.**
+
+The function **mermaid.parse(txt)**, takes a text string as an argument and returns true if the definition follows mermaid's syntax and
+false if it does not. The parseError function will be called when the parse function returns false.
+
+When the parser encounters invalid syntax the **mermaid.parseError** function is called. It is possible to override this
+function in order to handle the error in an application-specific way.
+
+The code-example below in meta code illustrates how this could work:
+
+```javascript
+mermaid.parseError = function (err, hash) {
+ displayErrorInGui(err);
+};
+
+var textFieldUpdated = function () {
+ var textStr = getTextFromFormField('code');
+
+ if (mermaid.parse(textStr)) {
+ reRender(textStr);
+ }
+};
+
+bindEventHandler('change', 'code', textFieldUpdated);
+```
+
+**Alternative to mermaid.parse():**
+One effective and more future-proof method of validating your graph definitions, is to paste and render them via the [Mermaid Live Editor](https://mermaid.live/). This will ensure that your code is compliant with the syntax of Mermaid's most recent version.
+
+## Configuration
+
+Mermaid takes a number of options which lets you tweak the rendering of the diagrams. Currently there are three ways of
+setting the options in mermaid.
+
+1. Instantiation of the configuration using the initialize call
+2. _Using the global mermaid object_ - **Deprecated**
+3. _using the global mermaid_config object_ - **Deprecated**
+4. Instantiation of the configuration using the **mermaid.init** call- **Deprecated**
+
+The list above has two ways too many of doing this. Three are deprecated and will eventually be removed. The list of
+configuration objects are described [in the mermaidAPI documentation](Setup.md).
+
+## Using the `mermaidAPI.initialize`/`mermaid.initialize` call
+
+The future proof way of setting the configuration is by using the initialization call to mermaid or mermaidAPI depending
+on what kind of integration you use.
+
+```html
+<script src="../dist/mermaid.js"></script>
+<script>
+ var config = { startOnLoad: true, flowchart: { useMaxWidth: false, htmlLabels: true } };
+ mermaid.initialize(config);
+</script>
+```
+
+::: tip
+This is the preferred way of configuring mermaid.
+:::
+
+### The following methods are deprecated and are kept only for backwards compatibility.
+
+## Using the mermaid object
+
+Is it possible to set some configuration via the mermaid object. The two parameters that are supported using this
+approach are:
+
+- mermaid.startOnLoad
+- mermaid.htmlLabels
+
+```javascript
+mermaid.startOnLoad = true;
+```
+
+::: warning
+This way of setting the configuration is deprecated. Instead the preferred way is to use the initialize method. This functionality is only kept for backwards compatibility.
+:::
+
+## Using the mermaid_config
+
+It is possible to set some configuration via the mermaid object. The two parameters that are supported using this
+approach are:
+
+- mermaid_config.startOnLoad
+- mermaid_config.htmlLabels
+
+```javascript
+mermaid_config.startOnLoad = true;
+```
+
+::: warning
+This way of setting the configuration is deprecated. Instead the preferred way is to use the initialize method. This functionality is only kept for backwards compatibility.
+:::
+
+## Using the mermaid.init call
+
+To set some configuration via the mermaid object. The two parameters that are supported using this approach are:
+
+- mermaid_config.startOnLoad
+- mermaid_config.htmlLabels
+
+```javascript
+mermaid_config.startOnLoad = true;
+```
+
+::: warning
+This way of setting the configuration is deprecated. Instead the preferred way is to use the initialize method. This functionality is only kept for backwards compatibility.
+:::
diff --git a/vdocs/edit.md b/vdocs/edit.md
new file mode 100644
index 0000000000..5c623db4d2
--- /dev/null
+++ b/vdocs/edit.md
@@ -0,0 +1,7 @@
+---
+layout: home
+
+title: Live Mermaid
+---
+
+<iframe id="editor" src="https://mermaid.live" style="position: fixed;left: 0px;bottom: 0px;right: 0px;top: 80px;width: 100%;height: calc(100% - 80px);"></iframe>
diff --git a/vdocs/index.md b/vdocs/index.md
new file mode 100644
index 0000000000..cc3cd9498d
--- /dev/null
+++ b/vdocs/index.md
@@ -0,0 +1,130 @@
+---
+layout: home
+
+title: Mermaid
+titleTemplate: Diagramming and charting tool
+
+hero:
+ name: Mermaid
+ text: Diagramming and charting tool
+ tagline: JavaScript based diagramming and charting tool that renders Markdown-inspired text definitions to create and modify diagrams dynamically.
+ image:
+ src: /header.png
+ alt: Mermaid
+ actions:
+ - theme: brand
+ text: Get Started
+ link: /intro/
+ - theme: alt
+ text: View on GitHub
+ link: https://mermaid-js.github.io/mermaid/#/
+
+features:
+ - title: ➕ Easy to use!
+ details: Mermaid allows even non-programmers to easily create detailed and diagrams through the Mermaid Live Editor.
+ - title: 🎥 Video Tutorials!
+ details: Has video tutorials for beginners and advanced users.
+ - title: 🏆 Award winner!
+ details: Mermaid was nominated and won the JS Open Source Awards (2019) in the category "The most exciting use of technology"!!!
+ - title: 🧩 Integrations available!
+ details: Use Mermaid with your favorite applications, check out the list of Integrations and Usages of Mermaid.
+---
+
+<script setup>
+import { VPTeamMembers } from 'vitepress/theme'
+
+const members = [
+ {
+ avatar: 'https://avatars.githubusercontent.com/u/5837277?v=4',
+ name: 'Knut Sveidqvist',
+ title: 'Creator',
+ links: [
+ { icon: 'github', link: 'https://github.com/knsv' },
+ ]
+ },
+ {
+ avatar: 'https://avatars.githubusercontent.com/u/1912783?v=4',
+ name: 'Marc Faber',
+ title: 'Developer',
+ links: [
+ { icon: 'github', link: 'https://gdfaber.github.io/' },
+ { icon: 'linkedin', link: 'https://www.linkedin.com/in/marc-faber/' },
+ ]
+ }, {
+ avatar: 'https://avatars.githubusercontent.com/u/1564825?v=4',
+ name: 'Nacho Orlandoni',
+ title: 'Developer',
+ links: [
+ { icon: 'github', link: 'https://github.com/IOrlandoni' },
+ ]
+ }, {
+ avatar: 'https://avatars.githubusercontent.com/u/6552521?v=4',
+ name: 'Christian Klemm',
+ title: 'Developer',
+ links: [
+ { icon: 'github', link: 'https://github.com/klemmchr' },
+ ]
+ }, {
+ avatar: 'https://avatars.githubusercontent.com/u/12032557?v=4',
+ name: 'Mindaugas Laganeckas',
+ title: 'Developer',
+ links: [
+ { icon: 'github', link: 'https://github.com/MindaugasLaganeckas' },
+ ]
+ }, {
+ avatar: 'https://avatars.githubusercontent.com/u/58763315?v=4',
+ name: 'Neil Cuzon',
+ title: 'Developer',
+ links: [
+ { icon: 'github', link: 'https://github.com/NeilCuzon' },
+ ]
+ }, {
+ avatar: 'https://avatars.githubusercontent.com/u/19526120?v=4',
+ name: 'Adrian Hall',
+ title: 'Developer',
+ links: [
+ { icon: 'github', link: 'https://github.com/spopida' },
+ ]
+ }, {
+ avatar: 'https://avatars.githubusercontent.com/u/53054099?v=4',
+ name: 'Yash Singh',
+ title: 'Developer',
+ links: [
+ { icon: 'github', link: 'https://github.com/Yash-Singh1' },
+ ]
+ },
+]
+</script>
+
+<div class="vp-doc" >
+ <h2 id="meet-the-team"> Meet The Team </h2>
+ <VPTeamMembers size="small" :members="members" />
+</div>
+
+<style>
+ .image-container .image-src {
+ margin: 1rem auto;
+ max-width: 100%;
+ }
+
+ .dark .image-src{
+ filter: invert(1) hue-rotate(217deg) contrast(0.72);
+ max-width: 100%;
+ }
+
+ .vp-doc {
+ align-items: center;
+ flex-direction: column;
+ display: flex;
+ margin-top: 2.5rem;
+ }
+
+ .vp-doc h2 {
+ margin: 48px 0 16px;
+ border-top: 1px solid var(--vp-c-divider-light);
+ padding-top: 24px;
+ letter-spacing: -.02em;
+ line-height: 32px;
+ font-size: 24px;
+}
+</style>
diff --git a/vdocs/intro/directives.md b/vdocs/intro/directives.md
new file mode 100644
index 0000000000..b96a2184cb
--- /dev/null
+++ b/vdocs/intro/directives.md
@@ -0,0 +1,254 @@
+# Directives
+
+## Directives
+
+Directives gives a diagram author the capability to alter the appearance of a diagram before rendering by changing the applied configuration.
+
+The significance of having directives is that you have them available while writing the diagram, and can modify the default global and diagram specific configurations. So, directives are applied on top of the default configurations. The beauty of directives is that you can use them to alter configuration settings for a specific diagram, i.e. at an individual level.
+
+While directives allow you to change most of the default configuration settings, there are some that are not available, that too for security reasons. Also, you do have the _option to define the set of configurations_ that you would allow to be available to the diagram author for overriding with help of directives.
+
+## Types of Directives options
+
+Mermaid basically supports two types of configuration options to be overridden by directives.
+
+1. _General/Top Level configurations_ : These are the configurations that are available and applied to all the diagram. **Some of the most important top-level** configurations are:
+
+- theme
+- fontFamily
+- logLevel
+- securityLevel
+- startOnLoad
+- secure
+
+2. _Diagram specific configurations_ : These are the configurations that are available and applied to a specific diagram. For each diagram there are specific configuration that will alter how that particular diagram looks and behaves.
+ For example, `mirrorActors` is a configuration that is specific to the `SequenceDiagram` and alter whether the actors are mirrored or not. So this config is available only for the `SequenceDiagram` type.
+
+**NOTE:** These options listed here are not all the configuration options. To get hold of all the configuration options, please refer to the [defaultConfig.js](https://github.com/mermaid-js/mermaid/blob/develop/src/defaultConfig.js) in the source code.
+
+```
+Soon we plan to publish a complete list of top-level configurations & all the diagram specific configurations, with their possible values in the docs
+```
+
+## Declaring directives
+
+Now that we have defined the types of configurations that are available, we can learn how to declare directives.
+A directive always starts and end `%%` sign with directive text in between, like `%% {directive_text} %%`.
+
+Here the structure of a directive text is like a nested key-value pair map or a JSON object with root being _init_. Where all the general configurations are defined in the top level, and all the diagram specific configurations are defined one level deeper with diagram type as key/root for that section.
+
+Following code snippet shows the structure of a directive:
+
+```
+%%{
+ init: {
+ "theme": "dark",
+ "fontFamily": "monospace",
+ "logLevel": "info",
+ "flowchart": {
+ "htmlLabels": true,
+ "curve": "linear"
+ },
+ "sequence": {
+ "mirrorActors": true
+ }
+ }
+}%%
+```
+
+You can also define the directives in a single line, like this:
+
+```
+%%{init: { **insert argument here**}}%%
+```
+
+For example, the following code snippet:
+
+```
+%%{init: { "sequence": { "mirrorActors":false }}}%%
+```
+
+**Notes:**
+The json object that is passed as {**argument** } must be valid key value pairs and encased in quotation marks or it will be ignored.
+Valid Key Value pairs can be found in config.
+
+Example with a simple graph:
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'dark' } }%%
+graph LR
+A-->B
+```
+
+Here the directive declaration will set the `logLevel` to `debug` and the `theme` to `dark` for a rendered mermaid diagram, changing the appearance of the diagram itself.
+
+Note: You can use 'init' or 'initialize' as both acceptable as init directives. Also note that `%%init%%` and `%%initialize%%` directives will be grouped together after they are parsed. This means:
+
+```mmd
+%%{init: { 'logLevel': 'debug', 'theme': 'forest' } }%%
+%%{initialize: { 'logLevel': 'fatal', "theme":'dark', 'startOnLoad': true } }%%
+...
+```
+
+parsing the above generates a single `%%init%%` JSON object below, combining the two directives and carrying over the last value given for `loglevel`:
+
+```json
+{
+ "logLevel": "fatal",
+ "theme": "dark",
+ "startOnLoad": true
+}
+```
+
+This will then be sent to `mermaid.initialize(...)` for rendering.
+
+## Directive Examples
+
+More directive examples for diagram specific configuration overrides
+Now that the concept of directives has been explained, Let us see some more examples for directives usage:
+
+### Changing Theme via directive
+
+The following code snippet changes theme to forest:
+
+`%%{init: { "theme": "forest" } }%%`
+
+Possible themes value are: `default`,`base`, `dark`, `forest` and `neutral`.
+Default Value is `default`.
+
+Example:
+
+```mermaid-example
+%%{init: { "theme": "forest" } }%%
+graph TD
+A(Forest) --> B[/Another/]
+A --> C[End]
+ subgraph section
+ B
+ C
+ end
+
+```
+
+### Changing fontFamily via directive
+
+The following code snippet changes fontFamily to rebuchet MS, Verdana, Arial, Sans-Serif:
+
+`%%{init: { "fontFamily": "Trebuchet MS, Verdana, Arial, Sans-Serif" } }%%`
+
+Example:
+
+```mermaid-example
+%%{init: { "fontFamily": "Trebuchet MS, Verdana, Arial, Sans-Serif" } }%%
+graph TD
+A(Forest) --> B[/Another/]
+A --> C[End]
+ subgraph section
+ B
+ C
+ end
+```
+
+### Changing logLevel via directive
+
+The following code snippet changes logLevel to 2:
+
+`%%{init: { "logLevel": 2 } }%%`
+
+Possible logLevel values are:
+
+- `1` for _debug_,
+- `2` for _info_
+- `3` for _warn_
+- `4` for _error_
+- `5` for _only fatal errors_
+
+Default Value is `5`.
+
+Example:
+
+```mermaid-example
+%%{init: { "logLevel": 2 } }%%
+graph TD
+A(Forest) --> B[/Another/]
+A --> C[End]
+ subgraph section
+ B
+ C
+ end
+```
+
+### Changing flowchart config via directive
+
+Some common flowchart configurations are:
+
+- _htmlLabels_: true/false
+- _curve_: linear/curve
+- _diagramPadding_: number
+- _useMaxWidth_: number
+
+For complete list of flowchart configurations, see [defaultConfig.js](https://github.com/mermaid-js/mermaid/blob/develop/src/defaultConfig.js) in the source code.
+_Soon we plan to publish a complete list all diagram specific configurations updated in the docs_
+
+The following code snippet changes flowchart config:
+
+`%%{init: { "flowchart": { "htmlLabels": true, "curve": "linear" } } }%%`
+
+Here were are overriding only the flowchart config, and not the general config, where HtmlLabels is set to true and curve is set to linear.
+
+```mermaid-example
+%%{init: { "flowchart": { "htmlLabels": true, "curve": "linear" } } }%%
+graph TD
+A(Forest) --> B[/Another/]
+A --> C[End]
+ subgraph section
+ B
+ C
+ end
+```
+
+### Changing Sequence diagram config via directive
+
+Some common sequence configurations are:
+
+- _width_: number
+- _height_: number
+- _messageAlign_: left, center, right
+- _mirrorActors_: boolean
+- _useMaxWidth_: boolean
+- _rightAngles_: boolean
+- _showSequenceNumbers_: boolean
+- _wrap_: boolean
+
+For complete list of sequence diagram configurations, see _defaultConfig.js_ in the source code.
+_Soon we plan to publish a complete list all diagram specific configurations updated in the docs_
+
+So, `wrap` by default has a value of `false` for sequence diagrams.
+
+Let us see an example:
+
+```mermaid-example
+sequenceDiagram
+
+Alice->Bob: Hello Bob, how are you?
+Bob->Alice: Fine, How did you mother like the book I suggested? And did you catch with the new book about alien invasion?
+Alice->Bob: Good.
+Bob->Alice: Cool
+```
+
+Now let us enable wrap for sequence diagrams.
+
+The following code snippet changes sequence diagram config for `wrap` to `true`:
+
+`%%{init: { "sequence": { "wrap": true} } }%%`
+
+Using in the diagram above, the wrap will be enabled.
+
+```mermaid-example
+%%{init: { "sequence": { "wrap": true, "width":300 } } }%%
+sequenceDiagram
+Alice->Bob: Hello Bob, how are you?
+Bob->Alice: Fine, How did you mother like the book I suggested? And did you catch with the new book about alien invasion?
+Alice->Bob: Good.
+Bob->Alice: Cool
+```
diff --git a/vdocs/intro/img/Code-Preview-Config.png b/vdocs/intro/img/Code-Preview-Config.png
new file mode 100644
index 0000000000..426e6bf633
Binary files /dev/null and b/vdocs/intro/img/Code-Preview-Config.png differ
diff --git a/vdocs/intro/img/Live-Editor-Choices.png b/vdocs/intro/img/Live-Editor-Choices.png
new file mode 100644
index 0000000000..5b4c2086db
Binary files /dev/null and b/vdocs/intro/img/Live-Editor-Choices.png differ
diff --git a/vdocs/intro/img/book-banner-post-release.jpg b/vdocs/intro/img/book-banner-post-release.jpg
new file mode 100644
index 0000000000..9ce3cc6fc7
Binary files /dev/null and b/vdocs/intro/img/book-banner-post-release.jpg differ
diff --git a/vdocs/intro/index.md b/vdocs/intro/index.md
new file mode 100644
index 0000000000..030409c6d2
--- /dev/null
+++ b/vdocs/intro/index.md
@@ -0,0 +1,398 @@
+# About Mermaid
+
+**Mermaid lets you create diagrams and visualizations using text and code.**
+
+It is a JavaScript based diagramming and charting tool that renders Markdown-inspired text definitions to create and modify diagrams dynamically.
+
+> If you are familiar with Markdown you should have no problem learning [Mermaid's Syntax](./n00b-syntaxReference.md).
+
+<img src="/header.png" alt="" />
+
+[](https://travis-ci.org/mermaid-js/mermaid) [](https://www.npmjs.com/package/mermaid) [](https://coveralls.io/github/mermaid-js/mermaid?branch=master) [](https://join.slack.com/t/mermaid-talk/shared_invite/enQtNzc4NDIyNzk4OTAyLWVhYjQxOTI2OTg4YmE1ZmJkY2Y4MTU3ODliYmIwOTY3NDJlYjA0YjIyZTdkMDMyZTUwOGI0NjEzYmEwODcwOTE)
+
+<!-- Mermaid book banner -->
+
+[](https://mermaid-js.github.io/mermaid/landing/)
+
+<!-- <Main description> -->
+
+Mermaid is a JavaScript based diagramming and charting tool that uses Markdown-inspired text definitions and a renderer to create and modify complex diagrams. The main purpose of Mermaid is to help documentation catch up with development.
+
+> Doc-Rot is a Catch-22 that Mermaid helps to solve.
+
+Diagramming and documentation costs precious developer time and gets outdated quickly.
+But not having diagrams or docs ruins productivity and hurts organizational learning.<br/>
+Mermaid addresses this problem by enabling users to create easily modifiable diagrams, it can also be made part of production scripts (and other pieces of code).<br/>
+<br/>
+Mermaid allows even non-programmers to easily create detailed and diagrams through the [Mermaid Live Editor](https://mermaid.live/).<br/>
+[Tutorials](../config/Tutorials.md) has video tutorials.
+Use Mermaid with your favorite applications, check out the list of [Integrations and Usages of Mermaid](../misc/integrations.md).
+
+For a more detailed introduction to Mermaid and some of its more basic uses, look to the [Beginner's Guide](../community/n00b-overview.md) and [Usage](../config/usage.md).
+
+🌐 [CDN](https://unpkg.com/mermaid/) | 📖 [Documentation](https://mermaidjs.github.io) | 🙌 [Contribution](https://github.com/mermaid-js/mermaid/blob/develop/docs/development.md) | 📜 [Version Log](../community/CHANGELOG.md) | 🔌 [Plug-Ins](../misc/integrations.md)
+
+::: warning 🖖
+Keep a steady pulse: mermaid needs more Collaborators, [Read More](https://github.com/knsv/mermaid/issues/866).
+:::
+
+:trophy: **Mermaid was nominated and won the [JS Open Source Awards (2019)](https://osawards.com/javascript/#nominees) in the category "The most exciting use of technology"!!!**
+
+**Thanks to all involved, people committing pull requests, people answering questions and special thanks to Tyler Long who is helping me maintain the project 🙏**
+
+In our release process we rely heavily on visual regression tests using [applitools](https://applitools.com/). Applitools is a great service which has been easy to use and integrate with our tests.
+
+<a href="https://applitools.com/">
+<svg width="170" height="32" viewBox="0 0 170 32" fill="none" xmlns="http://www.w3.org/2000/svg"><mask id="a" maskUnits="userSpaceOnUse" x="27" y="0" width="143" height="32"><path fill-rule="evenodd" clip-rule="evenodd" d="M27.732.227h141.391v31.19H27.733V.227z" fill="#fff"></path></mask><g mask="url(#a)"><path fill-rule="evenodd" clip-rule="evenodd" d="M153.851 22.562l1.971-3.298c1.291 1.219 3.837 2.402 5.988 2.402 1.971 0 2.903-.753 2.903-1.829 0-2.832-10.253-.502-10.253-7.313 0-2.904 2.51-5.45 7.099-5.45 2.904 0 5.234 1.004 6.955 2.367l-1.829 3.226c-1.039-1.075-3.011-2.008-5.126-2.008-1.65 0-2.725.717-2.725 1.685 0 2.546 10.289.395 10.289 7.386 0 3.19-2.724 5.52-7.528 5.52-3.012 0-5.916-1.003-7.744-2.688zm-5.7 2.259h4.553V.908h-4.553v23.913zm-6.273-8.676c0-2.689-1.578-5.02-4.446-5.02-2.832 0-4.409 2.331-4.409 5.02 0 2.724 1.577 5.055 4.409 5.055 2.868 0 4.446-2.33 4.446-5.055zm-13.588 0c0-4.912 3.442-9.07 9.142-9.07 5.736 0 9.178 4.158 9.178 9.07 0 4.911-3.442 9.106-9.178 9.106-5.7 0-9.142-4.195-9.142-9.106zm-5.628 0c0-2.689-1.577-5.02-4.445-5.02-2.832 0-4.41 2.331-4.41 5.02 0 2.724 1.578 5.055 4.41 5.055 2.868 0 4.445-2.33 4.445-5.055zm-13.587 0c0-4.912 3.441-9.07 9.142-9.07 5.736 0 9.178 4.158 9.178 9.07 0 4.911-3.442 9.106-9.178 9.106-5.701 0-9.142-4.195-9.142-9.106zm-8.425 4.338v-8.999h-2.868v-3.98h2.868V2.773h4.553v4.733h3.514v3.979h-3.514v7.78c0 1.111.574 1.936 1.578 1.936.681 0 1.326-.251 1.577-.538l.968 3.478c-.681.609-1.9 1.11-3.8 1.11-3.191 0-4.876-1.648-4.876-4.767zm-8.962 4.338h4.553V7.505h-4.553V24.82zm-.43-21.905a2.685 2.685 0 012.688-2.69c1.506 0 2.725 1.184 2.725 2.69a2.724 2.724 0 01-2.725 2.724c-1.47 0-2.688-1.219-2.688-2.724zM84.482 24.82h4.553V.908h-4.553v23.913zm-6.165-8.676c0-2.976-1.793-5.02-4.41-5.02-1.47 0-3.119.825-3.908 1.973v6.094c.753 1.111 2.438 2.008 3.908 2.008 2.617 0 4.41-2.044 4.41-5.055zm-8.318 6.453v8.82h-4.553V7.504H70v2.187c1.327-1.685 3.227-2.618 5.342-2.618 4.446 0 7.672 3.299 7.672 9.07 0 5.773-3.226 9.107-7.672 9.107-2.043 0-3.907-.86-5.342-2.653zm-10.718-6.453c0-2.976-1.793-5.02-4.41-5.02-1.47 0-3.119.825-3.908 1.973v6.094c.753 1.111 2.438 2.008 3.908 2.008 2.617 0 4.41-2.044 4.41-5.055zm-8.318 6.453v8.82H46.41V7.504h4.553v2.187c1.327-1.685 3.227-2.618 5.342-2.618 4.446 0 7.672 3.299 7.672 9.07 0 5.773-3.226 9.107-7.672 9.107-2.043 0-3.908-.86-5.342-2.653zm-11.758-1.936V18.51c-.753-1.004-2.187-1.542-3.657-1.542-1.793 0-3.263.968-3.263 2.617 0 1.65 1.47 2.582 3.263 2.582 1.47 0 2.904-.502 3.657-1.506zm0 4.159v-1.829c-1.183 1.434-3.227 2.259-5.485 2.259-2.761 0-5.988-1.864-5.988-5.736 0-4.087 3.227-5.593 5.988-5.593 2.33 0 4.337.753 5.485 2.115V13.85c0-1.756-1.506-2.904-3.8-2.904-1.829 0-3.55.717-4.984 2.044L28.63 9.8c2.115-1.901 4.84-2.726 7.564-2.726 3.98 0 7.6 1.578 7.6 6.561v11.186h-4.588z" fill="#00A298"></path></g><path fill-rule="evenodd" clip-rule="evenodd" d="M14.934 16.177c0 1.287-.136 2.541-.391 3.752-1.666-1.039-3.87-2.288-6.777-3.752 2.907-1.465 5.11-2.714 6.777-3.753.255 1.211.39 2.466.39 3.753m4.6-7.666V4.486a78.064 78.064 0 01-4.336 3.567c-1.551-2.367-3.533-4.038-6.14-5.207C11.1 4.658 12.504 6.7 13.564 9.262 5.35 15.155 0 16.177 0 16.177s5.35 1.021 13.564 6.915c-1.06 2.563-2.463 4.603-4.507 6.415 2.607-1.169 4.589-2.84 6.14-5.207a77.978 77.978 0 014.336 3.568v-4.025s-.492-.82-2.846-2.492c.6-1.611.93-3.354.93-5.174a14.8 14.8 0 00-.93-5.174c2.354-1.673 2.846-2.492 2.846-2.492" fill="#00A298"></path></svg>
+</a>
+
+## Diagram Types
+
+### [Flowchart](../syntax/flowchart.md?id=flowcharts-basic-syntax)
+
+```mmd
+graph TD;
+ A-->B;
+ A-->C;
+ B-->D;
+ C-->D;
+```
+
+```mermaid
+graph TD;
+ A-->B;
+ A-->C;
+ B-->D;
+ C-->D;
+```
+
+### [Sequence diagram](../syntax/sequenceDiagram.md)
+
+```mmd
+sequenceDiagram
+ participant Alice
+ participant Bob
+ Alice->>John: Hello John, how are you?
+ loop Healthcheck
+ John->>John: Fight against hypochondria
+ end
+ Note right of John: Rational thoughts <br/>prevail!
+ John-->>Alice: Great!
+ John->>Bob: How about you?
+ Bob-->>John: Jolly good!
+```
+
+```mermaid
+sequenceDiagram
+ participant Alice
+ participant Bob
+ Alice->>John: Hello John, how are you?
+ loop Healthcheck
+ John->>John: Fight against hypochondria
+ end
+ Note right of John: Rational thoughts <br/>prevail!
+ John-->>Alice: Great!
+ John->>Bob: How about you?
+ Bob-->>John: Jolly good!
+```
+
+### [Gantt diagram](../syntax/gantt.md)
+
+```mmd
+gantt
+ dateFormat YYYY-MM-DD
+ title Adding GANTT diagram to mermaid
+ excludes weekdays 2014-01-10
+
+ section A section
+ Completed task :done, des1, 2014-01-06,2014-01-08
+ Active task :active, des2, 2014-01-09, 3d
+ Future task : des3, after des2, 5d
+ Future task2 : des4, after des3, 5d
+```
+
+```mermaid
+gantt
+ dateFormat YYYY-MM-DD
+ title Adding GANTT diagram to mermaid
+ excludes weekdays 2014-01-10
+
+ section A section
+ Completed task :done, des1, 2014-01-06,2014-01-08
+ Active task :active, des2, 2014-01-09, 3d
+ Future task : des3, after des2, 5d
+ Future task2 : des4, after des3, 5d
+```
+
+### [Class diagram](../syntax/classDiagram.md)
+
+```mmd
+classDiagram
+ Class01 <|-- AveryLongClass : Cool
+ Class03 *-- Class04
+ Class05 o-- Class06
+ Class07 .. Class08
+ Class09 --> C2 : Where am i?
+ Class09 --* C3
+ Class09 --|> Class07
+ Class07 : equals()
+ Class07 : Object[] elementData
+ Class01 : size()
+ Class01 : int chimp
+ Class01 : int gorilla
+ Class08 <--> C2: Cool label
+```
+
+```mermaid
+classDiagram
+ Class01 <|-- AveryLongClass : Cool
+ Class03 *-- Class04
+ Class05 o-- Class06
+ Class07 .. Class08
+ Class09 --> C2 : Where am i?
+ Class09 --* C3
+ Class09 --|> Class07
+ Class07 : equals()
+ Class07 : Object[] elementData
+ Class01 : size()
+ Class01 : int chimp
+ Class01 : int gorilla
+ Class08 <--> C2: Cool label
+```
+
+### Git graph
+
+```mmd
+ gitGraph
+ commit
+ commit
+ branch develop
+ commit
+ commit
+ commit
+ checkout main
+ commit
+ commit
+```
+
+```mermaid
+ gitGraph
+ commit
+ commit
+ branch develop
+ commit
+ commit
+ commit
+ checkout main
+ commit
+ commit
+```
+
+### [Entity Relationship Diagram - :exclamation: experimental](../syntax/entityRelationshipDiagram.md)
+
+```mmd
+erDiagram
+ CUSTOMER ||--o{ ORDER : places
+ ORDER ||--|{ LINE-ITEM : contains
+ CUSTOMER }|..|{ DELIVERY-ADDRESS : uses
+
+```
+
+```mermaid
+erDiagram
+ CUSTOMER ||--o{ ORDER : places
+ ORDER ||--|{ LINE-ITEM : contains
+ CUSTOMER }|..|{ DELIVERY-ADDRESS : uses
+
+```
+
+### [User Journey Diagram] (../syntax/userjourney.md)
+
+```mmd
+journey
+ title My working day
+ section Go to work
+ Make tea: 5: Me
+ Go upstairs: 3: Me
+ Do work: 1: Me, Cat
+ section Go home
+ Go downstairs: 5: Me
+ Sit down: 5: Me
+```
+
+```mermaid
+journey
+ title My working day
+ section Go to work
+ Make tea: 5: Me
+ Go upstairs: 3: Me
+ Do work: 1: Me, Cat
+ section Go home
+ Go downstairs: 5: Me
+ Sit down: 5: Me
+```
+
+## Installation
+
+**In depth guides and examples can be found at [Getting Started](n00b-gettingStarted) and [Usage](../config/usage).**
+
+**It would also be helpful to learn more about mermaid's [Syntax](n00b-syntaxReference).**
+
+### CDN
+
+```
+https://unpkg.com/mermaid@<version>/dist/
+```
+
+To select a version:
+
+Replace `<version>` with the desired version number.
+
+Latest Version: [https://unpkg.com/browse/mermaid@8.8.0/](https://unpkg.com/browse/mermaid@8.8.0/)
+
+## Deploying Mermaid
+
+To Deploy Mermaid:
+
+1. You will need to install node v16, which would have npm
+2. Download yarn using npm
+3. Enter the following command: `yarn add mermaid`
+4. You can then add mermaid as a dev dependency using this command:
+ `yarn add --dev mermaid`
+
+### [Mermaid API](../config/Setup.md):
+
+**To deploy mermaid without a bundler, one can insert a `script` tag with an absolute address and a `mermaidAPI` call into the HTML like so:**
+
+```html
+<script src="https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js"></script>
+<script>
+ mermaid.initialize({ startOnLoad: true });
+</script>
+```
+
+**Doing so will command the mermaid parser to look for the `<div>` tags with `class="mermaid"`. From these tags mermaid will try to read the diagram/chart definitions and render them into SVG charts.**
+
+**Examples can be found at** [Other examples](../syntax/examples)
+
+## Sibling projects
+
+- [Mermaid Live Editor](https://github.com/mermaid-js/mermaid-live-editor)
+- [Mermaid CLI](https://github.com/mermaid-js/mermaid-cli)
+- [Mermaid Webpack Demo](https://github.com/mermaidjs/mermaid-webpack-demo)
+- [Mermaid Parcel Demo](https://github.com/mermaidjs/mermaid-parcel-demo)
+
+## Request for Assistance
+
+Things are piling up and I have a hard time keeping up. It would be great if we could form a core team of developers to cooperate
+with the future development of mermaid.
+
+As part of this team you would get write access to the repository and would
+represent the project when answering questions and issues.
+
+Together we could continue the work with things like:
+
+- Adding more types of diagrams like mindmaps, ert diagrams, etc.
+- Improving existing diagrams
+
+Don't hesitate to contact me if you want to get involved!
+
+## For contributors
+
+### Setup
+
+```sh
+yarn install
+```
+
+### Build
+
+```sh
+yarn build:watch
+```
+
+### Lint
+
+```sh
+yarn lint
+```
+
+We use [eslint](https://eslint.org/).
+We recommend you to install [editor plugins](https://eslint.org/docs/user-guide/integrations) to get real time lint result.
+
+### Test
+
+```sh
+yarn test
+```
+
+Manual test in browser: open `dist/index.html`
+
+### Release
+
+For those who have the permission to do so:
+
+Update version number in `package.json`.
+
+```sh
+npm publish
+```
+
+The above command generates files into the `dist` folder and publishes them to npmjs.org.
+
+## Related projects
+
+- [Command Line Interface](https://github.com/mermaid-js/mermaid-cli)
+- [Live Editor](https://github.com/mermaid-js/mermaid-live-editor)
+- [HTTP Server](https://github.com/TomWright/mermaid-server)
+
+## Contributors
+
+[](https://github.com/mermaid-js/mermaid/issues?q=is%3Aissue+is%3Aopen+label%3A%22Good+first+issue%21%22) [](https://github.com/mermaid-js/mermaid/graphs/contributors) [](https://github.com/mermaid-js/mermaid/graphs/contributors)
+
+Mermaid is a growing community and is always accepting new contributors. There's a lot of different ways to help out and we're always looking for extra hands! Look at [this issue](https://github.com/mermaid-js/mermaid/issues/866) if you want to know where to start helping out.
+
+Detailed information about how to contribute can be found in the [contribution guide](#)
+
+## Security and safe diagrams
+
+For public sites, it can be precarious to retrieve text from users on the internet, storing that content for presentation in a browser at a later stage. The reason is that the user content can contain embedded malicious scripts that will run when the data is presented. For Mermaid this is a risk, specially as mermaid diagrams contain many characters that are used in html which makes the standard sanitation unusable as it also breaks the diagrams. We still make an effort to sanitise the incoming code and keep refining the process but it is hard to guarantee that there are no loop holes.
+
+As an extra level of security for sites with external users we are happy to introduce a new security level in which the diagram is rendered in a sandboxed iframe preventing JavaScript in the code from being executed. This is a great step forward for better security.
+
+_Unfortunately you can not have a cake and eat it at the same time which in this case means that some of the interactive functionality gets blocked along with the possible malicious code._
+
+## Reporting vulnerabilities
+
+To report a vulnerability, please e-mail security@mermaid.live with a description of the issue, the steps you took to create the issue, affected versions, and if known, mitigations for the issue.
+
+## Appreciation
+
+A quick note from Knut Sveidqvist:
+
+> _Many thanks to the [d3](https://d3js.org/) and [dagre-d3](https://github.com/cpettitt/dagre-d3) projects for providing the graphical layout and drawing libraries!_ >_Thanks also to the [js-sequence-diagram](https://bramp.github.io/js-sequence-diagrams) project for usage of the grammar for the sequence diagrams. Thanks to Jessica Peter for inspiration and starting point for gantt rendering._ >_Thank you to [Tyler Long](https://github.com/tylerlong) who has been a collaborator since April 2017._
+>
+> _Thank you to the ever-growing list of [contributors](https://github.com/knsv/mermaid/graphs/contributors) that brought the project this far!_
+
+---
+
+_Mermaid was created by Knut Sveidqvist for easier documentation._
+
+<style scoped>
+ #contributors + p,
+ #about-mermaid + p + p + blockquote + img + p
+ {
+ display: flex
+ }
+
+ #contributors + p a,
+ #about-mermaid + p + p + blockquote + img + p a
+ {
+ margin: 0 0.5rem
+ }
+
+ .dark #VPContent > div > div > div.content > div > main > div > div > img
+ {
+ filter: invert(1) hue-rotate(217deg) contrast(0.72);
+ }
+</style>
diff --git a/vdocs/intro/n00b-gettingStarted.md b/vdocs/intro/n00b-gettingStarted.md
new file mode 100644
index 0000000000..14b49057e6
--- /dev/null
+++ b/vdocs/intro/n00b-gettingStarted.md
@@ -0,0 +1,216 @@
+# A Mermaid User-Guide for Beginners
+
+Mermaid is composed of three parts: Deployment, Syntax and Configuration.
+
+This section talks about the different ways to deploy Mermaid. Learning the [Syntax](./n00b-syntaxReference.md) would be of great help to the beginner.
+
+> Generally the live editor is enough for most general uses of mermaid, and is a good place to start learning.
+
+**Absolute beginners are advised to view the Video [Tutorials](../config/Tutorials.md) on the Live Editor, to gain a better understanding of mermaid.**
+
+## Four ways of using mermaid:
+
+1. Using the Mermaid Live Editor at [mermaid.live](https://mermaid.live).
+2. Using [mermaid plugins](../misc/integrations.md) with programs you are familiar with.
+3. Calling the Mermaid JavaScript API.
+4. Deploying Mermaid as a dependency.
+
+**Note: It is our recommendation that you review all approaches, and choose the one that is best for your project.**
+
+> More in depth information can be found at [Usage](../config/usage).
+
+## 1. Using the Live Editor
+
+Available at [mermaid.live](https://mermaid.live)
+
+```mermaid
+graph TD
+ A[Enter Chart Definition] --> B(Preview)
+ B --> C{decide}
+ C --> D[Keep]
+ C --> E[Edit Definition]
+ E --> B
+ D --> F[Save Image and Code]
+ F --> B
+```
+
+In the `Code` section one can write or edit raw mermaid code, and instantly `Preview` the rendered result on the panel beside it.
+
+The `Configuration` Section is for changing the appearance and behavior of mermaid diagrams. An easy introduction to mermaid configuration is found in the [Advanced usage](../config/n00b-advanced) section. A complete configuration reference cataloging the default values can be found on the [mermaidAPI](../config/Setup) page.
+
+
+
+### Editing History
+
+Your code will be autosaved every minute into the Timeline tab of History which shows the most recent 30 items.
+
+You can manually save code by clicking the Save icon in the History section. It can also be accessed in the Saved tab. This is stored in the browser storage only.
+
+### Saving a Diagram:
+
+You may choose any of the methods below, to save it
+
+**We recommend that you save your diagram code on top of any method you choose, in order to make edits and modifications further down the line.**
+
+
+
+### Editing your diagrams
+
+Editing is as easy as pasting your **Diagram code**, into the `code` section of the `Live Editor`.
+
+### Loading from Gists
+
+The Gist you create should have a code.mmd file and optionally a config.json. [Example](https://gist.github.com/sidharthv96/6268a23e673a533dcb198f241fd7012a)
+
+To load a gist into the Editor, you can use https://mermaid.live/edit?gist=https://gist.github.com/sidharthv96/6268a23e673a533dcb198f241fd7012a
+
+and to View, https://mermaid.live/view?gist=https://gist.github.com/sidharthv96/6268a23e673a533dcb198f241fd7012a
+
+## 2. Using Mermaid Plugins:
+
+You can generate mermaid diagrams from within popular applications using plug-ins. It can be done in the same way, you would use the Live Editor. Here's a list of [Mermaid Plugins](../misc/integrations).
+
+**This is covered in greater detail in the [Usage section](../config/usage)**
+
+## 3. Calling the JavaScript API
+
+This method can be used with any common web server like Apache, IIS, nginx, node express.
+
+You will also need a text editing tool like Notepad++ to generate a .html file. It is then deployed by a web browser (such as Firefox, Chrome, Safari, but not Internet Explorer).
+
+The API works by pulling rendering instructions from the source `mermaid.js` in order to render diagrams on the page.
+
+### Requirements for the Mermaid API.
+
+When writing the .html file, we give three instructions inside the html code to the web browser:
+
+a. A reference for fetching the online mermaid renderer, through the `mermaid.js` or `mermaid.min.js`.
+
+b. The mermaid code for the diagram we want to create.
+
+c. The `mermaid.initialize()` call, which dictates the appearance of diagrams and also starts the rendering process .
+
+**a. A reference to the external CDN in a `<script src>` tag, or a reference to mermaid.js as a separate file.:**
+
+```html
+<body>
+ <script src="https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.min.js"></script>
+</body>
+```
+
+**b. The embedded mermaid diagram definition inside a `<pre class="mermaid">`:**
+
+```html
+<body>
+ Here is a mermaid diagram:
+ <pre class="mermaid">
+ graph TD
+ A[Client] --> B[Load Balancer]
+ B --> C[Server01]
+ B --> D[Server02]
+ </pre>
+</body>
+```
+
+**Notes**: Every Mermaid chart/graph/diagram definition, should have separate `<pre>` tags.
+
+**c. The `mermaid.initialize()` call.**
+
+`mermaid.initialize()` call takes all the definitions contained in all the `<pre class="mermaid">` tags that it finds in the html body and renders them into diagrams. Example:
+
+```html
+<body>
+ <script>
+ mermaid.initialize({ startOnLoad: true });
+ </script>
+</body>
+```
+
+**Notes**:
+Rendering in Mermaid is initialized by `mermaid.initialize()` call. You can place `mermaid.initialize()` inside `mermaid.min.js` for brevity. However, doing the opposite lets you control when it starts looking for `<div>`tags inside the web page with `mermaid.initialize()`. This is useful when you think that not all `<div>` tags may have loaded on the execution of `mermaid.min.js` file.
+
+`startOnLoad` is one of the parameters that can be defined by `mermaid.initialize()`
+
+| Parameter | Description | Type | Values |
+| ----------- | --------------------------------- | ------- | ----------- |
+| startOnLoad | Toggle for Rendering upon loading | Boolean | true, false |
+
+### Working Examples
+
+**Here is a full working example of the mermaidAPI being called through the CDN:**
+
+```html
+<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:
+ <pre class="mermaid">
+ graph TD
+ A[Client] --> B[Load Balancer]
+ B --> C[Server1]
+ B --> D[Server2]
+ </pre>
+
+ And here is another:
+ <pre class="mermaid">
+ graph TD
+ A[Client] -->|tcp_123| B
+ B(Load Balancer)
+ B -->|tcp_456| C[Server1]
+ B -->|tcp_456| D[Server2]
+ </pre>
+ </body>
+</html>
+```
+
+**Another Option:**
+In this example mermaid.js is referenced in `src` as a separate JavaScript file, in an example Path.
+
+```html
+<html lang="en">
+ <head>
+ <meta charset="utf-8" />
+ </head>
+ <body>
+ <pre class="mermaid">
+ graph LR
+ A --- B
+ B-->C[fa:fa-ban forbidden]
+ B-->D(fa:fa-spinner);
+ </pre>
+ <pre class="mermaid">
+ graph TD
+ A[Client] --> B[Load Balancer]
+ B --> C[Server1]
+ B --> D[Server2]
+ </pre>
+ <script src="The\Path\In\Your\Package\mermaid.js"></script>
+ <script>
+ mermaid.initialize({ startOnLoad: true });
+ </script>
+ </body>
+</html>
+```
+
+---
+
+## 4. Adding Mermaid as a dependency.
+
+1. install node v16, which would have npm
+
+2. download yarn using npm by entering the command below:
+ npm install -g yarn
+
+3. After yarn installs, enter the following command:
+ yarn add mermaid
+
+4. To add Mermaid as a Dev Dependency
+ yarn add --dev mermaid
+
+**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 in the `<body>` as seen above. Older parts of the documentation frequently reflects the previous way which still works.
diff --git a/vdocs/intro/n00b-syntaxReference.md b/vdocs/intro/n00b-syntaxReference.md
new file mode 100644
index 0000000000..8434ec6c1e
--- /dev/null
+++ b/vdocs/intro/n00b-syntaxReference.md
@@ -0,0 +1,67 @@
+# Diagram Syntax
+
+Mermaid's syntax is used to create diagrams. You'll find that it is not too tricky and can be learned in a day. The next sections dive deep into the syntax of each diagram type.
+
+Syntax, together with Deployment and Configuration constitute the whole of Mermaid.
+
+Diagram Examples can be found in the [Mermaid Live Editor](https://mermaid-js.github.io/mermaid-live-editor), it is also a great practice area.
+
+## Syntax Structure
+
+One would notice that all **Diagrams definitions begin** with a declaration of the **diagram type**, followed by the definitions of the diagram and its contents. This declaration notifies the parser which kind of diagram the code is supposed to generate.
+
+**Example** : The code below is for an Entity Relationship Diagram, specified by the `erDiagram` declaration. What follows is the definition of the different `Entities` represented in it.
+
+```mermaid-example
+erDiagram
+ CUSTOMER }|..|{ DELIVERY-ADDRESS : has
+ CUSTOMER ||--o{ ORDER : places
+ CUSTOMER ||--o{ INVOICE : "liable for"
+ DELIVERY-ADDRESS ||--o{ ORDER : receives
+ INVOICE ||--|{ ORDER : covers
+ ORDER ||--|{ ORDER-ITEM : includes
+ PRODUCT-CATEGORY ||--|{ PRODUCT : contains
+ PRODUCT ||--o{ ORDER-ITEM : "ordered in"
+```
+
+The [Getting Started](./n00b-gettingStarted.md) section can also provide some practical examples of mermaid syntax.
+
+## Diagram Breaking
+
+One should **beware the use of some words or symbols** that can break diagrams. These words or symbols are few and often only affect specific types of diagrams. The table below will continuously be updated.
+
+| Diagram Breakers | Reason | Solution |
+| -------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------- |
+| **Comments** | | |
+| [` %%{``}%% `](https://github.com/mermaid-js/mermaid/issues/1968) | Similar to [Directives](../config/directives.md) confuses the renderer. | In comments using `%%`, avoid using "{}". |
+| **Flow-Charts** | | |
+| 'end' | The word "End" can cause Flowcharts and Sequence diagrams to break | Wrap them in quotation marks to prevent breakage. |
+| [Nodes inside Nodes](https://mermaid-js.github.io/mermaid/#/flowchart?id=special-characters-that-break-syntax) | Mermaid gets confused with nested shapes | wrap them in quotation marks to prevent breaking |
+
+### Mermaid Live Editor
+
+Now, that you've seen what you should not add to your diagrams, you can play around with them in the [Mermaid Live Editor](https://mermaid-js.github.io/mermaid-live-editor).
+
+# Configuration
+
+Configuration is the third part of Mermaid, after deployment and syntax. It deals with the different ways that Mermaid can be customized across different deployments.
+
+If you are interested in altering and customizing your Mermaid Diagrams, you will find the methods and values available for [Configuration](../config/Setup) here. It includes themes.
+This section will introduce the different methods of configuring the behaviors and appearances of Mermaid Diagrams.
+The following are the most commonly used methods, and they are all tied to Mermaid [Deployment](./n00b-gettingStarted.md) methods.
+
+### Configuration Section in the [Live Editor](https://mermaid-js.github.io/mermaid-live-editor).
+
+Here you can edit certain values to change the behavior and appearance of the diagram.
+
+### [The initialize() call](https://mermaid-js.github.io/mermaid/#/n00b-gettingStarted?id=_3-calling-the-javascript-api),
+
+Used when Mermaid is called via an API, or through a `<script>` tag.
+
+### [Directives](../config/directives),
+
+Allows for the limited reconfiguration of a diagram just before it is rendered. It can alter the font style, color and other aesthetic aspects of the diagram. You can pass a directive alongside your definition inside `%%{ }%%`. It can be done either above or below your diagram definition.
+
+### [Theme Manipulation](../config/theming):
+
+An application of using Directives to change [Themes](../config/theming). `Theme` is a value within Mermaid's configuration that dictates the color scheme for diagrams.
diff --git a/vdocs/misc/faq.md b/vdocs/misc/faq.md
new file mode 100644
index 0000000000..698061deff
--- /dev/null
+++ b/vdocs/misc/faq.md
@@ -0,0 +1,11 @@
+# Frequently Asked Questions
+
+1. [How to add title to flowchart?](https://github.com/knsv/mermaid/issues/556#issuecomment-363182217)
+1. [How to specify custom CSS file?](https://github.com/mermaidjs/mermaid.cli/pull/24#issuecomment-373402785)
+1. [How to fix tooltip misplacement issue?](https://github.com/knsv/mermaid/issues/542#issuecomment-3343564621)
+1. [How to specify gantt diagram xAxis format?](https://github.com/knsv/mermaid/issues/269#issuecomment-373229136)
+1. [How to bind an event?](https://github.com/knsv/mermaid/issues/372)
+1. [How to add newline in the text?](https://github.com/knsv/mermaid/issues/384#issuecomment-281339381)
+1. [How to have special characters in link text?](https://github.com/knsv/mermaid/issues/407#issuecomment-329944735)
+1. [How to change Flowchart curve style?](https://github.com/knsv/mermaid/issues/580#issuecomment-373929046)
+1. [How to create a Flowchart end-Node that says "End"](https://github.com/mermaid-js/mermaid/issues/1444#issuecomment-639528897)
diff --git a/vdocs/misc/integrations.md b/vdocs/misc/integrations.md
new file mode 100644
index 0000000000..4147059a03
--- /dev/null
+++ b/vdocs/misc/integrations.md
@@ -0,0 +1,180 @@
+# Integrations
+
+The following list is a compilation of different integrations and plugins that allow the rendering of mermaid definitions within other applications.
+
+They also serve as proof of concept, for the variety of things that can be built with mermaid.
+
+## Productivity
+
+- [GitHub](https://github.com) (**Native support**)
+ - [Using code blocks](https://github.blog/2022-02-14-include-diagrams-markdown-files-mermaid/) (**Native support**)
+ - [GitHub action: Compile mermaid to image](https://github.com/neenjaw/compile-mermaid-markdown-action)
+ - [svg-generator](https://github.com/SimonKenyonShepard/mermaidjs-github-svg-generator)
+- [GitLab](https://docs.gitlab.com/ee/user/markdown.html#diagrams-and-flowcharts) (**Native support**)
+- [Gitea](https://gitea.io) (**Native support**)
+- [Azure Devops](https://docs.microsoft.com/en-us/azure/devops/project/wiki/wiki-markdown-guidance?view=azure-devops#add-mermaid-diagrams-to-a-wiki-page) (**Native support**)
+- [Tuleap](https://docs.tuleap.org/user-guide/writing-in-tuleap.html#graphs) (**Native support**)
+- [Joplin](https://joplinapp.org) (**Native support**)
+- [Notion](https://notion.so) (**Native support**)
+- [Observable](https://observablehq.com/@observablehq/mermaid) (**Native support**)
+- [GitBook](https://gitbook.com)
+ - [Mermaid Plugin](https://github.com/JozoVilcek/gitbook-plugin-mermaid)
+ - [Markdown with Mermaid CLI](https://github.com/miao1007/gitbook-plugin-mermaid-cli)
+ - [Mermaid plugin for GitBook](https://github.com/wwformat/gitbook-plugin-mermaid-pdf)
+- [LiveBook](https://livebook.dev) (**Native support**)
+- [Atlassian Products](https://www.atlassian.com)
+ - [Mermaid Plugin for Confluence](https://marketplace.atlassian.com/apps/1214124/mermaid-plugin-for-confluence?hosting=server&tab=overview)
+ - [CloudScript.io Addon](https://marketplace.atlassian.com/apps/1219878/cloudscript-io-mermaid-addon?hosting=cloud&tab=overview)
+ - [Auto convert diagrams in Jira](https://github.com/coddingtonbear/jirafs-mermaid)
+- [Redmine](https://redmine.org)
+ - [Mermaid Macro](https://www.redmine.org/plugins/redmine_mermaid_macro)
+ - [redmine-mermaid](https://github.com/styz/redmine_mermaid)
+ - [markdown-for-mermaid-plugin](https://github.com/jamieh-mongolian/markdown-for-mermaid-plugin)
+- [Jetsbrain IDE eg Pycharm](https://www.jetbrains.com/go/guide/tips/mermaid-js-support-in-markdown/)
+- [mermerd](https://github.com/KarnerTh/mermerd)
+
+## CRM/ERP/Similar
+
+- [coreBOS](https://blog.corebos.org/blog/december2019)
+
+## Blogs
+
+- [Wordpress](https://wordpress.org)
+ - [WordPress Markdown Editor](https://wordpress.org/plugins/wp-githuber-md)
+ - [WP-ReliableMD](https://wordpress.org/plugins/wp-reliablemd/)
+- [Hexo](https://hexo.io)
+ - [hexo-filter-mermaid-diagrams](https://github.com/webappdevelp/hexo-filter-mermaid-diagrams)
+ - [hexo-tag-mermaid](https://github.com/JameChou/hexo-tag-mermaid)
+ - [hexo-mermaid-diagrams](https://github.com/mslxl/hexo-mermaid-diagrams)
+
+## CMS
+
+- [VitePress](https://vitepress.vuejs.org/)
+ - [Plugin for Mermaid.js](https://emersonbottero.github.io/vitepress-plugin-mermaid/)
+- [VuePress](https://vuepress.vuejs.org/)
+ - [Plugin for Mermaid.js](https://github.com/eFrane/vuepress-plugin-mermaidjs)
+- [Grav CMS](https://getgrav.org/)
+ - [Mermaid Diagrams](https://github.com/DanielFlaum/grav-plugin-mermaid-diagrams)
+ - [Gitlab Markdown Adapter](https://github.com/Goutte/grav-plugin-gitlab-markdown-adapter)
+
+## Communication
+
+- [Discourse](https://discourse.org)
+ - [Mermaid Plugin](https://github.com/pnewell/discourse-mermaid), [And](https://github.com/unfoldingWord-dev/discourse-mermaid)
+- [Mattermost](https://mattermost.com/)
+ - [Mermaid Plugin](https://github.com/SpikeTings/Mermaid)
+- [phpBB](https://phpbb.com)
+ - [phpbb-ext-mermaid](https://github.com/AlfredoRamos/phpbb-ext-mermaid)
+- [NodeBB](https://nodebb.org)
+ - [Mermaid Plugin](https://www.npmjs.com/package/nodebb-plugin-mermaid)
+
+## Wikis
+
+- [MediaWiki](https://www.mediawiki.org)
+ - [Mermaid Extension](https://www.mediawiki.org/wiki/Extension:Mermaid)
+ - [Flex Diagrams Extension](https://www.mediawiki.org/wiki/Extension:Flex_Diagrams)
+- [Semantic Media Wiki](https://semantic-mediawiki.org)
+ - [Mermaid Plugin](https://github.com/SemanticMediaWiki/Mermaid)
+- [FosWiki](https://foswiki.org)
+ - [Mermaid Plugin](https://foswiki.org/Extensions/MermaidPlugin)
+- [DokuWiki](https://dokuwiki.org)
+ - [Flowcharts](https://www.dokuwiki.org/plugin:flowcharts?s[]=mermaid)
+ - [ComboStrap](https://combostrap.com/mermaid)
+- [TiddlyWiki](https://tiddlywiki.com/)
+ - [mermaid-tw5: full js library](https://github.com/efurlanm/mermaid-tw5)
+ - [tw5-mermaid: wrapper for Mermaid Live](https://github.com/jasonmhoule/tw5-mermaid)
+
+## Editor Plugins
+
+- [Vs Code](https://code.visualstudio.com/)
+ - [Markdown Preview Mermaid Support](https://marketplace.visualstudio.com/items?itemName=bierner.markdown-mermaid)
+ - [Mermaid Preview](https://marketplace.visualstudio.com/items?itemName=vstirbu.vscode-mermaid-preview)
+ - [Mermaid Markdown Syntax Highlighting](https://marketplace.visualstudio.com/items?itemName=bpruitt-goddard.mermaid-markdown-syntax-highlighting)
+ - [Mermaid Editor](https://marketplace.visualstudio.com/items?itemName=tomoyukim.vscode-mermaid-editor)
+ - [Mermaid Export](https://marketplace.visualstudio.com/items?itemName=Gruntfuggly.mermaid-export)
+ - [Markdown PDF](https://marketplace.visualstudio.com/items?itemName=yzane.markdown-pdf)
+ - [Preview](https://marketplace.visualstudio.com/items?itemName=searKing.preview-vscode)
+ - [Preview Sequence Diagrams](https://marketplace.visualstudio.com/items?itemName=arichika.previewseqdiag-vscode)
+- [Markdown-It](https://github.com/markdown-it/markdown-it)
+ - [Textual UML Parser](https://github.com/manastalukdar/markdown-it-textual-uml)
+ - [Mermaid Plugin](https://github.com/tylingsoft/markdown-it-mermaid)
+ - [md-it-mermaid](https://github.com/iamcco/md-it-mermaid)
+ - [markdown-it-mermaid-fence-new](https://github.com/Revomatico/markdown-it-mermaid-fence-new)
+ - [markdown-it-mermaid-less](https://github.com/searKing/markdown-it-mermaid-less)
+- [Atom](https://atom.io)
+ - [Markdown Preview Enhanced](https://atom.io/packages/markdown-preview-enhanced)
+ - [Atom Mermaid](https://atom.io/packages/atom-mermaid)
+ - [Language Mermaid Syntax Highlighter](https://atom.io/packages/language-mermaid)
+- [Sublime Text 3](https://sublimetext.com)
+ - [Mermaid Package](https://packagecontrol.io/packages/Mermaid)
+- [Astah](https://astah.net)
+ - [Export to Mermaid](https://github.com/Avens666/Astah_Jude_UML_export_to_Markdown-mermaid-Plantuml-)
+- [Light Table](http://lighttable.com/)
+ - [Mermaid Plugin](https://github.com/cldwalker/Mermaid)
+- [Draw.io](https://draw.io) - [Plugin](https://github.com/nopeslide/drawio_mermaid_plugin)
+- [Inkdrop](https://www.inkdrop.app) - [Plugin](https://github.com/inkdropapp/inkdrop-mermaid)
+- [Vim](https://www.vim.org)
+ - [Vim Diagram Syntax](https://github.com/zhaozg/vim-diagram)
+- [GNU Emacs](https://www.gnu.org/software/emacs/)
+ - [Major mode for .mmd files](https://github.com/abrochard/mermaid-mode)
+ - [Org-Mode integration](https://github.com/arnm/ob-mermaid)
+- [Brackets](https://brackets.io/)
+ - [Mermaid Preview](https://github.com/AlanHohn/mermaid-preview)
+- [Iodide](https://github.com/iodide-project/iodide)
+ - [iodide-mermaid-plugin](https://github.com/iodide-project/iodide-mermaid-plugin)
+- [Google docs](https://docs.google.com/)
+ - [Mermaid plugin for google docs](https://workspace.google.com/marketplace/app/mermaid/636321283856)
+- [Podlite](https://github.com/zag/podlite-desktop)
+ - [Named block =Diagram](https://github.com/zag/podlite/tree/main/packages/podlite-diagrams)
+- [GNU Nano](https://www.nano-editor.org/)
+ - [Nano Mermaid](https://github.com/Yash-Singh1/nano-mermaid)
+
+## Document Generation
+
+- [Sphinx](https://www.sphinx-doc.org/en/master/)
+ - [sphinxcontrib-mermaid](https://github.com/mgaitan/sphinxcontrib-mermaid)
+- [remark.js](https://remark.js.org/)
+ - [remark-mermaid](https://github.com/temando/remark-mermaid)
+- [jSDoc](https://jsdoc.app/)
+ - [jsdoc-mermaid](https://github.com/Jellyvision/jsdoc-mermaid)
+- [MkDocs](https://mkdocs.org)
+ - [mkdocs-mermaid2-plugin](https://github.com/fralau/mkdocs-mermaid2-plugin)
+ - [mkdocs-material](https://github.com/squidfunk/mkdocs-material), check the [docs](https://squidfunk.github.io/mkdocs-material/reference/diagrams/)
+- [Type Doc](https://typedoc.org/)
+ - [typedoc-plugin-mermaid](https://www.npmjs.com/package/typedoc-plugin-mermaid)
+- [Docsy Hugo Theme](https://www.docsy.dev/docs/adding-content/lookandfeel/#diagrams-with-mermaid) (Native support in theme)
+- [Codedoc](https://codedoc.cc/)
+ - [codedoc-mermaid-plugin](https://www.npmjs.com/package/codedoc-mermaid-plugin)
+- [mdbook](https://rust-lang.github.io/mdBook/index.html)
+ - [mdbook-mermaid](https://github.com/badboy/mdbook-mermaid)
+
+## Browser Extensions
+
+| Name | Chrome Web Store | Firefox Add-ons | Opera | Edge | Source/Repository |
+| ------------------------ | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
+| GitHub + Mermaid | - | [🦊🔗](https://addons.mozilla.org/firefox/addon/github-mermaid/) | - | - | [🐙🔗](https://github.com/BackMarket/github-mermaid-extension) |
+| Asciidoctor Live Preview | [🎡🔗](https://chrome.google.com/webstore/detail/asciidoctorjs-live-previe/iaalpfgpbocpdfblpnhhgllgbdbchmia) | - | - | [🌀🔗](https://microsoftedge.microsoft.com/addons/detail/asciidoctorjs-live-previ/pefkelkanablhjdekgdahplkccnbdggd?hl=en-US) | - |
+| Diagram Tab | - | - | - | - | [🐙🔗](https://github.com/khafast/diagramtab) |
+| Markdown Diagrams | [🎡🔗](https://chrome.google.com/webstore/detail/markdown-diagrams/pmoglnmodacnbbofbgcagndelmgaclel/) | [🦊🔗](https://addons.mozilla.org/en-US/firefox/addon/markdown-diagrams/) | [🔴🔗](https://addons.opera.com/en/extensions/details/markdown-diagrams/) | [🌀🔗](https://microsoftedge.microsoft.com/addons/detail/markdown-diagrams/hceenoomhhdkjjijnmlclkpenkapfihe) | [🐙🔗](https://github.com/marcozaccari/markdown-diagrams-browser-extension/tree/master/doc/examples) |
+| Markdown Viewer | - | [🦊🔗](https://addons.mozilla.org/en-US/firefox/addon/markdown-viewer-chrome/) | - | - | [🐙🔗](https://github.com/simov/markdown-viewer) |
+| Extensions for Mermaid | - | [🦊🔗](https://addons.mozilla.org/en-US/firefox/addon/markdown-viewer-chrome/) | [🔴🔗](https://addons.opera.com/en/extensions/details/extensions-for-mermaid/) | - | [🐙🔗](https://github.com/Stefan-S/mermaid-extension) |
+| Chrome Diagrammer | [🎡🔗](https://chrome.google.com/webstore/detail/chrome-diagrammer/bkpbgjmkomfoakfklcjeoegkklgjnnpk) | - | - | - | - |
+| Mermaid Diagrams | [🎡🔗](https://chrome.google.com/webstore/detail/mermaid-diagrams/phfcghedmopjadpojhmmaffjmfiakfil) | - | - | - | - |
+| Mermaid Markdown | [🎡🔗](https://chrome.google.com/webstore/detail/mermaid-markdown/mboeoikjijmjcjgpccghbcoegikliijg) | - | - | - | - |
+| Monkeys | [🎡🔗](https://chrome.google.com/webstore/detail/monkeys-mermaid-for-githu/cplfdpoajbclbgphaphphcldamfkjlgi) | - | - | - | - |
+| Mermaid Previewer | [🎡🔗](https://chrome.google.com/webstore/detail/mermaid-previewer/oidjnlhbegipkcklbdfnbkikplpghfdl) | - | - | - | - |
+
+## Other
+
+- [Jekyll](https://jekyllrb.com/)
+ - [jekyll-mermaid](https://rubygems.org/gems/jekyll-mermaid)
+ - [jekyll-mermaid-diagrams](https://github.com/fuzhibo/jekyll-mermaid-diagrams)
+- [Reveal.js](https://github.com/hakimel/reveal.js)
+ - [reveal.js-mermaid-plugin](https://github.com/ludwick/reveal.js-mermaid-plugin)
+- [Bisheng](https://www.npmjs.com/package/bisheng)
+ - [bisheng-plugin-mermaid](https://github.com/yct21/bisheng-plugin-mermaid)
+- [Reveal CK](https://github.com/jedcn/reveal-ck)
+ - [reveal-ck-mermaid-plugin](https://github.com/tmtm/reveal-ck-mermaid-plugin)
+- [mermaid-server: Generate diagrams using a HTTP request](https://github.com/TomWright/mermaid-server)
+- [ExDoc](https://github.com/elixir-lang/ex_doc)
+ - [Rendering Mermaid graphs](https://github.com/elixir-lang/ex_doc#rendering-mermaid-graphs)
diff --git a/vdocs/public/.nojekyll b/vdocs/public/.nojekyll
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/vdocs/public/header.png b/vdocs/public/header.png
new file mode 100644
index 0000000000..6db8635c9d
Binary files /dev/null and b/vdocs/public/header.png differ
diff --git a/vdocs/syntax/c4c.md b/vdocs/syntax/c4c.md
new file mode 100644
index 0000000000..0ab805182c
--- /dev/null
+++ b/vdocs/syntax/c4c.md
@@ -0,0 +1,363 @@
+# C4 Diagrams
+
+> C4 Diagram: This is an experimental diagram for now. The syntax and properties can change in future releases. Proper documentation will be provided when the syntax is stable.
+
+Mermaid's c4 diagram syntax is compatible with plantUML. See example below:
+
+```mermaid-example
+ C4Context
+ title System Context diagram for Internet Banking System
+ Enterprise_Boundary(b0, "BankBoundary0") {
+ Person(customerA, "Banking Customer A", "A customer of the bank, with personal bank accounts.")
+ Person(customerB, "Banking Customer B")
+ Person_Ext(customerC, "Banking Customer C", "desc")
+
+ Person(customerD, "Banking Customer D", "A customer of the bank, <br/> with personal bank accounts.")
+
+ System(SystemAA, "Internet Banking System", "Allows customers to view information about their bank accounts, and make payments.")
+
+ Enterprise_Boundary(b1, "BankBoundary") {
+
+ SystemDb_Ext(SystemE, "Mainframe Banking System", "Stores all of the core banking information about customers, accounts, transactions, etc.")
+
+ System_Boundary(b2, "BankBoundary2") {
+ System(SystemA, "Banking System A")
+ System(SystemB, "Banking System B", "A system of the bank, with personal bank accounts. next line.")
+ }
+
+ System_Ext(SystemC, "E-mail system", "The internal Microsoft Exchange e-mail system.")
+ SystemDb(SystemD, "Banking System D Database", "A system of the bank, with personal bank accounts.")
+
+ Boundary(b3, "BankBoundary3", "boundary") {
+ SystemQueue(SystemF, "Banking System F Queue", "A system of the bank.")
+ SystemQueue_Ext(SystemG, "Banking System G Queue", "A system of the bank, with personal bank accounts.")
+ }
+ }
+ }
+
+ BiRel(customerA, SystemAA, "Uses")
+ BiRel(SystemAA, SystemE, "Uses")
+ Rel(SystemAA, SystemC, "Sends e-mails", "SMTP")
+ Rel(SystemC, customerA, "Sends e-mails to")
+
+ UpdateElementStyle(customerA, $fontColor="red", $bgColor="grey", $borderColor="red")
+ UpdateRelStyle(customerA, SystemAA, $textColor="blue", $lineColor="blue", $offsetX="5")
+ UpdateRelStyle(SystemAA, SystemE, $textColor="blue", $lineColor="blue", $offsetY="-10")
+ UpdateRelStyle(SystemAA, SystemC, $textColor="blue", $lineColor="blue", $offsetY="-40", $offsetX="-50")
+ UpdateRelStyle(SystemC, customerA, $textColor="red", $lineColor="red", $offsetX="-50", $offsetY="20")
+
+ UpdateLayoutConfig($c4ShapeInRow="3", $c4BoundaryInRow="1")
+
+
+```
+
+For an example, see the source code demos/index.html
+
+5 types of C4 charts are supported.
+
+- System Context (C4Context)
+- Container diagram (C4Container)
+- Component diagram (C4Component)
+- Dynamic diagram (C4Dynamic)
+- Deployment diagram (C4Deployment)
+
+Please refer to the linked document [C4-PlantUML syntax](https://github.com/plantuml-stdlib/C4-PlantUML/blob/master/README.md) for how to write the c4 diagram.
+
+C4 diagram is fixed style, such as css color, so different css is not provided under different skins.
+updateElementStyle and UpdateElementStyle are written in the diagram last part. updateElementStyle is inconsistent with the original definition and updates the style of the relationship, including the offset of the text label relative to the original position.
+
+The layout does not use a fully automated layout algorithm. The position of shapes is adjusted by changing the order in which statements are written. So there is no plan to support the following Layout statements.
+The number of shapes per row and the number of boundaries can be adjusted using UpdateLayoutConfig.
+
+- Layout
+- - Lay_U, Lay_Up
+- - Lay_D, Lay_Down
+- - Lay_L, Lay_Left
+- - Lay_R, Lay_Right
+
+The following unfinished features are not supported in the short term.
+
+- [ ] sprite
+- [ ] tags
+- [ ] link
+- [ ] Legend
+
+- [x] System Context
+- - [x] Person(alias, label, ?descr, ?sprite, ?tags, $link)
+- - [x] Person_Ext
+- - [x] System(alias, label, ?descr, ?sprite, ?tags, $link)
+- - [x] SystemDb
+- - [x] SystemQueue
+- - [x] System_Ext
+- - [x] SystemDb_Ext
+- - [x] SystemQueue_Ext
+- - [x] Boundary(alias, label, ?type, ?tags, $link)
+- - [x] Enterprise_Boundary(alias, label, ?tags, $link)
+- - [x] System_Boundary
+
+- [x] Container diagram
+- - [x] Container(alias, label, ?techn, ?descr, ?sprite, ?tags, $link)
+- - [x] ContainerDb
+- - [x] ContainerQueue
+- - [x] Container_Ext
+- - [x] ContainerDb_Ext
+- - [x] ContainerQueue_Ext
+- - [x] Container_Boundary(alias, label, ?tags, $link)
+
+- [x] Component diagram
+- - [x] Component(alias, label, ?techn, ?descr, ?sprite, ?tags, $link)
+- - [x] ComponentDb
+- - [x] ComponentQueue
+- - [x] Component_Ext
+- - [x] ComponentDb_Ext
+- - [x] ComponentQueue_Ext
+
+- [x] Dynamic diagram
+- - [x] RelIndex(index, from, to, label, ?tags, $link)
+
+- [x] Deployment diagram
+- - [x] Deployment_Node(alias, label, ?type, ?descr, ?sprite, ?tags, $link)
+- - [x] Node(alias, label, ?type, ?descr, ?sprite, ?tags, $link): short name of Deployment_Node()
+- - [x] Node_L(alias, label, ?type, ?descr, ?sprite, ?tags, $link): left aligned Node()
+- - [x] Node_R(alias, label, ?type, ?descr, ?sprite, ?tags, $link): right aligned Node()
+
+- [x] Relationship Types
+- - [x] Rel(from, to, label, ?techn, ?descr, ?sprite, ?tags, $link)
+- - [x] BiRel (bidirectional relationship)
+- - [x] Rel_U, Rel_Up
+- - [x] Rel_D, Rel_Down
+- - [x] Rel_L, Rel_Left
+- - [x] Rel_R, Rel_Right
+- - [x] Rel_Back
+- - [x] RelIndex \* Compatible with C4-Plantuml syntax, but ignores the index parameter. The sequence number is determined by the order in which the rel statements are written.
+
+- [ ] Custom tags/stereotypes support and skinparam updates
+- - [ ] AddElementTag(tagStereo, ?bgColor, ?fontColor, ?borderColor, ?shadowing, ?shape, ?sprite, ?techn, ?legendText, ?legendSprite): Introduces a new element tag. The styles of the tagged elements are updated and the tag is displayed in the calculated legend.
+- - [ ] AddRelTag(tagStereo, ?textColor, ?lineColor, ?lineStyle, ?sprite, ?techn, ?legendText, ?legendSprite): Introduces a new Relationship tag. The styles of the tagged relationships are updated and the tag is displayed in the calculated legend.
+- - [x] UpdateElementStyle(elementName, ?bgColor, ?fontColor, ?borderColor, ?shadowing, ?shape, ?sprite, ?techn, ?legendText, ?legendSprite): This call updates the default style of the elements (component, ...) and creates no additional legend entry.
+- - [x] UpdateRelStyle(from, to, ?textColor, ?lineColor, ?offsetX, ?offsetY): This call updates the default relationship colors and creates no additional legend entry. Two new parameters, offsetX and offsetY, are added to set the offset of the original position of the text.
+- - [ ] RoundedBoxShape(): This call returns the name of the rounded box shape and can be used as ?shape argument.
+- - [ ] EightSidedShape(): This call returns the name of the eight sided shape and can be used as ?shape argument.
+- - [ ] DashedLine(): This call returns the name of the dashed line and can be used as ?lineStyle argument.
+- - [ ] DottedLine(): This call returns the name of the dotted line and can be used as ?lineStyle argument.
+- - [ ] BoldLine(): This call returns the name of the bold line and can be used as ?lineStyle argument.
+- - [x] UpdateLayoutConfig(?c4ShapeInRow, ?c4BoundaryInRow): New. This call updates the default c4ShapeInRow(4) and c4BoundaryInRow(2).
+
+There are two ways to assign parameters with question marks. One uses the non-named parameter assignment method in the order of the parameters, and the other uses the named parameter assignment method, where the name must start with a $ symbol.
+
+Example: UpdateRelStyle(from, to, ?textColor, ?lineColor, ?offsetX, ?offsetY)
+
+```
+UpdateRelStyle(customerA, bankA, "red", "blue", "-40", "60")
+UpdateRelStyle(customerA, bankA, $offsetX="-40", $offsetY="60", $lineColor="blue", $textColor="red")
+UpdateRelStyle(customerA, bankA, $offsetY="60")
+
+```
+
+## C4 System Context Diagram (C4Context)
+
+```mermaid-example
+ C4Context
+ title System Context diagram for Internet Banking System
+ Enterprise_Boundary(b0, "BankBoundary0") {
+ Person(customerA, "Banking Customer A", "A customer of the bank, with personal bank accounts.")
+ Person(customerB, "Banking Customer B")
+ Person_Ext(customerC, "Banking Customer C", "desc")
+
+ Person(customerD, "Banking Customer D", "A customer of the bank, <br/> with personal bank accounts.")
+
+ System(SystemAA, "Internet Banking System", "Allows customers to view information about their bank accounts, and make payments.")
+
+ Enterprise_Boundary(b1, "BankBoundary") {
+
+ SystemDb_Ext(SystemE, "Mainframe Banking System", "Stores all of the core banking information about customers, accounts, transactions, etc.")
+
+ System_Boundary(b2, "BankBoundary2") {
+ System(SystemA, "Banking System A")
+ System(SystemB, "Banking System B", "A system of the bank, with personal bank accounts. next line.")
+ }
+
+ System_Ext(SystemC, "E-mail system", "The internal Microsoft Exchange e-mail system.")
+ SystemDb(SystemD, "Banking System D Database", "A system of the bank, with personal bank accounts.")
+
+ Boundary(b3, "BankBoundary3", "boundary") {
+ SystemQueue(SystemF, "Banking System F Queue", "A system of the bank.")
+ SystemQueue_Ext(SystemG, "Banking System G Queue", "A system of the bank, with personal bank accounts.")
+ }
+ }
+ }
+
+ BiRel(customerA, SystemAA, "Uses")
+ BiRel(SystemAA, SystemE, "Uses")
+ Rel(SystemAA, SystemC, "Sends e-mails", "SMTP")
+ Rel(SystemC, customerA, "Sends e-mails to")
+
+ UpdateElementStyle(customerA, $fontColor="red", $bgColor="grey", $borderColor="red")
+ UpdateRelStyle(customerA, SystemAA, $textColor="blue", $lineColor="blue", $offsetX="5")
+ UpdateRelStyle(SystemAA, SystemE, $textColor="blue", $lineColor="blue", $offsetY="-10")
+ UpdateRelStyle(SystemAA, SystemC, $textColor="blue", $lineColor="blue", $offsetY="-40", $offsetX="-50")
+ UpdateRelStyle(SystemC, customerA, $textColor="red", $lineColor="red", $offsetX="-50", $offsetY="20")
+
+ UpdateLayoutConfig($c4ShapeInRow="3", $c4BoundaryInRow="1")
+
+```
+
+## C4 Container diagram (C4Container)
+
+```mermaid-example
+ C4Container
+ title Container diagram for Internet Banking System
+
+ System_Ext(email_system, "E-Mail System", "The internal Microsoft Exchange system", $tags="v1.0")
+ Person(customer, Customer, "A customer of the bank, with personal bank accounts", $tags="v1.0")
+
+ Container_Boundary(c1, "Internet Banking") {
+ Container(spa, "Single-Page App", "JavaScript, Angular", "Provides all the Internet banking functionality to cutomers via their web browser")
+ Container_Ext(mobile_app, "Mobile App", "C#, Xamarin", "Provides a limited subset of the Internet banking functionality to customers via their mobile device")
+ Container(web_app, "Web Application", "Java, Spring MVC", "Delivers the static content and the Internet banking SPA")
+ ContainerDb(database, "Database", "SQL Database", "Stores user registration information, hashed auth credentials, access logs, etc.")
+ ContainerDb_Ext(backend_api, "API Application", "Java, Docker Container", "Provides Internet banking functionality via API")
+
+ }
+
+ System_Ext(banking_system, "Mainframe Banking System", "Stores all of the core banking information about customers, accounts, transactions, etc.")
+
+ Rel(customer, web_app, "Uses", "HTTPS")
+ UpdateRelStyle(customer, web_app, $offsetY="60", $offsetX="90")
+ Rel(customer, spa, "Uses", "HTTPS")
+ UpdateRelStyle(customer, spa, $offsetY="-40")
+ Rel(customer, mobile_app, "Uses")
+ UpdateRelStyle(customer, mobile_app, $offsetY="-30")
+
+ Rel(web_app, spa, "Delivers")
+ UpdateRelStyle(web_app, spa, $offsetX="130")
+ Rel(spa, backend_api, "Uses", "async, JSON/HTTPS")
+ Rel(mobile_app, backend_api, "Uses", "async, JSON/HTTPS")
+ Rel_Back(database, backend_api, "Reads from and writes to", "sync, JDBC")
+
+ Rel(email_system, customer, "Sends e-mails to")
+ UpdateRelStyle(email_system, customer, $offsetX="-45")
+ Rel(backend_api, email_system, "Sends e-mails using", "sync, SMTP")
+ UpdateRelStyle(backend_api, email_system, $offsetY="-60")
+ Rel(backend_api, banking_system, "Uses", "sync/async, XML/HTTPS")
+ UpdateRelStyle(backend_api, banking_system, $offsetY="-50", $offsetX="-140")
+
+```
+
+## C4 Component diagram (C4Component)
+
+```mermaid-example
+ C4Component
+ title Component diagram for Internet Banking System - API Application
+
+ Container(spa, "Single Page Application", "javascript and angular", "Provides all the internet banking functionality to customers via their web browser.")
+ Container(ma, "Mobile App", "Xamarin", "Provides a limited subset ot the internet banking functionality to customers via their mobile mobile device.")
+ ContainerDb(db, "Database", "Relational Database Schema", "Stores user registration information, hashed authentication credentials, access logs, etc.")
+ System_Ext(mbs, "Mainframe Banking System", "Stores all of the core banking information about customers, accounts, transactions, etc.")
+
+ Container_Boundary(api, "API Application") {
+ Component(sign, "Sign In Controller", "MVC Rest Controller", "Allows users to sign in to the internet banking system")
+ Component(accounts, "Accounts Summary Controller", "MVC Rest Controller", "Provides customers with a summary of their bank accounts")
+ Component(security, "Security Component", "Spring Bean", "Provides functionality related to singing in, changing passwords, etc.")
+ Component(mbsfacade, "Mainframe Banking System Facade", "Spring Bean", "A facade onto the mainframe banking system.")
+
+ Rel(sign, security, "Uses")
+ Rel(accounts, mbsfacade, "Uses")
+ Rel(security, db, "Read & write to", "JDBC")
+ Rel(mbsfacade, mbs, "Uses", "XML/HTTPS")
+ }
+
+ Rel_Back(spa, sign, "Uses", "JSON/HTTPS")
+ Rel(spa, accounts, "Uses", "JSON/HTTPS")
+
+ Rel(ma, sign, "Uses", "JSON/HTTPS")
+ Rel(ma, accounts, "Uses", "JSON/HTTPS")
+
+ UpdateRelStyle(spa, sign, $offsetY="-40")
+ UpdateRelStyle(spa, accounts, $offsetX="40", $offsetY="40")
+
+ UpdateRelStyle(ma, sign, $offsetX="-90", $offsetY="40")
+ UpdateRelStyle(ma, accounts, $offsetY="-40")
+
+ UpdateRelStyle(sign, security, $offsetX="-160", $offsetY="10")
+ UpdateRelStyle(accounts, mbsfacade, $offsetX="140", $offsetY="10")
+ UpdateRelStyle(security, db, $offsetY="-40")
+ UpdateRelStyle(mbsfacade, mbs, $offsetY="-40")
+
+```
+
+## C4 Dynamic diagram (C4Dynamic)
+
+```mermaid-example
+ C4Dynamic
+ title Dynamic diagram for Internet Banking System - API Application
+
+ ContainerDb(c4, "Database", "Relational Database Schema", "Stores user registration information, hashed authentication credentials, access logs, etc.")
+ Container(c1, "Single-Page Application", "JavaScript and Angular", "Provides all of the Internet banking functionality to customers via their web browser.")
+ Container_Boundary(b, "API Application") {
+ Component(c3, "Security Component", "Spring Bean", "Provides functionality Related to signing in, changing passwords, etc.")
+ Component(c2, "Sign In Controller", "Spring MVC Rest Controller", "Allows users to sign in to the Internet Banking System.")
+ }
+ Rel(c1, c2, "Submits credentials to", "JSON/HTTPS")
+ Rel(c2, c3, "Calls isAuthenticated() on")
+ Rel(c3, c4, "select * from users where username = ?", "JDBC")
+
+ UpdateRelStyle(c1, c2, $textColor="red", $offsetY="-40")
+ UpdateRelStyle(c2, c3, $textColor="red", $offsetX="-40", $offsetY="60")
+ UpdateRelStyle(c3, c4, $textColor="red", $offsetY="-40", $offsetX="10")
+
+```
+
+## C4 Deployment diagram (C4Deployment)
+
+```mermaid-example
+ C4Deployment
+ title Deployment Diagram for Internet Banking System - Live
+
+ Deployment_Node(mob, "Customer's mobile device", "Apple IOS or Android"){
+ Container(mobile, "Mobile App", "Xamarin", "Provides a limited subset of the Internet Banking functionality to customers via their mobile device.")
+ }
+
+ Deployment_Node(comp, "Customer's computer", "Mircosoft Windows or Apple macOS"){
+ Deployment_Node(browser, "Web Browser", "Google Chrome, Mozilla Firefox,<br/> Apple Safari or Microsoft Edge"){
+ Container(spa, "Single Page Application", "JavaScript and Angular", "Provides all of the Internet Banking functionality to customers via their web browser.")
+ }
+ }
+
+ Deployment_Node(plc, "Big Bank plc", "Big Bank plc data center"){
+ Deployment_Node(dn, "bigbank-api*** x8", "Ubuntu 16.04 LTS"){
+ Deployment_Node(apache, "Apache Tomcat", "Apache Tomcat 8.x"){
+ Container(api, "API Application", "Java and Spring MVC", "Provides Internet Banking functionality via a JSON/HTTPS API.")
+ }
+ }
+ Deployment_Node(bb2, "bigbank-web*** x4", "Ubuntu 16.04 LTS"){
+ Deployment_Node(apache2, "Apache Tomcat", "Apache Tomcat 8.x"){
+ Container(web, "Web Application", "Java and Spring MVC", "Delivers the static content and the Internet Banking single page application.")
+ }
+ }
+ Deployment_Node(bigbankdb01, "bigbank-db01", "Ubuntu 16.04 LTS"){
+ Deployment_Node(oracle, "Oracle - Primary", "Oracle 12c"){
+ ContainerDb(db, "Database", "Relational Database Schema", "Stores user registration information, hashed authentication credentials, access logs, etc.")
+ }
+ }
+ Deployment_Node(bigbankdb02, "bigbank-db02", "Ubuntu 16.04 LTS") {
+ Deployment_Node(oracle2, "Oracle - Secondary", "Oracle 12c") {
+ ContainerDb(db2, "Database", "Relational Database Schema", "Stores user registration information, hashed authentication credentials, access logs, etc.")
+ }
+ }
+ }
+
+ Rel(mobile, api, "Makes API calls to", "json/HTTPS")
+ Rel(spa, api, "Makes API calls to", "json/HTTPS")
+ Rel_U(web, spa, "Delivers to the customer's web browser")
+ Rel(api, db, "Reads from and writes to", "JDBC")
+ Rel(api, db2, "Reads from and writes to", "JDBC")
+ Rel_R(db, db2, "Replicates data to")
+
+ UpdateRelStyle(spa, api, $offsetY="-40")
+ UpdateRelStyle(web, spa, $offsetY="-40")
+ UpdateRelStyle(api, db, $offsetY="-20", $offsetX="5")
+ UpdateRelStyle(api, db2, $offsetX="-40", $offsetY="-20")
+ UpdateRelStyle(db, db2, $offsetY="-10")
+
+```
diff --git a/vdocs/syntax/classDiagram.md b/vdocs/syntax/classDiagram.md
new file mode 100644
index 0000000000..87d76cd37a
--- /dev/null
+++ b/vdocs/syntax/classDiagram.md
@@ -0,0 +1,625 @@
+# Class diagrams
+
+> "In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among objects."
+> Wikipedia
+
+The class diagram is the main building block of object-oriented modeling. It is used for general conceptual modeling of the structure of the application, and for detailed modeling to translate the models into programming code. Class diagrams can also be used for data modeling. The classes in a class diagram represent both the main elements, interactions in the application, and the classes to be programmed.
+
+Mermaid can render class diagrams.
+
+```mermaid-example
+classDiagram
+ Animal <|-- Duck
+ Animal <|-- Fish
+ Animal <|-- Zebra
+ Animal : +int age
+ Animal : +String gender
+ Animal: +isMammal()
+ Animal: +mate()
+ class Duck{
+ +String beakColor
+ +swim()
+ +quack()
+ }
+ class Fish{
+ -int sizeInFeet
+ -canEat()
+ }
+ class Zebra{
+ +bool is_wild
+ +run()
+ }
+```
+
+## Syntax
+
+### Class
+
+UML provides mechanisms to represent class members, such as attributes and methods, and additional information about them.
+A single instance of a class in the diagram contains three compartments:
+
+- The top compartment contains the name of the class. It is printed in bold and centered, and the first letter is capitalized. It may also contain optional annotation text describing the nature of the class.
+- The middle compartment contains the attributes of the class. They are left-aligned and the first letter is lowercase.
+- The bottom compartment contains the operations the class can execute. They are also left-aligned and the first letter is lowercase.
+
+```mermaid-example
+classDiagram
+ class BankAccount
+ BankAccount : +String owner
+ BankAccount : +Bigdecimal balance
+ BankAccount : +deposit(amount)
+ BankAccount : +withdrawal(amount)
+
+```
+
+## Define a class
+
+There are two ways to define a class:
+
+- Explicitly using keyword **class** like `class Animal` which would define the Animal class.
+- Via a **relationship** which defines two classes at a time along with their relationship. For instance, `Vehicle <|-- Car`.
+
+```mermaid-example
+classDiagram
+ class Animal
+ Vehicle <|-- Car
+```
+
+Naming convention: a class name should be composed only of alphanumeric characters (including unicode), and underscores.
+
+## Defining Members of a class
+
+UML provides mechanisms to represent class members such as attributes and methods, as well as additional information about them.
+
+Mermaid distinguishes between attributes and functions/methods based on if the **parenthesis** `()` are present or not. The ones with `()` are treated as functions/methods, and all others as attributes.
+
+There are two ways to define the members of a class, and regardless of whichever syntax is used to define the members, the output will still be same. The two different ways are :
+
+- Associate a member of a class using **:** (colon) followed by member name, useful to define one member at a time. For example:
+
+```mermaid-example
+classDiagram
+class BankAccount
+BankAccount : +String owner
+BankAccount : +BigDecimal balance
+BankAccount : +deposit(amount)
+BankAccount : +withdrawal(amount)
+```
+
+- Associate members of a class using **{}** brackets, where members are grouped within curly brackets. Suitable for defining multiple members at once. For example:
+
+```mermaid-example
+classDiagram
+class BankAccount{
+ +String owner
+ +BigDecimal balance
+ +deposit(amount)
+ +withdrawal(amount)
+}
+```
+
+#### Return Type
+
+Optionally you can end a method/function definition with the data type that will be returned (note: there must be a space between the final `)` and the return type). An example:
+
+```mermaid-example
+classDiagram
+class BankAccount{
+ +String owner
+ +BigDecimal balance
+ +deposit(amount) bool
+ +withdrawal(amount) int
+}
+```
+
+#### Generic Types
+
+Members can be defined using generic types, such as `List<int>`, for fields, parameters, and return types by enclosing the type within `~` (**tilde**). Note: **nested** type declarations such as `List<List<int>>` are not currently supported.
+
+Generics can be represented as part of a class definition and also in the parameters or the return value of a method/function:
+
+```mermaid-example
+classDiagram
+class Square~Shape~{
+ int id
+ List~int~ position
+ setPoints(List~int~ points)
+ getPoints() List~int~
+}
+
+Square : -List~string~ messages
+Square : +setMessages(List~string~ messages)
+Square : +getMessages() List~string~
+```
+
+#### Return Type
+
+Optionally you can end the method/function definition with the data type that will be returned.
+
+#### Visibility
+
+To describe the visibility (or encapsulation) of an attribute or method/function that is a part of a class (i.e. a class member), optional notation may be placed before that members' name:
+
+- `+` Public
+- `-` Private
+- `#` Protected
+- `~` Package/Internal
+
+> _note_ you can also include additional _classifiers_ to a method definition by adding the following notation to the _end_ of the method, i.e.: after the `()`:
+>
+> - `*` Abstract e.g.: `someAbstractMethod()*`
+> - `$` Static e.g.: `someStaticMethod()$`
+
+> _note_ you can also include additional _classifiers_ to a field definition by adding the following notation to the end of its name:
+>
+> - `$` Static e.g.: `String someField$`
+
+## Defining Relationship
+
+A relationship is a general term covering the specific types of logical connections found on class and object diagrams.
+
+```
+[classA][Arrow][ClassB]
+```
+
+There are eight different types of relations defined for classes under UML which are currently supported:
+
+| Type | Description |
+| ----- | ------------- |
+| <\|-- | Inheritance |
+| \*-- | Composition |
+| o-- | Aggregation |
+| --> | Association |
+| -- | Link (Solid) |
+| ..> | Dependency |
+| ..\|> | Realization |
+| .. | Link (Dashed) |
+
+```mermaid-example
+classDiagram
+classA <|-- classB
+classC *-- classD
+classE o-- classF
+classG <-- classH
+classI -- classJ
+classK <.. classL
+classM <|.. classN
+classO .. classP
+
+```
+
+We can use the labels to describe the nature of the relation between two classes. Also, arrowheads can be used in the opposite direction as well:
+
+```mermaid-example
+classDiagram
+classA --|> classB : Inheritance
+classC --* classD : Composition
+classE --o classF : Aggregation
+classG --> classH : Association
+classI -- classJ : Link(Solid)
+classK ..> classL : Dependency
+classM ..|> classN : Realization
+classO .. classP : Link(Dashed)
+
+```
+
+### Labels on Relations
+
+It is possible to add label text to a relation:
+
+```
+[classA][Arrow][ClassB]:LabelText
+```
+
+```mermaid-example
+classDiagram
+classA <|-- classB : implements
+classC *-- classD : composition
+classE o-- classF : aggregation
+```
+
+### Two-way relations
+
+Relations can logically represent an N:M association:
+
+```mmd
+classDiagram
+ Animal <|--|> Zebra
+```
+
+Here is the syntax:
+
+```
+[Relation Type][Link][Relation Type]
+```
+
+Where `Relation Type` can be one of:
+
+| Type | Description |
+| ---- | ----------- |
+| <\| | Inheritance |
+| \* | Composition |
+| o | Aggregation |
+| > | Association |
+| < | Association |
+| \|> | Realization |
+
+And `Link` can be one of:
+
+| Type | Description |
+| ---- | ----------- |
+| -- | Solid |
+| .. | Dashed |
+
+## Cardinality / Multiplicity on relations
+
+Multiplicity or cardinality in class diagrams indicates the number of instances of one class that can be linked to an instance of the other class. For example, each company will have one or more employees (not zero), and each employee currently works for zero or one companies.
+
+Multiplicity notations are placed near the end of an association.
+
+The different cardinality options are :
+
+- `1` Only 1
+- `0..1` Zero or One
+- `1..*` One or more
+- `*` Many
+- `n` n {where n>1}
+- `0..n` zero to n {where n>1}
+- `1..n` one to n {where n>1}
+
+Cardinality can be easily defined by placing the text option within quotes `"` before or after a given arrow. For example:
+
+```
+[classA] "cardinality1" [Arrow] "cardinality2" [ClassB]:LabelText
+```
+
+```mermaid-example
+classDiagram
+ Customer "1" --> "*" Ticket
+ Student "1" --> "1..*" Course
+ Galaxy --> "many" Star : Contains
+```
+
+## Annotations on classes
+
+It is possible to annotate classes with markers to provide additional metadata about the class. This can give a clearer indication about its nature. Some common annotations include:
+
+- `<<Interface>>` To represent an Interface class
+- `<<Abstract>>` To represent an abstract class
+- `<<Service>>` To represent a service class
+- `<<Enumeration>>` To represent an enum
+
+Annotations are defined within the opening `<<` and closing `>>`. There are two ways to add an annotation to a class, and either way the output will be same:
+
+- In a **_separate line_** after a class is defined:
+
+```mermaid-example
+classDiagram
+class Shape
+<<interface>> Shape
+Shape : noOfVertices
+Shape : draw()
+```
+
+- In a **_nested structure_** along with the class definition:
+
+```mermaid-example
+classDiagram
+class Shape{
+ <<interface>>
+ noOfVertices
+ draw()
+}
+class Color{
+ <<enumeration>>
+ RED
+ BLUE
+ GREEN
+ WHITE
+ BLACK
+}
+
+```
+
+## Comments
+
+Comments can be entered within a class diagram, which will be ignored by the parser. Comments need to be on their own line, and must be prefaced with `%%` (double percent signs). Any text until the next newline will be treated as a comment, including any class diagram syntax.
+
+```mmd
+classDiagram
+%% This whole line is a comment classDiagram class Shape <<interface>>
+class Shape{
+ <<interface>>
+ noOfVertices
+ draw()
+}
+```
+
+## Setting the direction of the diagram
+
+With class diagrams you can use the direction statement to set the direction in which the diagram will render:
+
+```mermaid-example
+classDiagram
+ direction RL
+ class Student {
+ -idCard : IdCard
+ }
+ class IdCard{
+ -id : int
+ -name : string
+ }
+ class Bike{
+ -id : int
+ -name : string
+ }
+ Student "1" --o "1" IdCard : carries
+ Student "1" --o "1" Bike : rides
+```
+
+## Interaction
+
+It is possible to bind a click event to a node. The click can lead to either a javascript callback or to a link which will be opened in a new browser tab. **Note**: This functionality is disabled when using `securityLevel='strict'` and enabled when using `securityLevel='loose'`.
+
+You would define these actions on a separate line after all classes have been declared.
+
+```
+action className "reference" "tooltip"
+click className call callback() "tooltip"
+click className href "url" "tooltip"
+```
+
+- _action_ is either `link` or `callback`, depending on which type of interaction you want to have called
+- _className_ is the id of the node that the action will be associated with
+- _reference_ is either the url link, or the function name for callback.
+- (_optional_) tooltip is a string to be displayed when hovering over element (note: The styles of the tooltip are set by the class .mermaidTooltip.)
+- note: callback function will be called with the nodeId as parameter.
+
+### Examples
+
+_URL Link:_
+
+```mmd
+classDiagram
+class Shape
+link Shape "https://www.github.com" "This is a tooltip for a link"
+class Shape2
+click Shape2 href "https://www.github.com" "This is a tooltip for a link"
+```
+
+_Callback:_
+
+```mmd
+classDiagram
+class Shape
+callback Shape "callbackFunction" "This is a tooltip for a callback"
+class Shape2
+click Shape2 call callbackFunction() "This is a tooltip for a callback"
+```
+
+```html
+<script>
+ var callbackFunction = function () {
+ alert('A callback was triggered');
+ };
+</script>
+```
+
+```mermaid
+classDiagram
+ class Class01
+ class Class02
+ callback Class01 "callbackFunction" "Callback tooltip"
+ link Class02 "https://www.github.com" "This is a link"
+ class Class03
+ class Class04
+ click Class03 call callbackFunction() "Callback tooltip"
+ click Class04 href "https://www.github.com" "This is a link"
+```
+
+> **Success** The tooltip functionality and the ability to link to urls are available from version 0.5.2.
+
+Beginner's tip—a full example using interactive links in an HTML page:
+
+```html
+<body>
+ <pre class="mermaid">
+ classDiagram
+ Animal <|-- Duck
+ Animal <|-- Fish
+ Animal <|-- Zebra
+ Animal : +int age
+ Animal : +String gender
+ Animal: +isMammal()
+ Animal: +mate()
+ class Duck{
+ +String beakColor
+ +swim()
+ +quack()
+ }
+ class Fish{
+ -int sizeInFeet
+ -canEat()
+ }
+ class Zebra{
+ +bool is_wild
+ +run()
+ }
+
+ callback Duck callback "Tooltip"
+ link Zebra "https://www.github.com" "This is a link"
+ </pre>
+
+ <script>
+ var callback = function () {
+ alert('A callback was triggered');
+ };
+ var config = {
+ startOnLoad: true,
+ securityLevel: 'loose',
+ };
+ mermaid.initialize(config);
+ </script>
+</body>
+```
+
+## Styling
+
+### Styling a node
+
+It is possible to apply specific styles such as a thicker border or a different background color to individual nodes. This is done by predefining classes in css styles that can be applied from the graph definition:
+
+```html
+<style>
+ .cssClass > rect {
+ fill: #ff0000;
+ stroke: #ffff00;
+ stroke-width: 4px;
+ }
+</style>
+```
+
+Then attaching that class to a specific node:
+
+```
+ cssClass "nodeId1" cssClass;
+```
+
+It is also possible to attach a class to a list of nodes in one statement:
+
+```
+ cssClass "nodeId1,nodeId2" cssClass;
+```
+
+A shorter form of adding a class is to attach the classname to the node using the `:::` operator:
+
+```mmd
+classDiagram
+ class Animal:::cssClass
+```
+
+Or:
+
+```mmd
+classDiagram
+ class Animal:::cssClass {
+ -int sizeInFeet
+ -canEat()
+ }
+```
+
+?> cssClasses cannot be added using this shorthand method at the same time as a relation statement.
+
+?> Due to limitations with existing markup for class diagrams, it is not currently possible to define css classes within the diagram itself. **_Coming soon!_**
+
+### Default Styles
+
+The main styling of the class diagram is done with a preset number of css classes. During rendering these classes are extracted from the file located at src/themes/class.scss. The classes used here are described below:
+
+| Class | Description |
+| ------------------ | ----------------------------------------------------------------- |
+| g.classGroup text | Styles for general class text |
+| classGroup .title | Styles for general class title |
+| g.classGroup rect | Styles for class diagram rectangle |
+| g.classGroup line | Styles for class diagram line |
+| .classLabel .box | Styles for class label box |
+| .classLabel .label | Styles for class label text |
+| composition | Styles for composition arrow head and arrow line |
+| aggregation | Styles for aggregation arrow head and arrow line(dashed or solid) |
+| dependency | Styles for dependency arrow head and arrow line |
+
+#### Sample stylesheet
+
+```scss
+body {
+ background: white;
+}
+
+g.classGroup text {
+ fill: $nodeBorder;
+ stroke: none;
+ font-family: 'trebuchet ms', verdana, arial;
+ font-family: var(--mermaid-font-family);
+ font-size: 10px;
+
+ .title {
+ font-weight: bolder;
+ }
+}
+
+g.classGroup rect {
+ fill: $nodeBkg;
+ stroke: $nodeBorder;
+}
+
+g.classGroup line {
+ stroke: $nodeBorder;
+ stroke-width: 1;
+}
+
+.classLabel .box {
+ stroke: none;
+ stroke-width: 0;
+ fill: $nodeBkg;
+ opacity: 0.5;
+}
+
+.classLabel .label {
+ fill: $nodeBorder;
+ font-size: 10px;
+}
+
+.relation {
+ stroke: $nodeBorder;
+ stroke-width: 1;
+ fill: none;
+}
+
+@mixin composition {
+ fill: $nodeBorder;
+ stroke: $nodeBorder;
+ stroke-width: 1;
+}
+
+#compositionStart {
+ @include composition;
+}
+
+#compositionEnd {
+ @include composition;
+}
+
+@mixin aggregation {
+ fill: $nodeBkg;
+ stroke: $nodeBorder;
+ stroke-width: 1;
+}
+
+#aggregationStart {
+ @include aggregation;
+}
+
+#aggregationEnd {
+ @include aggregation;
+}
+
+#dependencyStart {
+ @include composition;
+}
+
+#dependencyEnd {
+ @include composition;
+}
+
+#extensionStart {
+ @include composition;
+}
+
+#extensionEnd {
+ @include composition;
+}
+```
+
+## Configuration
+
+`Coming soon`
diff --git a/vdocs/syntax/entityRelationshipDiagram.md b/vdocs/syntax/entityRelationshipDiagram.md
new file mode 100644
index 0000000000..341c9147c4
--- /dev/null
+++ b/vdocs/syntax/entityRelationshipDiagram.md
@@ -0,0 +1,188 @@
+# Entity Relationship Diagrams
+
+> An entity–relationship model (or ER model) describes interrelated things of interest in a specific domain of knowledge. A basic ER model is composed of entity types (which classify the things of interest) and specifies relationships that can exist between entities (instances of those entity types). Wikipedia.
+
+Note that practitioners of ER modelling almost always refer to _entity types_ simply as _entities_. For example the `CUSTOMER` entity _type_ would be referred to simply as the `CUSTOMER` entity. This is so common it would be inadvisable to do anything else, but technically an entity is an abstract _instance_ of an entity type, and this is what an ER diagram shows - abstract instances, and the relationships between them. This is why entities are always named using singular nouns.
+
+Mermaid can render ER diagrams
+
+```mermaid-example
+erDiagram
+ CUSTOMER ||--o{ ORDER : places
+ ORDER ||--|{ LINE-ITEM : contains
+ CUSTOMER }|..|{ DELIVERY-ADDRESS : uses
+```
+
+Entity names are often capitalised, although there is no accepted standard on this, and it is not required in Mermaid.
+
+Relationships between entities are represented by lines with end markers representing cardinality. Mermaid uses the most popular crow's foot notation. The crow's foot intuitively conveys the possibility of many instances of the entity that it connects to.
+
+ER diagrams can be used for various purposes, ranging from abstract logical models devoid of any implementation details, through to physical models of relational database tables. It can be useful to include attribute definitions on ER diagrams to aid comprehension of the purpose and meaning of entities. These do not necessarily need to be exhaustive; often a small subset of attributes is enough. Mermaid allows them to be defined in terms of their _type_ and _name_.
+
+```mermaid-example
+erDiagram
+ CUSTOMER ||--o{ ORDER : places
+ CUSTOMER {
+ string name
+ string custNumber
+ string sector
+ }
+ ORDER ||--|{ LINE-ITEM : contains
+ ORDER {
+ int orderNumber
+ string deliveryAddress
+ }
+ LINE-ITEM {
+ string productCode
+ int quantity
+ float pricePerUnit
+ }
+```
+
+When including attributes on ER diagrams, you must decide whether to include foreign keys as attributes. This probably depends on how closely you are trying to represent relational table structures. If your diagram is a _logical_ model which is not meant to imply a relational implementation, then it is better to leave these out because the associative relationships already convey the way that entities are associated. For example, a JSON data structure can implement a one-to-many relationship without the need for foreign key properties, using arrays. Similarly an object-oriented programming language may use pointers or references to collections. Even for models that are intended for relational implementation, you might decide that inclusion of foreign key attributes duplicates information already portrayed by the relationships, and does not add meaning to entities. Ultimately, it's your choice.
+
+## Syntax
+
+### Entities and Relationships
+
+Mermaid syntax for ER diagrams is compatible with PlantUML, with an extension to label the relationship. Each statement consists of the following parts:
+
+```
+ <first-entity> [<relationship> <second-entity> : <relationship-label>]
+```
+
+Where:
+
+- `first-entity` is the name of an entity. Names must begin with an alphabetic character and may also contain digits, hyphens, and underscores.
+- `relationship` describes the way that both entities inter-relate. See below.
+- `second-entity` is the name of the other entity.
+- `relationship-label` describes the relationship from the perspective of the first entity.
+
+For example:
+
+```
+ PROPERTY ||--|{ ROOM : contains
+```
+
+This statement can be read as _a property contains one or more rooms, and a room is part of one and only one property_. You can see that the label here is from the first entity's perspective: a property contains a room, but a room does not contain a property. When considered from the perspective of the second entity, the equivalent label is usually very easy to infer. (Some ER diagrams label relationships from both perspectives, but this is not supported here, and is usually superfluous).
+
+Only the `first-entity` part of a statement is mandatory. This makes it possible to show an entity with no relationships, which can be useful during iterative construction of diagrams. If any other parts of a statement are specified, then all parts are mandatory.
+
+### Relationship Syntax
+
+The `relationship` part of each statement can be broken down into three sub-components:
+
+- the cardinality of the first entity with respect to the second,
+- whether the relationship confers identity on a 'child' entity
+- the cardinality of the second entity with respect to the first
+
+Cardinality is a property that describes how many elements of another entity can be related to the entity in question. In the above example a `PROPERTY` can have one or more `ROOM` instances associated to it, whereas a `ROOM` can only be associated with one `PROPERTY`. In each cardinality marker there are two characters. The outermost character represents a maximum value, and the innermost character represents a minimum value. The table below summarises possible cardinalities.
+
+| Value (left) | Value (right) | Meaning |
+| :----------: | :-----------: | ----------------------------- |
+| `\|o` | `o\|` | Zero or one |
+| `\|\|` | `\|\|` | Exactly one |
+| `}o` | `o{` | Zero or more (no upper limit) |
+| `}\|` | `\|{` | One or more (no upper limit) |
+
+### Identification
+
+Relationships may be classified as either _identifying_ or _non-identifying_ and these are rendered with either solid or dashed lines respectively. This is relevant when one of the entities in question can not have independent existence without the other. For example a firm that insures people to drive cars might need to store data on `NAMED-DRIVER`s. In modelling this we might start out by observing that a `CAR` can be driven by many `PERSON` instances, and a `PERSON` can drive many `CAR`s - both entities can exist without the other, so this is a non-identifying relationship that we might specify in Mermaid as: `PERSON }|..|{ CAR : "driver"`. Note the two dots in the middle of the relationship that will result in a dashed line being drawn between the two entities. But when this many-to-many relationship is resolved into two one-to-many relationships, we observe that a `NAMED-DRIVER` cannot exist without both a `PERSON` and a `CAR` - the relationships become identifying and would be specified using hyphens, which translate to a solid line:
+
+```mmd
+erDiagram
+ CAR ||--o{ NAMED-DRIVER : allows
+ PERSON ||--o{ NAMED-DRIVER : is
+```
+
+### Attributes
+
+Attributes can be defined for entities by specifying the entity name followed by a block containing multiple `type name` pairs, where a block is delimited by an opening `{` and a closing `}`. For example:
+
+```mermaid-example
+erDiagram
+ CAR ||--o{ NAMED-DRIVER : allows
+ CAR {
+ string registrationNumber
+ string make
+ string model
+ }
+ PERSON ||--o{ NAMED-DRIVER : is
+ PERSON {
+ string firstName
+ string lastName
+ int age
+ }
+```
+
+The attributes are rendered inside the entity boxes:
+
+```mermaid-example
+erDiagram
+ CAR ||--o{ NAMED-DRIVER : allows
+ CAR {
+ string registrationNumber
+ string make
+ string model
+ }
+ PERSON ||--o{ NAMED-DRIVER : is
+ PERSON {
+ string firstName
+ string lastName
+ int age
+ }
+```
+
+The `type` and `name` values must begin with an alphabetic character and may contain digits, hyphens or underscores. Other than that, there are no restrictions, and there is no implicit set of valid data types.
+
+#### Attribute Keys and Comments
+
+Attributes may also have a `key` or comment defined. Keys can be "PK" or "FK", for Primary Key or Foreign Key. And a `comment` is defined by double quotes at the end of an attribute. Comments themselves cannot have double-quote characters in them.
+
+```mermaid-example
+erDiagram
+ CAR ||--o{ NAMED-DRIVER : allows
+ CAR {
+ string allowedDriver FK "The license of the allowed driver"
+ string registrationNumber
+ string make
+ string model
+ }
+ PERSON ||--o{ NAMED-DRIVER : is
+ PERSON {
+ string driversLicense PK "The license #"
+ string firstName
+ string lastName
+ int age
+ }
+```
+
+### Other Things
+
+- If you want the relationship label to be more than one word, you must use double quotes around the phrase
+- If you don't want a label at all on a relationship, you must use an empty double-quoted string
+
+## Styling
+
+### Config options
+
+For simple color customization:
+
+| Name | Used as |
+| :------- | :------------------------------------------------------------------- |
+| `fill` | Background color of an entity or attribute |
+| `stroke` | Border color of an entity or attribute, line color of a relationship |
+
+### Classes used
+
+The following CSS class selectors are available for richer styling:
+
+| Selector | Description |
+| :------------------------- | :---------------------------------------------------- |
+| `.er.attributeBoxEven` | The box containing attributes on even-numbered rows |
+| `.er.attributeBoxOdd` | The box containing attributes on odd-numbered rows |
+| `.er.entityBox` | The box representing an entity |
+| `.er.entityLabel` | The label for an entity |
+| `.er.relationshipLabel` | The label for a relationship |
+| `.er.relationshipLabelBox` | The box surrounding a relationship label |
+| `.er.relationshipLine` | The line representing a relationship between entities |
diff --git a/vdocs/syntax/examples.md b/vdocs/syntax/examples.md
new file mode 100644
index 0000000000..45fb06de38
--- /dev/null
+++ b/vdocs/syntax/examples.md
@@ -0,0 +1,158 @@
+# Examples
+
+This page contains a collection of examples of diagrams and charts that can be created through mermaid and its myriad applications.
+
+**If you wish to learn how to support mermaid on your webpage, read the [Beginner's Guide](../config/usage?id=usage).**
+
+**If you wish to learn about mermaid's syntax, Read the [Diagram Syntax](../syntax/flowchart?id=flowcharts-basic-syntax) section.**
+
+## Basic Pie Chart
+
+```mermaid-example
+pie title NETFLIX
+ "Time spent looking for movie" : 90
+ "Time spent watching it" : 10
+```
+
+```mermaid-example
+pie title What Voldemort doesn't have?
+ "FRIENDS" : 2
+ "FAMILY" : 3
+ "NOSE" : 45
+```
+
+## Basic sequence diagram
+
+```mermaid-example
+sequenceDiagram
+ Alice ->> Bob: Hello Bob, how are you?
+ Bob-->>John: How about you John?
+ Bob--x Alice: I am good thanks!
+ Bob-x John: I am good thanks!
+ Note right of John: Bob thinks a long<br/>long time, so long<br/>that the text does<br/>not fit on a row.
+
+ Bob-->Alice: Checking with John...
+ Alice->John: Yes... John, how are you?
+```
+
+## Basic flowchart
+
+```mermaid-example
+graph LR
+ A[Square Rect] -- Link text --> B((Circle))
+ A --> C(Round Rect)
+ B --> D{Rhombus}
+ C --> D
+```
+
+## Larger flowchart with some styling
+
+```mermaid-example
+graph TB
+ sq[Square shape] --> ci((Circle shape))
+
+ subgraph A
+ od>Odd shape]-- Two line<br/>edge comment --> ro
+ di{Diamond with <br/> line break} -.-> ro(Rounded<br>square<br>shape)
+ di==>ro2(Rounded square shape)
+ end
+
+ %% Notice that no text in shape are added here instead that is appended further down
+ e --> od3>Really long text with linebreak<br>in an Odd shape]
+
+ %% Comments after double percent signs
+ e((Inner / circle<br>and some odd <br>special characters)) --> f(,.?!+-*ز)
+
+ cyr[Cyrillic]-->cyr2((Circle shape Начало));
+
+ classDef green fill:#9f6,stroke:#333,stroke-width:2px;
+ classDef orange fill:#f96,stroke:#333,stroke-width:4px;
+ class sq,e green
+ class di orange
+```
+
+## SequenceDiagram: Loops, alt and opt
+
+```mermaid-example
+sequenceDiagram
+ loop Daily query
+ Alice->>Bob: Hello Bob, how are you?
+ alt is sick
+ Bob->>Alice: Not so good :(
+ else is well
+ Bob->>Alice: Feeling fresh like a daisy
+ end
+
+ opt Extra response
+ Bob->>Alice: Thanks for asking
+ end
+ end
+```
+
+## SequenceDiagram: Message to self in loop
+
+```mermaid-example
+sequenceDiagram
+ participant Alice
+ participant Bob
+ Alice->>John: Hello John, how are you?
+ loop Healthcheck
+ John->>John: Fight against hypochondria
+ end
+ Note right of John: Rational thoughts<br/>prevail...
+ John-->>Alice: Great!
+ John->>Bob: How about you?
+ Bob-->>John: Jolly good!
+```
+
+## Sequence Diagram: Blogging app service communication
+
+```mermaid-example
+sequenceDiagram
+ participant web as Web Browser
+ participant blog as Blog Service
+ participant account as Account Service
+ participant mail as Mail Service
+ participant db as Storage
+
+ Note over web,db: The user must be logged in to submit blog posts
+ web->>+account: Logs in using credentials
+ account->>db: Query stored accounts
+ db->>account: Respond with query result
+
+ alt Credentials not found
+ account->>web: Invalid credentials
+ else Credentials found
+ account->>-web: Successfully logged in
+
+ Note over web,db: When the user is authenticated, they can now submit new posts
+ web->>+blog: Submit new post
+ blog->>db: Store post data
+
+ par Notifications
+ blog--)mail: Send mail to blog subscribers
+ blog--)db: Store in-site notifications
+ and Response
+ blog-->>-web: Successfully posted
+ end
+ end
+
+```
+
+## A commit flow diagram.
+
+```mermaid
+gitGraph:
+ commit "Ashish"
+ branch newbranch
+ checkout newbranch
+ commit id:"1111"
+ commit tag:"test"
+ checkout main
+ commit type: HIGHLIGHT
+ commit
+ merge newbranch
+ commit
+ branch b2
+ commit
+```
diff --git a/vdocs/syntax/flowchart.md b/vdocs/syntax/flowchart.md
new file mode 100644
index 0000000000..21c0b91459
--- /dev/null
+++ b/vdocs/syntax/flowchart.md
@@ -0,0 +1,699 @@
+# Flowcharts - Basic Syntax
+
+All Flowcharts are composed of **nodes**, the geometric shapes and **edges**, the arrows or lines. The mermaid code defines the way that these **nodes** and **edges** are made and interact.
+
+It can also accommodate different arrow types, multi directional arrows, and linking to and from subgraphs.
+
+> **Important note**: Do not type the word "end" as a Flowchart node. Capitalize all or any one the letters to keep the flowchart from breaking, i.e, "End" or "END". Or you can apply this [workaround](https://github.com/mermaid-js/mermaid/issues/1444#issuecomment-639528897).\*\*
+
+### A node (default)
+
+```mermaid-example
+flowchart LR
+ id
+```
+
+> **Note** The id is what is displayed in the box.
+
+### A node with text
+
+It is also possible to set text in the box that differs from the id. If this is done several times, it is the last text
+found for the node that will be used. Also if you define edges for the node later on, you can omit text definitions. The
+one previously defined will be used when rendering the box.
+
+```mermaid-example
+flowchart LR
+ id1[This is the text in the box]
+```
+
+## Graph
+
+This statement declares the direction of the Flowchart.
+
+This declares the flowchart is oriented from top to bottom (`TD` or `TB`).
+
+```mermaid-example
+flowchart TD
+ Start --> Stop
+```
+
+This declares the flowchart is oriented from left to right (`LR`).
+
+```mermaid-example
+flowchart LR
+ Start --> Stop
+```
+
+## Flowchart Orientation
+
+Possible FlowChart orientations are:
+
+- TB - top to bottom
+- TD - top-down/ same as top to bottom
+- BT - bottom to top
+- RL - right to left
+- LR - left to right
+
+## Node shapes
+
+### A node with round edges
+
+```mermaid-example
+flowchart LR
+ id1(This is the text in the box)
+```
+
+### A stadium-shaped node
+
+```mermaid-example
+flowchart LR
+ id1([This is the text in the box])
+```
+
+### A node in a subroutine shape
+
+```mermaid-example
+flowchart LR
+ id1[[This is the text in the box]]
+```
+
+### A node in a cylindrical shape
+
+```mermaid-example
+flowchart LR
+ id1[(Database)]
+```
+
+### A node in the form of a circle
+
+```mermaid-example
+flowchart LR
+ id1((This is the text in the circle))
+```
+
+### A node in an asymmetric shape
+
+```mermaid-example
+flowchart LR
+ id1>This is the text in the box]
+```
+
+Currently only the shape above is possible and not its mirror. _This might change with future releases._
+
+### A node (rhombus)
+
+```mermaid-example
+flowchart LR
+ id1{This is the text in the box}
+```
+
+### A hexagon node
+
+Code:
+
+```mmd
+flowchart LR
+ id1{{This is the text in the box}}
+```
+
+Render:
+
+```mermaid
+flowchart LR
+ id1{{This is the text in the box}}
+```
+
+### Parallelogram
+
+```mermaid-example
+flowchart TD
+ id1[/This is the text in the box/]
+```
+
+### Parallelogram alt
+
+```mermaid-example
+flowchart TD
+ id1[\This is the text in the box\]
+```
+
+### Trapezoid
+
+```mermaid-example
+flowchart TD
+ A[/Christmas\]
+```
+
+### Trapezoid alt
+
+```mermaid-example
+flowchart TD
+ B[\Go shopping/]
+```
+
+### Double circle
+
+```mermaid-example
+flowchart TD
+ id1(((This is the text in the circle)))
+```
+
+## Links between nodes
+
+Nodes can be connected with links/edges. It is possible to have different types of links or attach a text string to a link.
+
+### A link with arrow head
+
+```mermaid-example
+flowchart LR
+ A-->B
+```
+
+### An open link
+
+```mermaid-example
+flowchart LR
+ A --- B
+```
+
+### Text on links
+
+```mermaid-example
+flowchart LR
+ A-- This is the text! ---B
+```
+
+or
+
+```mermaid-example
+flowchart LR
+ A---|This is the text|B
+```
+
+### A link with arrow head and text
+
+```mermaid-example
+flowchart LR
+ A-->|text|B
+```
+
+or
+
+```mermaid-example
+flowchart LR
+ A-- text -->B
+```
+
+### Dotted link
+
+```mermaid-example
+flowchart LR;
+ A-.->B;
+```
+
+### Dotted link with text
+
+```mermaid-example
+flowchart LR
+ A-. text .-> B
+```
+
+### Thick link
+
+```mermaid-example
+flowchart LR
+ A ==> B
+```
+
+### Thick link with text
+
+```mermaid-example
+flowchart LR
+ A == text ==> B
+```
+
+### Chaining of links
+
+It is possible declare many links in the same line as per below:
+
+```mermaid-example
+flowchart LR
+ A -- text --> B -- text2 --> C
+```
+
+It is also possible to declare multiple nodes links in the same line as per below:
+
+```mermaid-example
+flowchart LR
+ a --> b & c--> d
+```
+
+You can then describe dependencies in a very expressive way. Like the one-liner below:
+
+```mermaid-example
+flowchart TB
+ A & B--> C & D
+```
+
+If you describe the same diagram using the the basic syntax, it will take four lines. A
+word of warning, one could go overboard with this making the flowchart harder to read in
+markdown form. The Swedish word `lagom` comes to mind. It means, not too much and not too little.
+This goes for expressive syntaxes as well.
+
+```mmd
+flowchart TB
+ A --> C
+ A --> D
+ B --> C
+ B --> D
+```
+
+### New arrow types
+
+There are new types of arrows supported as per below:
+
+```mermaid-example
+flowchart LR
+ A --o B
+ B --x C
+```
+
+### Multi directional arrows
+
+There is the possibility to use multidirectional arrows.
+
+```mermaid-example
+flowchart LR
+ A o--o B
+ B <--> C
+ C x--x D
+```
+
+### Minimum length of a link
+
+Each node in the flowchart is ultimately assigned to a rank in the rendered
+graph, i.e. to a vertical or horizontal level (depending on the flowchart
+orientation), based on the nodes to which it is linked. By default, links
+can span any number of ranks, but you can ask for any link to be longer
+than the others by adding extra dashes in the link definition.
+
+In the following example, two extra dashes are added in the link from node _B_
+to node _E_, so that it spans two more ranks than regular links:
+
+```mermaid-example
+flowchart TD
+ A[Start] --> B{Is it?}
+ B -->|Yes| C[OK]
+ C --> D[Rethink]
+ D --> B
+ B ---->|No| E[End]
+```
+
+> **Note** Links may still be made longer than the requested number of ranks
+> by the rendering engine to accommodate other requests.
+
+When the link label is written in the middle of the link, the extra dashes must
+be added on the right side of the link. The following example is equivalent to
+the previous one:
+
+```mermaid-example
+flowchart TD
+ A[Start] --> B{Is it?}
+ B -- Yes --> C[OK]
+ C --> D[Rethink]
+ D --> B
+ B -- No ----> E[End]
+```
+
+For dotted or thick links, the characters to add are equals signs or dots,
+as summed up in the following table:
+
+| Length | 1 | 2 | 3 |
+| ----------------- | :----: | :-----: | :------: |
+| Normal | `---` | `----` | `-----` |
+| Normal with arrow | `-->` | `--->` | `---->` |
+| Thick | `===` | `====` | `=====` |
+| Thick with arrow | `==>` | `===>` | `====>` |
+| Dotted | `-.-` | `-..-` | `-...-` |
+| Dotted with arrow | `-.->` | `-..->` | `-...->` |
+
+## Special characters that break syntax
+
+It is possible to put text within quotes in order to render more troublesome characters. As in the example below:
+
+```mermaid-example
+flowchart LR
+ id1["This is the (text) in the box"]
+```
+
+### Entity codes to escape characters
+
+It is possible to escape characters using the syntax exemplified here.
+
+```mermaid-example
+ flowchart LR
+ A["A double quote:#quot;"] -->B["A dec char:#9829;"]
+```
+
+Numbers given are base 10, so `#` can be encoded as `#35;`. It is also supported to use HTML character names.
+
+## Subgraphs
+
+```
+subgraph title
+ graph definition
+end
+```
+
+An example below:
+
+```mermaid-example
+flowchart TB
+ c1-->a2
+ subgraph one
+ a1-->a2
+ end
+ subgraph two
+ b1-->b2
+ end
+ subgraph three
+ c1-->c2
+ end
+```
+
+You can also set an explicit id for the subgraph.
+
+```mermaid-example
+flowchart TB
+ c1-->a2
+ subgraph ide1 [one]
+ a1-->a2
+ end
+```
+
+## flowcharts
+
+With the graphtype flowchart it is also possible to set edges to and from subgraphs as in the flowchart below.
+
+```mermaid-example
+flowchart TB
+ c1-->a2
+ subgraph one
+ a1-->a2
+ end
+ subgraph two
+ b1-->b2
+ end
+ subgraph three
+ c1-->c2
+ end
+ one --> two
+ three --> two
+ two --> c2
+```
+
+## Direction in subgraphs
+
+With the graphtype flowcharts you can use the direction statement to set the direction which the subgraph will render like in this example.
+
+```mermaid-example
+flowchart LR
+ subgraph TOP
+ direction TB
+ subgraph B1
+ direction RL
+ i1 -->f1
+ end
+ subgraph B2
+ direction BT
+ i2 -->f2
+ end
+ end
+ A --> TOP --> B
+ B1 --> B2
+```
+
+## Interaction
+
+It is possible to bind a click event to a node, the click can lead to either a javascript callback or to a link which will be opened in a new browser tab. **Note**: This functionality is disabled when using `securityLevel='strict'` and enabled when using `securityLevel='loose'`.
+
+```
+click nodeId callback
+click nodeId call callback()
+```
+
+- nodeId is the id of the node
+- callback is the name of a javascript function defined on the page displaying the graph, the function will be called with the nodeId as parameter.
+
+Examples of tooltip usage below:
+
+```html
+<script>
+ var callback = function () {
+ alert('A callback was triggered');
+ };
+</script>
+```
+
+The tooltip text is surrounded in double quotes. The styles of the tooltip are set by the class `.mermaidTooltip`.
+
+```mermaid-example
+flowchart LR
+ A-->B
+ B-->C
+ C-->D
+ click A callback "Tooltip for a callback"
+ click B "https://www.github.com" "This is a tooltip for a link"
+ click A call callback() "Tooltip for a callback"
+ click B href "https://www.github.com" "This is a tooltip for a link"
+```
+
+> **Success** The tooltip functionality and the ability to link to urls are available from version 0.5.2.
+
+?> Due to limitations with how Docsify handles JavaScript callback functions, an alternate working demo for the above code can be viewed at [this jsfiddle](https://jsfiddle.net/s37cjoau/3/).
+
+Links are opened in the same browser tab/window by default. It is possible to change this by adding a link target to the click definition (`_self`, `_blank`, `_parent` and `_top` are supported):
+
+```mermaid-example
+flowchart LR
+ A-->B
+ B-->C
+ C-->D
+ D-->E
+ click A "https://www.github.com" _blank
+ click B "https://www.github.com" "Open this in a new tab" _blank
+ click C href "https://www.github.com" _blank
+ click D href "https://www.github.com" "Open this in a new tab" _blank
+```
+
+Beginner's tip—a full example using interactive links in a html context:
+
+```html
+<body>
+ <pre class="mermaid">
+ flowchart LR
+ A-->B
+ B-->C
+ C-->D
+ click A callback "Tooltip"
+ click B "https://www.github.com" "This is a link"
+ click C call callback() "Tooltip"
+ click D href "https://www.github.com" "This is a link"
+ </pre>
+
+ <script>
+ var callback = function () {
+ alert('A callback was triggered');
+ };
+ var config = {
+ startOnLoad: true,
+ flowchart: { useMaxWidth: true, htmlLabels: true, curve: 'cardinal' },
+ securityLevel: 'loose',
+ };
+ mermaid.initialize(config);
+ </script>
+</body>
+```
+
+### Comments
+
+Comments can be entered within a flow diagram, which will be ignored by the parser. Comments need to be on their own line, and must be prefaced with `%%` (double percent signs). Any text after the start of the comment to the next newline will be treated as a comment, including any flow syntax
+
+```mmd
+flowchart LR
+%% this is a comment A -- text --> B{node}
+ A -- text --> B -- text2 --> C
+```
+
+## Styling and classes
+
+### Styling links
+
+It is possible to style links. For instance, you might want to style a link that is going backwards in the flow. As links
+have no ids in the same way as nodes, some other way of deciding what style the links should be attached to is required.
+Instead of ids, the order number of when the link was defined in the graph is used, or use default to apply to all links.
+In the example below the style defined in the linkStyle statement will belong to the fourth link in the graph:
+
+```
+linkStyle 3 stroke:#ff3,stroke-width:4px,color:red;
+```
+
+### Styling line curves
+
+It is possible to style the type of curve used for lines between items, if the default method does not meet your needs.
+Available curve styles include `basis`, `bump`, `linear`, `monotoneX`, `monotoneY`, `natural`, `step`, `stepAfter`,
+and `stepBefore`.
+
+In this example, a left-to-right graph uses the `stepBefore` curve style:
+
+```
+%%{ init: { 'flowchart': { 'curve': 'stepBefore' } } }%%
+graph LR
+```
+
+For a full list of available curves, including an explanation of custom curves, refer to
+the [Shapes](https://github.com/d3/d3-shape/blob/main/README.md#curves) documentation in the
+[d3-shape](https://github.com/d3/d3-shape/) project.
+
+### Styling a node
+
+It is possible to apply specific styles such as a thicker border or a different background color to a node.
+
+```mermaid-example
+flowchart LR
+ id1(Start)-->id2(Stop)
+ style id1 fill:#f9f,stroke:#333,stroke-width:4px
+ style id2 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff,stroke-dasharray: 5 5
+```
+
+#### Classes
+
+More convenient than defining the style every time is to define a class of styles and attach this class to the nodes that
+should have a different look.
+
+a class definition looks like the example below:
+
+```
+ classDef className fill:#f9f,stroke:#333,stroke-width:4px;
+```
+
+Attachment of a class to a node is done as per below:
+
+```
+ class nodeId1 className;
+```
+
+It is also possible to attach a class to a list of nodes in one statement:
+
+```
+ class nodeId1,nodeId2 className;
+```
+
+A shorter form of adding a class is to attach the classname to the node using the `:::`operator as per below:
+
+```mermaid-example
+flowchart LR
+ A:::someclass --> B
+ classDef someclass fill:#f96;
+```
+
+### Css classes
+
+It is also possible to predefine classes in css styles that can be applied from the graph definition as in the example
+below:
+
+**Example style**
+
+```html
+<style>
+ .cssClass > rect {
+ fill: #ff0000;
+ stroke: #ffff00;
+ stroke-width: 4px;
+ }
+</style>
+```
+
+**Example definition**
+
+```mermaid-example
+flowchart LR;
+ A-->B[AAA<span>BBB</span>]
+ B-->D
+ class A cssClass
+```
+
+### Default class
+
+If a class is named default it will be assigned to all classes without specific class definitions.
+
+```
+ classDef default fill:#f9f,stroke:#333,stroke-width:4px;
+```
+
+## Basic support for fontawesome
+
+It is possible to add icons from fontawesome.
+
+The icons are accessed via the syntax fa:#icon class name#.
+
+```mmd
+flowchart TD
+ B["fab:fa-twitter for peace"]
+ B-->C[fa:fa-ban forbidden]
+ B-->D(fa:fa-spinner)
+ B-->E(A fa:fa-camera-retro perhaps?)
+```
+
+```mermaid
+flowchart TD
+ B[<img class='fab' src='https://raw.githubusercontent.com/FortAwesome/Font-Awesome/afecf2af5d897b763e5e8e28d46aad2f710ccad6/svgs/brands/twitter.svg'> for peace .]
+ B-->C[<img class='fab' src='https://raw.githubusercontent.com/FortAwesome/Font-Awesome/afecf2af5d897b763e5e8e28d46aad2f710ccad6/svgs/solid/ban.svg'> forbidden .]
+ B-->D(<img class='fab' src='https://raw.githubusercontent.com/FortAwesome/Font-Awesome/afecf2af5d897b763e5e8e28d46aad2f710ccad6/svgs/solid/spinner.svg'> .)
+ B-->E(A <img class='fab' src='https://raw.githubusercontent.com/FortAwesome/Font-Awesome/afecf2af5d897b763e5e8e28d46aad2f710ccad6/svgs/solid/camera-retro.svg'> perhaps? .)
+```
+
+?> Mermaid is now only compatible with Font Awesome versions 4 and 5. Check that you are using the correct version of Font Awesome.
+
+## Graph declarations with spaces between vertices and link and without semicolon
+
+- In graph declarations, the statements also can now end without a semicolon. After release 0.2.16, ending a graph statement with semicolon is just optional. So the below graph declaration is also valid along with the old declarations of the graph.
+
+- A single space is allowed between vertices and the link. However there should not be any space between a vertex and its text and a link and its text. The old syntax of graph declaration will also work and hence this new feature is optional and is introduced to improve readability.
+
+Below is the new declaration of the graph edges which is also valid along with the old declaration of the graph edges.
+
+```mermaid-example
+flowchart LR
+ A[Hard edge] -->|Link text| B(Round edge)
+ B --> C{Decision}
+ C -->|One| D[Result one]
+ C -->|Two| E[Result two]
+```
+
+## Configuration...
+
+Is it possible to adjust the width of the rendered flowchart.
+
+This is done by defining **mermaid.flowchartConfig** or by the CLI to use a JSON file with the configuration. How to use the CLI is described in the mermaidCLI page.
+mermaid.flowchartConfig can be set to a JSON string with config parameters or the corresponding object.
+
+```javascript
+mermaid.flowchartConfig = {
+ width: 100%
+}
+```
+
+<style>
+.fa, .fab, .fal, .far, .fas {
+ width: 16px;
+ height: 16px;
+ filter: opacity(0.5);
+}
+
+.dark .fa, .dark .fab, .dark .fal, .dark .far, .dark .fas {
+ width: 16px;
+ height: 16px;
+ filter: invert(1) opacity(0.5);
+}
+</style>
diff --git a/vdocs/syntax/gantt.md b/vdocs/syntax/gantt.md
new file mode 100644
index 0000000000..5ed4c76017
--- /dev/null
+++ b/vdocs/syntax/gantt.md
@@ -0,0 +1,343 @@
+# Gantt diagrams
+
+> A Gantt chart is a type of bar chart, first developed by Karol Adamiecki in 1896, and independently by Henry Gantt in the 1910s, that illustrates a project schedule and the amount of time it would take for any one project to finish. Gantt charts illustrate number of days between the start and finish dates of the terminal elements and summary elements of a project.
+
+## A note to users
+
+Gantt Charts will record each scheduled task as one continuous bar that extends from the left to the right. The x axis represents time and the y records the different tasks and the order in which they are to be completed.
+
+It is important to remember that when a date, day, or collection of dates specific to a task are "excluded", the Gantt Chart will accommodate those changes by extending an equal number of days, towards the right, not by creating a gap inside the task.
+As shown here 
+
+However, if the excluded dates are between two tasks that are set to start consecutively, the excluded dates will be skipped graphically and left blank, and the following task will begin after the end of the excluded dates.
+As shown here 
+
+A Gantt chart is useful for tracking the amount of time it would take before a project is finished, but it can also be used to graphically represent "non-working days", with a few tweaks.
+
+Mermaid can render Gantt diagrams as SVG, PNG or a MarkDown link that can be pasted into docs.
+
+```mermaid-example
+gantt
+ title A Gantt Diagram
+ dateFormat YYYY-MM-DD
+ section Section
+ A task :a1, 2014-01-01, 30d
+ Another task :after a1 , 20d
+ section Another
+ Task in sec :2014-01-12 , 12d
+ another task : 24d
+```
+
+## Syntax
+
+```mermaid-example
+gantt
+ dateFormat YYYY-MM-DD
+ title Adding GANTT diagram functionality to mermaid
+ excludes weekends
+ %% (`excludes` accepts specific dates in YYYY-MM-DD format, days of the week ("sunday") or "weekends", but not the word "weekdays".)
+
+ section A section
+ Completed task :done, des1, 2014-01-06,2014-01-08
+ Active task :active, des2, 2014-01-09, 3d
+ Future task : des3, after des2, 5d
+ Future task2 : des4, after des3, 5d
+
+ section Critical tasks
+ Completed task in the critical line :crit, done, 2014-01-06,24h
+ Implement parser and jison :crit, done, after des1, 2d
+ Create tests for parser :crit, active, 3d
+ Future task in critical line :crit, 5d
+ Create tests for renderer :2d
+ Add to mermaid :1d
+ Functionality added :milestone, 2014-01-25, 0d
+
+ section Documentation
+ Describe gantt syntax :active, a1, after des1, 3d
+ Add gantt diagram to demo page :after a1 , 20h
+ Add another diagram to demo page :doc1, after a1 , 48h
+
+ section Last section
+ Describe gantt syntax :after doc1, 3d
+ Add gantt diagram to demo page :20h
+ Add another diagram to demo page :48h
+```
+
+It is possible to set multiple dependencies separated by space:
+
+```mermaid-example
+ gantt
+ apple :a, 2017-07-20, 1w
+ banana :crit, b, 2017-07-23, 1d
+ cherry :active, c, after b a, 1d
+```
+
+### Title
+
+The `title` is an _optional_ string to be displayed at the top of the Gantt chart to describe the chart as a whole.
+
+### Section statements
+
+You can divide the chart into various sections, for example to separate different parts of a project like development and documentation.
+
+To do so, start a line with the `section` keyword and give it a name. (Note that unlike with the [title for the entire chart](#title), this name is _required_.
+
+### Milestones
+
+You can add milestones to the diagrams. Milestones differ from tasks as they represent a single instant in time and are identified by the keyword `milestone`. Below is an example on how to use milestones. As you may notice, the exact location of the milestone is determined by the initial date for the milestone and the "duration" of the task this way: _initial date_+_duration_/2.
+
+```mermaid-example
+gantt
+dateFormat HH:mm
+axisFormat %H:%M
+Initial milestone : milestone, m1, 17:49,2min
+taska2 : 10min
+taska3 : 5min
+Final milestone : milestone, m2, 18:14, 2min
+```
+
+## Setting dates
+
+`dateFormat` defines the format of the date **input** of your gantt elements. How these dates are represented in the rendered chart **output** are defined by `axisFormat`.
+
+### Input date format
+
+The default input date format is `YYYY-MM-DD`. You can define your custom `dateFormat`.
+
+```
+dateFormat YYYY-MM-DD
+```
+
+The following formatting options are supported:
+
+```
+Input Example Description:
+YYYY 2014 4 digit year
+YY 14 2 digit year
+Q 1..4 Quarter of year. Sets month to first month in quarter.
+M MM 1..12 Month number
+MMM MMMM January..Dec Month name in locale set by moment.locale()
+D DD 1..31 Day of month
+Do 1st..31st Day of month with ordinal
+DDD DDDD 1..365 Day of year
+X 1410715640.579 Unix timestamp
+x 1410715640579 Unix ms timestamp
+H HH 0..23 24 hour time
+h hh 1..12 12 hour time used with a A.
+a A am pm Post or ante meridiem
+m mm 0..59 Minutes
+s ss 0..59 Seconds
+S 0..9 Tenths of a second
+SS 0..99 Hundreds of a second
+SSS 0..999 Thousandths of a second
+Z ZZ +12:00 Offset from UTC as +-HH:mm, +-HHmm, or Z
+```
+
+More info in: https://momentjs.com/docs/#/parsing/string-format/
+
+### Output date format on the axis
+
+The default output date format is YYYY-MM-DD. You can define your custom `axisFormat`, like `2020-Q1` for the first quarter of the year 2020.
+
+```
+axisFormat %Y-%m-%d
+```
+
+The following formatting strings are supported:
+
+```
+%a - abbreviated weekday name.
+%A - full weekday name.
+%b - abbreviated month name.
+%B - full month name.
+%c - date and time, as "%a %b %e %H:%M:%S %Y".
+%d - zero-padded day of the month as a decimal number [01,31].
+%e - space-padded day of the month as a decimal number [ 1,31]; equivalent to %_d.
+%H - hour (24-hour clock) as a decimal number [00,23].
+%I - hour (12-hour clock) as a decimal number [01,12].
+%j - day of the year as a decimal number [001,366].
+%m - month as a decimal number [01,12].
+%M - minute as a decimal number [00,59].
+%L - milliseconds as a decimal number [000, 999].
+%p - either AM or PM.
+%S - second as a decimal number [00,61].
+%U - week number of the year (Sunday as the first day of the week) as a decimal number [00,53].
+%w - weekday as a decimal number [0(Sunday),6].
+%W - week number of the year (Monday as the first day of the week) as a decimal number [00,53].
+%x - date, as "%m/%d/%Y".
+%X - time, as "%H:%M:%S".
+%y - year without century as a decimal number [00,99].
+%Y - year with century as a decimal number.
+%Z - time zone offset, such as "-0700".
+%% - a literal "%" character.
+```
+
+More info in: https://github.com/mbostock/d3/wiki/Time-Formatting
+
+## Comments
+
+Comments can be entered within a gantt chart, which will be ignored by the parser. Comments need to be on their own line and must be prefaced with `%%` (double percent signs). Any text after the start of the comment to the next newline will be treated as a comment, including any diagram syntax
+
+```mmd
+gantt
+ title A Gantt Diagram
+ %% this is a comment
+ dateFormat YYYY-MM-DD
+ section Section
+ A task :a1, 2014-01-01, 30d
+ Another task :after a1 , 20d
+ section Another
+ Task in sec :2014-01-12 , 12d
+ another task : 24d
+
+```
+
+## Styling
+
+Styling of the a gantt diagram is done by defining a number of css classes. During rendering, these classes are extracted from the file located at src/themes/gantt.scss
+
+### Classes used
+
+| Class | Description |
+| --------------------- | ---------------------------------------------------------------------- |
+| grid.tick | Styling for the Grid Lines |
+| grid.path | Styling for the Grid's borders |
+| .taskText | Task Text Styling |
+| .taskTextOutsideRight | Styling for Task Text that exceeds the activity bar towards the right. |
+| .taskTextOutsideLeft | Styling for Task Text that exceeds the activity bar, towards the left. |
+| todayMarker | Toggle and Styling for the "Today Marker" |
+
+### Sample stylesheet
+
+```css
+.grid .tick {
+ stroke: lightgrey;
+ opacity: 0.3;
+ shape-rendering: crispEdges;
+}
+.grid path {
+ stroke-width: 0;
+}
+
+#tag {
+ color: white;
+ background: #fa283d;
+ width: 150px;
+ position: absolute;
+ display: none;
+ padding: 3px 6px;
+ margin-left: -80px;
+ font-size: 11px;
+}
+
+#tag:before {
+ border: solid transparent;
+ content: ' ';
+ height: 0;
+ left: 50%;
+ margin-left: -5px;
+ position: absolute;
+ width: 0;
+ border-width: 10px;
+ border-bottom-color: #fa283d;
+ top: -20px;
+}
+.taskText {
+ fill: white;
+ text-anchor: middle;
+}
+.taskTextOutsideRight {
+ fill: black;
+ text-anchor: start;
+}
+.taskTextOutsideLeft {
+ fill: black;
+ text-anchor: end;
+}
+```
+
+## Today marker
+
+You can style or hide the marker for the current date. To style it, add a value for the `todayMarker` key.
+
+```
+todayMarker stroke-width:5px,stroke:#0f0,opacity:0.5
+```
+
+To hide the marker, set `todayMarker` to `off`.
+
+```
+todayMarker off
+```
+
+## Configuration
+
+It is possible to adjust the margins for rendering the gantt diagram.
+
+This is done by defining the `ganttConfig` part of the configuration object.
+How to use the CLI is described in the [mermaidCLI](../config/mermaidCLI) page.
+
+mermaid.ganttConfig can be set to a JSON string with config parameters or the corresponding object.
+
+```javascript
+mermaid.ganttConfig = {
+ titleTopMargin: 25,
+ barHeight: 20,
+ barGap: 4,
+ topPadding: 75,
+ sidePadding: 75,
+};
+```
+
+### Possible configuration params:
+
+| Param | Description | Default value |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------- |
+| mirrorActor | Turns on/off the rendering of actors below the diagram as well as above it | false |
+| bottomMarginAdj | Adjusts how far down the graph ended. Wide borders styles with css could generate unwanted clipping which is why this config param exists. | 1 |
+
+## Interaction
+
+It is possible to bind a click event to a task. The click can lead to either a javascript callback or to a link which will be opened in the current browser tab. **Note**: This functionality is disabled when using `securityLevel='strict'` and enabled when using `securityLevel='loose'`.
+
+```
+click taskId call callback(arguments)
+click taskId href URL
+```
+
+- taskId is the id of the task
+- callback is the name of a javascript function defined on the page displaying the graph, the function will be called with the taskId as the parameter if no other arguments are specified.
+
+Beginner's tip—a full example using interactive links in an html context:
+
+```html
+<body>
+ <pre class="mermaid">
+ gantt
+ dateFormat YYYY-MM-DD
+
+ section Clickable
+ Visit mermaidjs :active, cl1, 2014-01-07, 3d
+ Print arguments :cl2, after cl1, 3d
+ Print task :cl3, after cl2, 3d
+
+ click cl1 href "https://mermaidjs.github.io/"
+ click cl2 call printArguments("test1", "test2", test3)
+ click cl3 call printTask()
+ </pre>
+
+ <script>
+ var printArguments = function (arg1, arg2, arg3) {
+ alert('printArguments called with arguments: ' + arg1 + ', ' + arg2 + ', ' + arg3);
+ };
+ var printTask = function (taskId) {
+ alert('taskId: ' + taskId);
+ };
+ var config = {
+ startOnLoad: true,
+ securityLevel: 'loose',
+ };
+ mermaid.initialize(config);
+ </script>
+</body>
+```
diff --git a/vdocs/syntax/gitGraph.md b/vdocs/syntax/gitGraph.md
new file mode 100644
index 0000000000..adfaabf40c
--- /dev/null
+++ b/vdocs/syntax/gitGraph.md
@@ -0,0 +1,1016 @@
+# Gitgraph Diagrams
+
+> A Git Graph is a pictorial representation of git commits and git actions(commands) on various branches.
+
+These kind of diagram are particularly helpful to developers and devops teams to share their Git branching strategies. For example, it makes it easier to visualize how git flow works.
+
+Mermaid can render Git diagrams
+
+```mermaid-example
+ gitGraph
+ commit
+ commit
+ branch develop
+ checkout develop
+ commit
+ commit
+ checkout main
+ merge develop
+ commit
+ commit
+```
+
+In Mermaid, we support the basic git operations like:
+
+- _commit_ : Representing a new commit on the current branch.
+- _branch_ : To create & switch to a new branch, setting it as the current branch.
+- _checkout_ : To checking out an existing branch and setting it as the current branch.
+- _merge_ : To merge an existing branch onto the current branch.
+
+With the help of these key git commands, you will be able to draw a gitgraph in Mermaid very easily and quickly.
+Entity names are often capitalized, although there is no accepted standard on this, and it is not required in Mermaid.
+
+## Syntax
+
+Mermaid syntax for a gitgraph is very straight-forward and simple. It follows a declarative-approach, where each commit is drawn on the timeline in the diagram, in order of its occurrences/presence in code. Basically, it follows the insertion order for each command.
+
+First thing you do is to declare your diagram type using the **gitgraph** keyword. This `gitgraph` keyword, tells Mermaid that you wish to draw a gitgraph, and parse the diagram code accordingly.
+
+Each gitgraph, is initialized with **_main_** branch. So unless you create a different branch, by-default the commits will go to the main branch. This is driven with how git works, where in the beginning you always start with the main branch (formerly called as **_master_** branch). And by-default, `main` branch is set as your **_current branch_**.
+
+You make use of **_commit_** keyword to register a commit on the current branch. Let see how this works:
+
+A simple gitgraph showing three commits on the default (**_main_**) branch:
+
+```mermaid-example
+ gitGraph
+ commit
+ commit
+ commit
+```
+
+If you look closely at the previous example, you can see the default branch `main` along with three commits. Also, notice that by default each commit has been given a unique & random ID. What if you wanted to give your own custom ID to a commit? Yes, it is possible to do that with Mermaid.
+
+### Adding custom commit id
+
+For a given commit you may specify a custom ID at the time of declaring it using the `id` attribute, followed by `:` and your custom value within a `""` quote. For example: `commit id: "your_custom_id"`
+
+Let us see how this works with the help of the following diagram:
+
+```mermaid-example
+ gitGraph
+ commit id: "Alpha"
+ commit id: "Beta"
+ commit id: "Gamma"
+```
+
+In this example, we have given our custom IDs to the commits.
+
+### Modifying commit type
+
+In Mermaid, a commit can be of three type, which render a bit different in the diagram. These types are:
+
+- `NORMAL` : Default commit type. Represented by a solid circle in the diagram
+- `REVERSE` : To emphasize a commit as a reverse commit. Represented by a crossed solid circle in the diagram.
+- `HIGHLIGHT` : To highlight a particular commit in the diagram. Represented by a filled rectangle in the diagram.
+
+For a given commit you may specify its type at the time of declaring it using the `type` attribute, followed by `:` and the required type option discussed above. For example: `commit type: HIGHLIGHT`
+
+NOTE: If no commit type is specified, `NORMAL` is picked as default.
+
+Let us see how these different commit type look with the help of the following diagram:
+
+```mermaid-example
+ gitGraph
+ commit id: "Normal"
+ commit
+ commit id: "Reverse" type: REVERSE
+ commit
+ commit id: "Highlight" type: HIGHLIGHT
+ commit
+```
+
+In this example, we have specified different types to each commit. Also, see how we have included both `id` and `type` together at the time of declaring our commits.
+
+### Adding Tags
+
+For a given commit you may decorate it as a **tag**, similar to the concept of tags or release version in git world.
+You can attach a custom tag at the time of declaring a commit using the `tag` attribute, followed by `:` and your custom value within `""` quote. For example: `commit tag: "your_custom_tag"`
+
+Let us see how this works with the help of the following diagram:
+
+```mermaid-example
+ gitGraph
+ commit
+ commit id: "Normal" tag: "v1.0.0"
+ commit
+ commit id: "Reverse" type: REVERSE tag: "RC_1"
+ commit
+ commit id: "Highlight" type: HIGHLIGHT tag: "8.8.4"
+ commit
+```
+
+In this example, we have given custom tags to the commits. Also, see how we have combined all these attributes in a single commit declaration. You can mix-match these attributes as you like.
+
+### Create a new branch
+
+In Mermaid, in-order to create a new branch, you make use of the `branch` keyword. You also need to provide a name of the new branch. The name has to be unique and cannot be that of an existing branch. Usage example: `branch develop`
+
+When Mermaid, reads the `branch` keyword, it creates a new branch and sets it as the current branch. Equivalent to you creating a new branch and checking it out in Git world.
+
+Let see this in an example:
+
+```mermaid-example
+ gitGraph
+ commit
+ commit
+ branch develop
+ commit
+ commit
+ commit
+```
+
+In this example, see how we started with default `main` branch, and pushed two commits on that.
+Then we created the `develop` branch, and all commits afterwards are put on the `develop` branch as it became the current branch.
+
+### Checking out an existing branch
+
+In Mermaid, in order to switch to an existing branch, you make use of the `checkout` keyword. You also need to provide a name of an existing branch. If no branch is found with the given name, it will result in console error. Usage example: `checkout develop`
+
+When Mermaid, reads the `checkout` keyword, it finds the given branch and sets it as the current branch. Equivalent to checking out a branch in the Git world.
+
+Let see modify our previous example:
+
+```mermaid-example
+ gitGraph
+ commit
+ commit
+ branch develop
+ commit
+ commit
+ commit
+ checkout main
+ commit
+ commit
+```
+
+In this example, see how we started with default `main` branch, and pushed two commits on that.
+Then we created the `develop` branch, and all three commits afterwards are put on the `develop` branch as it became the current branch.
+After this we made use of the `checkout` keyword to set the current branch as `main`, and all commit that follow are registered against the current branch, i.e. `main`.
+
+### Merging two branches
+
+In Mermaid, in order to merge or join to an existing branch, you make use of the `merge` keyword. You also need to provide the name of an existing branch to merge from. If no branch is found with the given name, it will result in console error. Also, you can only merge two separate branches, and cannot merge a branch with itself. In such case an error is throw.
+
+Usage example: `merge develop`
+
+When Mermaid, reads the `merge` keyword, it finds the given branch and its head commit (the last commit on that branch), and joins it with the head commit on the **current branch**. Each merge results in a **_merge commit_**, represented in the diagram with **filled double circle**.
+
+Let us modify our previous example to merge our two branches:
+
+```mermaid-example
+ gitGraph
+ commit
+ commit
+ branch develop
+ commit
+ commit
+ commit
+ checkout main
+ commit
+ commit
+ merge develop
+ commit
+ commit
+```
+
+In this example, see how we started with default `main` branch, and pushed two commits on that.
+Then we created the `develop` branch, and all three commits afterwards are put on the `develop` branch as it became the current branch.
+After this we made use of the `checkout` keyword to set the current branch as `main`, and all commits that follow are registered against the current branch, i.e. `main`.
+After this we merge the `develop` branch onto the current branch `main`, resulting in a merge commit.
+Since the current branch at this point is still `main`, the last two commits are registered against that.
+
+You can also decorate your merge with similar attributes as you did for the commit using:
+
+- `id`--> To override the default ID with custom ID
+- `tag`--> To add a custom tag to your merge commit
+- `type`--> To override the default shape of merge commit. Here you can use other commit type mentioned earlier.
+
+And you can choose to use none, some or all of these attributes together.
+For example: `merge develop id: "my_custom_id" tag: "my_custom_tag" type: REVERSE`
+
+Let us see how this works with the help of the following diagram:
+
+```mermaid-example
+ gitGraph
+ commit id: "1"
+ commit id: "2"
+ branch nice_feature
+ checkout nice_feature
+ commit id: "3"
+ checkout main
+ commit id: "4"
+ checkout nice_feature
+ branch very_nice_feature
+ checkout very_nice_feature
+ commit id: "5"
+ checkout main
+ commit id: "6"
+ checkout nice_feature
+ commit id: "7"
+ checkout main
+ merge nice_feature id: "customID" tag: "customTag" type: REVERSE
+ checkout very_nice_feature
+ commit id: "8"
+ checkout main
+ commit id: "9"
+```
+
+### Cherry Pick commit from another branch
+
+Similar to how 'git' allows you to cherry-pick a commit from **another branch** onto the **current** branch, Mermaid also supports this functionality. You can also cherry-pick a commit from another branch using the `cherry-pick` keyword.
+
+To use the `cherry-pick` keyword, you must specify the id using the `id` attribute, followed by `:` and your desired commit id within a `""` quote. For example:
+
+`cherry-pick id: "your_custom_id"`
+
+Here, a new commit representing the cherry-pick is created on the current branch, and is visually highlighted in the diagram with a **cherry** and a tag depicting the commit id from which it is cherry-picked from.
+
+A few important rules to note here are:
+
+1. You need to provide the `id` for an existing commit to be cherry-picked. If given commit id does not exist it will result in an error. For this, make use of the `commit id:$value` format of declaring commits. See the examples from above.
+2. The given commit must not exist on the current branch. The cherry-picked commit must always be a different branch than the current branch.
+3. Current branch must have at least one commit, before you can cherry-pick, otherwise it will cause an error is throw.
+
+Let see an example:
+
+```mermaid-example
+ gitGraph
+ commit id: "ZERO"
+ branch develop
+ commit id:"A"
+ checkout main
+ commit id:"ONE"
+ checkout develop
+ commit id:"B"
+ checkout main
+ commit id:"TWO"
+ cherry-pick id:"A"
+ commit id:"THREE"
+ checkout develop
+ commit id:"C"
+```
+
+## Gitgraph specific configuration options
+
+In Mermaid, you have the option to configure the gitgraph diagram. You can configure the following options:
+
+- `showBranches` : Boolean, default is `true`. If set to `false`, the branches are not shown in the diagram.
+- `showCommitLabel` : Boolean, default is `true`. If set to `false`, the commit labels are not shown in the diagram.
+- `mainBranchName` : String, default is `main`. The name of the default/root branch.
+- `mainBranchOrder` : Position of the main branch in the list of branches. default is `0`, meaning, by default `main` branch is the first in the order.
+
+Let's look at them one by one.
+
+## Hiding Branch names and lines
+
+Sometimes you may want to hide the branch names and lines from the diagram. You can do this by using the `showBranches` keyword. By default its value is `true`. You can set it to `false` using directives.
+
+Usage example:
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'base', 'gitGraph': {'showBranches': false}} }%%
+ gitGraph
+ commit
+ branch hotfix
+ checkout hotfix
+ commit
+ branch develop
+ checkout develop
+ commit id:"ash" tag:"abc"
+ branch featureB
+ checkout featureB
+ commit type:HIGHLIGHT
+ checkout main
+ checkout hotfix
+ commit type:NORMAL
+ checkout develop
+ commit type:REVERSE
+ checkout featureB
+ commit
+ checkout main
+ merge hotfix
+ checkout featureB
+ commit
+ checkout develop
+ branch featureA
+ commit
+ checkout develop
+ merge hotfix
+ checkout featureA
+ commit
+ checkout featureB
+ commit
+ checkout develop
+ merge featureA
+ branch release
+ checkout release
+ commit
+ checkout main
+ commit
+ checkout release
+ merge main
+ checkout develop
+ merge release
+```
+
+## Commit labels Layout: Rotated or Horizontal
+
+Mermaid supports two types of commit labels layout. The default layout is **rotated**, which means the labels are placed below the commit circle, rotated at 45 degrees for better readability. This is particularly useful for commits with long labels.
+
+The other option is **horizontal**, which means the labels are placed below the commit circle centred horizontally, and are not rotated. This is particularly useful for commits with short labels.
+
+You can change the layout of the commit labels by using the `rotateCommitLabel` keyword in the directive. It defaults to `true`, which means the commit labels are rotated.
+
+Usage example: Rotated commit labels
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'base', 'gitGraph': {'rotateCommitLabel': true}} }%%
+gitGraph
+ commit id: "feat(api): ..."
+ commit id: "a"
+ commit id: "b"
+ commit id: "fix(client): .extra long label.."
+ branch c2
+ commit id: "feat(modules): ..."
+ commit id: "test(client): ..."
+ checkout main
+ commit id: "fix(api): ..."
+ commit id: "ci: ..."
+ branch b1
+ commit
+ branch b2
+ commit
+```
+
+Usage example: Horizontal commit labels
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'base', 'gitGraph': {'rotateCommitLabel': false}} }%%
+gitGraph
+ commit id: "feat(api): ..."
+ commit id: "a"
+ commit id: "b"
+ commit id: "fix(client): .extra long label.."
+ branch c2
+ commit id: "feat(modules): ..."
+ commit id: "test(client): ..."
+ checkout main
+ commit id: "fix(api): ..."
+ commit id: "ci: ..."
+ branch b1
+ commit
+ branch b2
+ commit
+```
+
+## Hiding commit labels
+
+Sometimes you may want to hide the commit labels from the diagram. You can do this by using the `showCommitLabel` keyword. By default its value is `true`. You can set it to `false` using directives.
+
+Usage example:
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'base', 'gitGraph': {'showBranches': false,'showCommitLabel': false}} }%%
+ gitGraph
+ commit
+ branch hotfix
+ checkout hotfix
+ commit
+ branch develop
+ checkout develop
+ commit id:"ash"
+ branch featureB
+ checkout featureB
+ commit type:HIGHLIGHT
+ checkout main
+ checkout hotfix
+ commit type:NORMAL
+ checkout develop
+ commit type:REVERSE
+ checkout featureB
+ commit
+ checkout main
+ merge hotfix
+ checkout featureB
+ commit
+ checkout develop
+ branch featureA
+ commit
+ checkout develop
+ merge hotfix
+ checkout featureA
+ commit
+ checkout featureB
+ commit
+ checkout develop
+ merge featureA
+ branch release
+ checkout release
+ commit
+ checkout main
+ commit
+ checkout release
+ merge main
+ checkout develop
+ merge release
+```
+
+## Customizing main branch name
+
+Sometimes you may want to customize the name of the main/default branch. You can do this by using the `mainBranchName` keyword. By default its value is `main`. You can set it to any string using directives.
+
+Usage example:
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'base', 'gitGraph': {'showBranches': true, 'showCommitLabel':true,'mainBranchName': 'MetroLine1'}} }%%
+ gitGraph
+ commit id:"NewYork"
+ commit id:"Dallas"
+ branch MetroLine2
+ commit id:"LosAngeles"
+ commit id:"Chicago"
+ commit id:"Houston"
+ branch MetroLine3
+ commit id:"Phoenix"
+ commit type: HIGHLIGHT id:"Denver"
+ commit id:"Boston"
+ checkout MetroLine1
+ commit id:"Atlanta"
+ merge MetroLine3
+ commit id:"Miami"
+ commit id:"Washington"
+ merge MetroLine2 tag:"MY JUNCTION"
+ commit id:"Boston"
+ commit id:"Detroit"
+ commit type:REVERSE id:"SanFrancisco"
+```
+
+Look at the imaginary railroad map created using Mermaid. Here, we have changed the default main branch name to `MetroLine1`.
+
+## Customizing branch ordering
+
+In Mermaid, by default the branches are shown in the order of their definition or appearance in the diagram code.
+
+Sometimes you may want to customize the order of the branches. You can do this by using the `order` keyword next the branch definition. You can set it to a positive number.
+
+Mermaid follows the given precedence order of the `order` keyword.
+
+- Main branch is always shown first as it has default order value of `0`. (unless its order is modified and changed from `0` using the `mainBranchOrder` keyword in the config)
+- Next, All branches without an `order` are shown in the order of their appearance in the diagram code.
+- Next, All branches with an `order` are shown in the order of their `order` value.
+
+To fully control the order of all the branches, you must define `order` for all the branches.
+
+Usage example:
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'base', 'gitGraph': {'showBranches': true, 'showCommitLabel':true}} }%%
+ gitGraph
+ commit
+ branch test1 order: 3
+ branch test2 order: 2
+ branch test3 order: 1
+
+```
+
+Look at the diagram, all the branches are following the order defined.
+
+Usage example:
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'base', 'gitGraph': {'showBranches': true, 'showCommitLabel':true,'mainBranchOrder': 2}} }%%
+ gitGraph
+ commit
+ branch test1 order: 3
+ branch test2
+ branch test3
+ branch test4 order: 1
+
+```
+
+Look at the diagram, here, all the branches without a specified order are drawn in their order of definition.
+Then, `test4` branch is drawn because the order of `1`.
+Then, `main` branch is drawn because the order of `2`.
+And, lastly `test1`is drawn because the order of `3`.
+
+NOTE: Because we have overridden the `mainBranchOrder` to `2`, the `main` branch is not drawn in the beginning, instead follows the ordering.
+
+Here, we have changed the default main branch name to `MetroLine1`.
+
+## Themes
+
+Mermaid supports a bunch of pre-defined themes which you can use to find the right one for you. PS: you can actually override an existing theme's variable to get your own custom theme going. Learn more about theming your diagram [here](../config/theming.md).
+
+The following are the different pre-defined theme options:
+
+- `base`
+- `forest`
+- `dark`
+- `default`
+- `neutral`
+
+**NOTE**: To change theme you can either use the `initialize` call or _directives_. Learn more about [directives](../config/directives.md)
+Let's put them to use, and see how our sample diagram looks in different themes:
+
+### Base Theme
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'base' } }%%
+ gitGraph
+ commit
+ branch hotfix
+ checkout hotfix
+ commit
+ branch develop
+ checkout develop
+ commit id:"ash" tag:"abc"
+ branch featureB
+ checkout featureB
+ commit type:HIGHLIGHT
+ checkout main
+ checkout hotfix
+ commit type:NORMAL
+ checkout develop
+ commit type:REVERSE
+ checkout featureB
+ commit
+ checkout main
+ merge hotfix
+ checkout featureB
+ commit
+ checkout develop
+ branch featureA
+ commit
+ checkout develop
+ merge hotfix
+ checkout featureA
+ commit
+ checkout featureB
+ commit
+ checkout develop
+ merge featureA
+ branch release
+ checkout release
+ commit
+ checkout main
+ commit
+ checkout release
+ merge main
+ checkout develop
+ merge release
+```
+
+### Forest Theme
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'forest' } }%%
+ gitGraph
+ commit
+ branch hotfix
+ checkout hotfix
+ commit
+ branch develop
+ checkout develop
+ commit id:"ash" tag:"abc"
+ branch featureB
+ checkout featureB
+ commit type:HIGHLIGHT
+ checkout main
+ checkout hotfix
+ commit type:NORMAL
+ checkout develop
+ commit type:REVERSE
+ checkout featureB
+ commit
+ checkout main
+ merge hotfix
+ checkout featureB
+ commit
+ checkout develop
+ branch featureA
+ commit
+ checkout develop
+ merge hotfix
+ checkout featureA
+ commit
+ checkout featureB
+ commit
+ checkout develop
+ merge featureA
+ branch release
+ checkout release
+ commit
+ checkout main
+ commit
+ checkout release
+ merge main
+ checkout develop
+ merge release
+```
+
+### Default Theme
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'default' } }%%
+ gitGraph
+ commit type:HIGHLIGHT
+ branch hotfix
+ checkout hotfix
+ commit
+ branch develop
+ checkout develop
+ commit id:"ash" tag:"abc"
+ branch featureB
+ checkout featureB
+ commit type:HIGHLIGHT
+ checkout main
+ checkout hotfix
+ commit type:NORMAL
+ checkout develop
+ commit type:REVERSE
+ checkout featureB
+ commit
+ checkout main
+ merge hotfix
+ checkout featureB
+ commit
+ checkout develop
+ branch featureA
+ commit
+ checkout develop
+ merge hotfix
+ checkout featureA
+ commit
+ checkout featureB
+ commit
+ checkout develop
+ merge featureA
+ branch release
+ checkout release
+ commit
+ checkout main
+ commit
+ checkout release
+ merge main
+ checkout develop
+ merge release
+```
+
+### Dark Theme
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'dark' } }%%
+ gitGraph
+ commit
+ branch hotfix
+ checkout hotfix
+ commit
+ branch develop
+ checkout develop
+ commit id:"ash" tag:"abc"
+ branch featureB
+ checkout featureB
+ commit type:HIGHLIGHT
+ checkout main
+ checkout hotfix
+ commit type:NORMAL
+ checkout develop
+ commit type:REVERSE
+ checkout featureB
+ commit
+ checkout main
+ merge hotfix
+ checkout featureB
+ commit
+ checkout develop
+ branch featureA
+ commit
+ checkout develop
+ merge hotfix
+ checkout featureA
+ commit
+ checkout featureB
+ commit
+ checkout develop
+ merge featureA
+ branch release
+ checkout release
+ commit
+ checkout main
+ commit
+ checkout release
+ merge main
+ checkout develop
+ merge release
+```
+
+### Neutral Theme
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'neutral' } }%%
+ gitGraph
+ commit
+ branch hotfix
+ checkout hotfix
+ commit
+ branch develop
+ checkout develop
+ commit id:"ash" tag:"abc"
+ branch featureB
+ checkout featureB
+ commit type:HIGHLIGHT
+ checkout main
+ checkout hotfix
+ commit type:NORMAL
+ checkout develop
+ commit type:REVERSE
+ checkout featureB
+ commit
+ checkout main
+ merge hotfix
+ checkout featureB
+ commit
+ checkout develop
+ branch featureA
+ commit
+ checkout develop
+ merge hotfix
+ checkout featureA
+ commit
+ checkout featureB
+ commit
+ checkout develop
+ merge featureA
+ branch release
+ checkout release
+ commit
+ checkout main
+ commit
+ checkout release
+ merge main
+ checkout develop
+ merge release
+```
+
+## Customize using Theme Variables
+
+Mermaid allows you to customize your diagram using theme variables which govern the look and feel of various elements of the diagram.
+
+For understanding let us take a sample diagram with theme `default`, the default values of the theme variables is picked automatically from the theme. Later on we will see how to override the default values of the theme variables.
+
+See how the default theme is used to set the colors for the branches:
+
+```mermaid-example
+%%{init: { 'logLevel': 'debug', 'theme': 'default' } }%%
+ gitGraph
+ commit
+ branch develop
+ commit tag:"v1.0.0"
+ commit
+ checkout main
+ commit type: HIGHLIGHT
+ commit
+ merge develop
+ commit
+ branch featureA
+ commit
+```
+
+> #### IMPORTANT:
+>
+> Mermaid supports the theme variables to override the default values for **up to 8 branches**, i.e., you can set the color/styling of up to 8 branches using theme variables. After this threshold of 8 branches, the theme variables are reused in the cyclic manner, i.e. the 9th branch will use the color/styling of the 1st branch, or the branch at index position '8' will use the color/styling of the branch at index position '0'.
+> _More on this in the next section. See examples on **Customizing branch label colors** below_
+
+### Customizing branch colors
+
+You can customize the branch colors using the `git0` to `git7` theme variables. Mermaid allows you to set the colors for up-to 8 branches, where `git0` variable will drive the value of the first branch, `git1` will drive the value of the second branch and so on.
+
+NOTE: Default values for these theme variables are picked from the selected theme. If you want to override the default values, you can use the `initialize` call to add your custom theme variable values.
+
+Example:
+
+Now let's override the default values for the `git0` to `git3` variables:
+
+```mermaid-example
+ %%{init: { 'logLevel': 'debug', 'theme': 'default' , 'themeVariables': {
+ 'git0': '#ff0000',
+ 'git1': '#00ff00',
+ 'git2': '#0000ff',
+ 'git3': '#ff00ff',
+ 'git4': '#00ffff',
+ 'git5': '#ffff00',
+ 'git6': '#ff00ff',
+ 'git7': '#00ffff'
+ } } }%%
+ gitGraph
+ commit
+ branch develop
+ commit tag:"v1.0.0"
+ commit
+ checkout main
+ commit type: HIGHLIGHT
+ commit
+ merge develop
+ commit
+ branch featureA
+ commit
+
+```
+
+See how the branch colors are changed to the values specified in the theme variables.
+
+### Customizing branch label colors
+
+You can customize the branch label colors using the `gitBranchLabel0` to `gitBranchLabel7` theme variables. Mermaid allows you to set the colors for up-to 8 branches, where `gitBranchLabel0` variable will drive the value of the first branch label, `gitBranchLabel1` will drive the value of the second branch label and so on.
+
+Lets see how the default theme is used to set the colors for the branch labels:
+
+Now let's override the default values for the `gitBranchLabel0` to `gitBranchLabel2` variables:
+
+```mermaid-example
+ %%{init: { 'logLevel': 'debug', 'theme': 'default' , 'themeVariables': {
+ 'gitBranchLabel0': '#ffffff',
+ 'gitBranchLabel1': '#ffffff',
+ 'gitBranchLabel2': '#ffffff',
+ 'gitBranchLabel3': '#ffffff',
+ 'gitBranchLabel4': '#ffffff',
+ 'gitBranchLabel5': '#ffffff',
+ 'gitBranchLabel6': '#ffffff',
+ 'gitBranchLabel7': '#ffffff',
+ 'gitBranchLabel8': '#ffffff',
+ 'gitBranchLabel9': '#ffffff'
+ } } }%%
+ gitGraph
+ checkout main
+ branch branch1
+ branch branch2
+ branch branch3
+ branch branch4
+ branch branch5
+ branch branch6
+ branch branch7
+ branch branch8
+ branch branch9
+ checkout branch1
+ commit
+```
+
+Here, you can see that `branch8` and `branch9` colors and the styles are being picked from branch at index position `0` (`main`) and `1`(`branch1`) respectively, i.e., **branch themeVariables are repeated cyclically**.
+
+### Customizing Commit colors
+
+You can customize commit using the `commitLabelColor` and `commitLabelBackground` theme variables for changes in the commit label color and background color respectively.
+
+Example:
+Now let's override the default values for the `commitLabelColor` to `commitLabelBackground` variables:
+
+```mermaid-example
+ %%{init: { 'logLevel': 'debug', 'theme': 'default' , 'themeVariables': {
+ 'commitLabelColor': '#ff0000',
+ 'commitLabelBackground': '#00ff00'
+ } } }%%
+ gitGraph
+ commit
+ branch develop
+ commit tag:"v1.0.0"
+ commit
+ checkout main
+ commit type: HIGHLIGHT
+ commit
+ merge develop
+ commit
+ branch featureA
+ commit
+
+```
+
+See how the commit label color and background color are changed to the values specified in the theme variables.
+
+### Customizing Commit Label Font Size
+
+You can customize commit using the `commitLabelFontSize` theme variables for changing in the font soze of the commit label .
+
+Example:
+Now let's override the default values for the `commitLabelFontSize` variable:
+
+```mermaid-example
+ %%{init: { 'logLevel': 'debug', 'theme': 'default' , 'themeVariables': {
+ 'commitLabelColor': '#ff0000',
+ 'commitLabelBackground': '#00ff00',
+ 'commitLabelFontSize': '16px'
+ } } }%%
+ gitGraph
+ commit
+ branch develop
+ commit tag:"v1.0.0"
+ commit
+ checkout main
+ commit type: HIGHLIGHT
+ commit
+ merge develop
+ commit
+ branch featureA
+ commit
+
+```
+
+See how the commit label font size changed.
+
+### Customizing Tag Label Font Size
+
+You can customize commit using the `tagLabelFontSize` theme variables for changing in the font soze of the tag label .
+
+Example:
+Now let's override the default values for the `tagLabelFontSize` variable:
+
+```mermaid-example
+ %%{init: { 'logLevel': 'debug', 'theme': 'default' , 'themeVariables': {
+ 'commitLabelColor': '#ff0000',
+ 'commitLabelBackground': '#00ff00',
+ 'tagLabelFontSize': '16px'
+ } } }%%
+ gitGraph
+ commit
+ branch develop
+ commit tag:"v1.0.0"
+ commit
+ checkout main
+ commit type: HIGHLIGHT
+ commit
+ merge develop
+ commit
+ branch featureA
+ commit
+
+```
+
+See how the tag label font size changed.
+
+### Customizing Tag colors
+
+You can customize tag using the `tagLabelColor`,`tagLabelBackground` and `tagLabelBorder` theme variables for changes in the tag label color,tag label background color and tag label border respectively.
+Example:
+Now let's override the default values for the `tagLabelColor`, `tagLabelBackground` and to `tagLabelBorder` variables:
+
+```mermaid-example
+ %%{init: { 'logLevel': 'debug', 'theme': 'default' , 'themeVariables': {
+ 'tagLabelColor': '#ff0000',
+ 'tagLabelBackground': '#00ff00',
+ 'tagLabelBorder': '#0000ff'
+ } } }%%
+ gitGraph
+ commit
+ branch develop
+ commit tag:"v1.0.0"
+ commit
+ checkout main
+ commit type: HIGHLIGHT
+ commit
+ merge develop
+ commit
+ branch featureA
+ commit
+
+```
+
+See how the tag colors are changed to the values specified in the theme variables.
+
+### Customizing Highlight commit colors
+
+You can customize the highlight commit colors in relation to the branch it is on using the `gitInv0` to `gitInv7` theme variables. Mermaid allows you to set the colors for up-to 8 branches specific highlight commit, where `gitInv0` variable will drive the value of the first branch's highlight commits, `gitInv1` will drive the value of the second branch's highlight commit label and so on.
+
+Example:
+
+Now let's override the default values for the `git0` to `git3` variables:
+
+```mermaid-example
+ %%{init: { 'logLevel': 'debug', 'theme': 'default' , 'themeVariables': {
+ 'gitInv0': '#ff0000'
+ } } }%%
+ gitGraph
+ commit
+ branch develop
+ commit tag:"v1.0.0"
+ commit
+ checkout main
+ commit type: HIGHLIGHT
+ commit
+ merge develop
+ commit
+ branch featureA
+ commit
+
+```
+
+See how the highlighted commit color on the first branch is changed to the value specified in the theme variable `gitInv0`.
diff --git a/vdocs/syntax/img/Gantt-excluded-days-within.png b/vdocs/syntax/img/Gantt-excluded-days-within.png
new file mode 100644
index 0000000000..2283bf99d8
Binary files /dev/null and b/vdocs/syntax/img/Gantt-excluded-days-within.png differ
diff --git a/vdocs/syntax/img/Gantt-long-weekend-look.png b/vdocs/syntax/img/Gantt-long-weekend-look.png
new file mode 100644
index 0000000000..1b2fc8e17e
Binary files /dev/null and b/vdocs/syntax/img/Gantt-long-weekend-look.png differ
diff --git a/vdocs/syntax/pie.md b/vdocs/syntax/pie.md
new file mode 100644
index 0000000000..75d377e4be
--- /dev/null
+++ b/vdocs/syntax/pie.md
@@ -0,0 +1,51 @@
+# Pie chart diagrams
+
+> A pie chart (or a circle chart) is a circular statistical graphic, which is divided into slices to illustrate numerical proportion. In a pie chart, the arc length of each slice (and consequently its central angle and area), is proportional to the quantity it represents. While it is named for its resemblance to a pie which has been sliced, there are variations on the way it can be presented. The earliest known pie chart is generally credited to William Playfair's Statistical Breviary of 1801
+> -Wikipedia
+
+Mermaid can render Pie Chart diagrams.
+
+```mmd
+pie title Pets adopted by volunteers
+ "Dogs" : 386
+ "Cats" : 85
+ "Rats" : 15
+```
+
+```mermaid
+pie title Pets adopted by volunteers
+ "Dogs" : 386
+ "Cats" : 85
+ "Rats" : 15
+```
+
+## Syntax
+
+Drawing a pie chart is really simple in mermaid.
+
+- Start with `pie` keyword to begin the diagram
+ - `showData` to render the actual data values after the legend text. This is **_OPTIONAL_**
+- Followed by `title` keyword and its value in string to give a title to the pie-chart. This is **_OPTIONAL_**
+- Followed by dataSet
+ - `label` for a section in the pie diagram within `" "` quotes.
+ - Followed by `:` colon as separator
+ - Followed by `positive numeric value` (supported upto two decimal places)
+
+[pie] [showData] (OPTIONAL)
+[title] [titlevalue] (OPTIONAL)
+"[datakey1]" : [dataValue1]
+"[datakey2]" : [dataValue2]
+"[datakey3]" : [dataValue3]
+.
+.
+
+## Example
+
+```mermaid-example
+pie showData
+ title Key elements in Product X
+ "Calcium" : 42.96
+ "Potassium" : 50.05
+ "Magnesium" : 10.01
+ "Iron" : 5
+```
diff --git a/vdocs/syntax/requirementDiagram.md b/vdocs/syntax/requirementDiagram.md
new file mode 100644
index 0000000000..7c221312b7
--- /dev/null
+++ b/vdocs/syntax/requirementDiagram.md
@@ -0,0 +1,158 @@
+# Requirement Diagram
+
+> A Requirement diagram provides a visualization for requirements and their connections, to each other and other documented elements. The modeling specs follow those defined by SysML v1.6.
+
+Rendering requirements is straightforward.
+
+```mermaid-example
+ requirementDiagram
+
+ requirement test_req {
+ id: 1
+ text: the test text.
+ risk: high
+ verifymethod: test
+ }
+
+ element test_entity {
+ type: simulation
+ }
+
+ test_entity - satisfies -> test_req
+```
+
+## Syntax
+
+There are three types of components to a requirement diagram: requirement, element, and relationship.
+
+The grammar for defining each is defined below. Words denoted in angle brackets, such as `<word>`, are enumerated keywords that have options elaborated in a table. `user_defined_...` is use in any place where user input is expected.
+
+An important note on user text: all input can be surrounded in quotes or not. For example, both `Id: "here is an example"` and `Id: here is an example` are both valid. However, users must be careful with unquoted input. The parser will fail if another keyword is detected.
+
+### Requirement
+
+A requirement definition contains a requirement type, name, id, text, risk, and verification method. The syntax follows:
+
+```
+<type> user_defined_name {
+ id: user_defined_id
+ text: user_defined text
+ risk: <risk>
+ verifymethod: <method>
+}
+```
+
+Type, risk, and method are enumerations defined in SysML.
+
+| Keyword | Options |
+| ------------------ | ----------------------------------------------------------------------------------------------------------------------- |
+| Type | requirement, functionalRequirement, interfaceRequirement, performanceRequirement, physicalRequirement, designConstraint |
+| Risk | Low, Medium, High |
+| VerificationMethod | Analysis, Inspection, Test, Demonstration |
+
+### Element
+
+An element definition contains an element name, type, and document reference. These three are all user defined. The element feature is intended to be lightweight but allow requirements to be connected to portions of other documents.
+
+```
+element user_defined_name {
+ type: user_defined_type
+ docref: user_defined_ref
+}
+```
+
+### Relationship
+
+Relationships are comprised of a source node, destination node, and relationship type.
+
+Each follows the definition format of
+
+```
+{name of source} - <type> -> {name of destination}
+```
+
+or
+
+```
+{name of destination} <- <type> - {name of source}
+```
+
+"name of source" and "name of destination" should be names of requirement or element nodes defined elsewhere.
+
+A relationship type can be one of contains, copies, derives, satisfies, verifies, refines, or traces.
+
+Each relationship is labeled in the diagram.
+
+## Larger Example
+
+This example uses all features of the diagram.
+
+```mermaid-example
+ requirementDiagram
+
+ requirement test_req {
+ id: 1
+ text: the test text.
+ risk: high
+ verifymethod: test
+ }
+
+ functionalRequirement test_req2 {
+ id: 1.1
+ text: the second test text.
+ risk: low
+ verifymethod: inspection
+ }
+
+ performanceRequirement test_req3 {
+ id: 1.2
+ text: the third test text.
+ risk: medium
+ verifymethod: demonstration
+ }
+
+ interfaceRequirement test_req4 {
+ id: 1.2.1
+ text: the fourth test text.
+ risk: medium
+ verifymethod: analysis
+ }
+
+ physicalRequirement test_req5 {
+ id: 1.2.2
+ text: the fifth test text.
+ risk: medium
+ verifymethod: analysis
+ }
+
+ designConstraint test_req6 {
+ id: 1.2.3
+ text: the sixth test text.
+ risk: medium
+ verifymethod: analysis
+ }
+
+ element test_entity {
+ type: simulation
+ }
+
+ element test_entity2 {
+ type: word doc
+ docRef: reqs/test_entity
+ }
+
+ element test_entity3 {
+ type: "test suite"
+ docRef: github.com/all_the_tests
+ }
+
+
+ test_entity - satisfies -> test_req2
+ test_req - traces -> test_req2
+ test_req - contains -> test_req3
+ test_req3 - contains -> test_req4
+ test_req4 - derives -> test_req5
+ test_req5 - refines -> test_req6
+ test_entity3 - verifies -> test_req5
+ test_req <- copies - test_entity2
+```
diff --git a/vdocs/syntax/sequenceDiagram.md b/vdocs/syntax/sequenceDiagram.md
new file mode 100644
index 0000000000..079eaa4d58
--- /dev/null
+++ b/vdocs/syntax/sequenceDiagram.md
@@ -0,0 +1,569 @@
+# Sequence diagrams
+
+> A Sequence diagram is an interaction diagram that shows how processes operate with one another and in what order.
+
+Mermaid can render sequence diagrams.
+
+```mermaid-example
+sequenceDiagram
+ Alice->>John: Hello John, how are you?
+ John-->>Alice: Great!
+ Alice-)John: See you later!
+```
+
+::: warning
+A note on nodes, the word "end" could potentially break the diagram, due to the way that the mermaid language is scripted.
+
+If unavoidable, one must use parentheses(), quotation marks "", or brackets {},[], to enclose the word "end". i.e : (end), [end], {end}.
+:::
+
+## Syntax
+
+### Participants
+
+The participants can be defined implicitly as in the first example on this page. The participants or actors are
+rendered in order of appearance in the diagram source text. Sometimes you might want to show the participants in a
+different order than how they appear in the first message. It is possible to specify the actor's order of
+appearance by doing the following:
+
+```mermaid-example
+sequenceDiagram
+ participant Alice
+ participant Bob
+ Alice->>Bob: Hi Bob
+ Bob->>Alice: Hi Alice
+```
+
+### Actors
+
+If you specifically want to use the actor symbol instead of a rectangle with text you can do so by using actor statements as per below.
+
+```mermaid-example
+sequenceDiagram
+ actor Alice
+ actor Bob
+ Alice->>Bob: Hi Bob
+ Bob->>Alice: Hi Alice
+```
+
+### Aliases
+
+The actor can have a convenient identifier and a descriptive label.
+
+```mermaid-example
+sequenceDiagram
+ participant A as Alice
+ participant J as John
+ A->>J: Hello John, how are you?
+ J->>A: Great!
+```
+
+## Messages
+
+Messages can be of two displayed either solid or with a dotted line.
+
+```
+[Actor][Arrow][Actor]:Message text
+```
+
+There are six types of arrows currently supported:
+
+| Type | Description |
+| ---- | ------------------------------------------------ |
+| -> | Solid line without arrow |
+| --> | Dotted line without arrow |
+| ->> | Solid line with arrowhead |
+| -->> | Dotted line with arrowhead |
+| -x | Solid line with a cross at the end |
+| --x | Dotted line with a cross at the end. |
+| -) | Solid line with an open arrow at the end (async) |
+| --) | Dotted line with a open arrow at the end (async) |
+
+## Activations
+
+It is possible to activate and deactivate an actor. (de)activation can be dedicated declarations:
+
+```mermaid-example
+sequenceDiagram
+ Alice->>John: Hello John, how are you?
+ activate John
+ John-->>Alice: Great!
+ deactivate John
+```
+
+There is also a shortcut notation by appending `+`/`-` suffix to the message arrow:
+
+```mermaid-example
+sequenceDiagram
+ Alice->>+John: Hello John, how are you?
+ John-->>-Alice: Great!
+```
+
+Activations can be stacked for same actor:
+
+```mermaid-example
+sequenceDiagram
+ Alice->>+John: Hello John, how are you?
+ Alice->>+John: John, can you hear me?
+ John-->>-Alice: Hi Alice, I can hear you!
+ John-->>-Alice: I feel great!
+```
+
+## Notes
+
+It is possible to add notes to a sequence diagram. This is done by the notation
+Note [ right of | left of | over ] [Actor]: Text in note content
+
+See the example below:
+
+```mermaid-example
+sequenceDiagram
+ participant John
+ Note right of John: Text in note
+```
+
+It is also possible to create notes spanning two participants:
+
+```mermaid-example
+sequenceDiagram
+ Alice->John: Hello John, how are you?
+ Note over Alice,John: A typical interaction
+```
+
+## Loops
+
+It is possible to express loops in a sequence diagram. This is done by the notation
+
+```
+loop Loop text
+... statements ...
+end
+```
+
+See the example below:
+
+```mermaid-example
+sequenceDiagram
+ Alice->John: Hello John, how are you?
+ loop Every minute
+ John-->Alice: Great!
+ end
+```
+
+## Alt
+
+It is possible to express alternative paths in a sequence diagram. This is done by the notation
+
+```
+alt Describing text
+... statements ...
+else
+... statements ...
+end
+```
+
+or if there is sequence that is optional (if without else).
+
+```
+opt Describing text
+... statements ...
+end
+```
+
+See the example below:
+
+```mermaid-example
+sequenceDiagram
+ Alice->>Bob: Hello Bob, how are you?
+ alt is sick
+ Bob->>Alice: Not so good :(
+ else is well
+ Bob->>Alice: Feeling fresh like a daisy
+ end
+ opt Extra response
+ Bob->>Alice: Thanks for asking
+ end
+```
+
+## Parallel
+
+It is possible to show actions that are happening in parallel.
+
+This is done by the notation
+
+```
+par [Action 1]
+... statements ...
+and [Action 2]
+... statements ...
+and [Action N]
+... statements ...
+end
+```
+
+See the example below:
+
+```mermaid-example
+sequenceDiagram
+ par Alice to Bob
+ Alice->>Bob: Hello guys!
+ and Alice to John
+ Alice->>John: Hello guys!
+ end
+ Bob-->>Alice: Hi Alice!
+ John-->>Alice: Hi Alice!
+```
+
+It is also possible to nest parallel blocks.
+
+```mermaid-example
+sequenceDiagram
+ par Alice to Bob
+ Alice->>Bob: Go help John
+ and Alice to John
+ Alice->>John: I want this done today
+ par John to Charlie
+ John->>Charlie: Can we do this today?
+ and John to Diana
+ John->>Diana: Can you help us today?
+ end
+ end
+```
+
+## Critical Region
+
+It is possible to show actions that must happen automatically with conditional handling of circumstances.
+
+This is done by the notation
+
+```
+critical [Action that must be performed]
+... statements ...
+option [Circumstance A]
+... statements ...
+option [Circumstance B]
+... statements ...
+end
+```
+
+See the example below:
+
+```mermaid-example
+sequenceDiagram
+ critical Establish a connection to the DB
+ Service-->DB: connect
+ option Network timeout
+ Service-->Service: Log error
+ option Credentials rejected
+ Service-->Service: Log different error
+ end
+```
+
+It is also possible to have no options at all
+
+```mermaid-example
+sequenceDiagram
+ critical Establish a connection to the DB
+ Service-->DB: connect
+ end
+```
+
+This critical block can also be nested, equivalently to the `par` statement as seen above.
+
+## Break
+
+It is possible to indicate a stop of the sequence within the flow (usually used to model exceptions).
+
+This is done by the notation
+
+```
+break [something happened]
+... statements ...
+end
+```
+
+See the example below:
+
+```mermaid-example
+sequenceDiagram
+ Consumer-->API: Book something
+ API-->BookingService: Start booking process
+ break when the booking process fails
+ API-->Consumer: show failure
+ end
+ API-->BillingService: Start billing process
+```
+
+## Background Highlighting
+
+It is possible to highlight flows by providing colored background rects. This is done by the notation
+
+The colors are defined using rgb and rgba syntax.
+
+```
+rect rgb(0, 255, 0)
+... content ...
+end
+```
+
+```
+rect rgba(0, 0, 255, .1)
+... content ...
+end
+```
+
+See the examples below:
+
+```mermaid-example
+sequenceDiagram
+ participant Alice
+ participant John
+
+ rect rgb(191, 223, 255)
+ note right of Alice: Alice calls John.
+ Alice->>+John: Hello John, how are you?
+ rect rgb(200, 150, 255)
+ Alice->>+John: John, can you hear me?
+ John-->>-Alice: Hi Alice, I can hear you!
+ end
+ John-->>-Alice: I feel great!
+ end
+ Alice ->>+ John: Did you want to go to the game tonight?
+ John -->>- Alice: Yeah! See you there.
+
+```
+
+## Comments
+
+Comments can be entered within a sequence diagram, which will be ignored by the parser. Comments need to be on their own line, and must be prefaced with `%%` (double percent signs). Any text after the start of the comment to the next newline will be treated as a comment, including any diagram syntax
+
+```mmd
+sequenceDiagram
+ Alice->>John: Hello John, how are you?
+ %% this is a comment
+ John-->>Alice: Great!
+```
+
+## Entity codes to escape characters
+
+It is possible to escape characters using the syntax exemplified here.
+
+```mermaid-example
+sequenceDiagram
+ A->>B: I #9829; you!
+ B->>A: I #9829; you #infin; times more!
+```
+
+Numbers given are base 10, so `#` can be encoded as `#35;`. It is also supported to use HTML character names.
+
+Because semicolons can be used instead of line breaks to define the markup, you need to use `#59;` to include a semicolon in message text.
+
+## sequenceNumbers
+
+It is possible to get a sequence number attached to each arrow in a sequence diagram. This can be configured when adding mermaid to the website as shown below:
+
+```html
+<script>
+ mermaid.initialize({ sequence: { showSequenceNumbers: true } });
+</script>
+```
+
+It can also be be turned on via the diagram code as in the diagram:
+
+```mermaid-example
+sequenceDiagram
+ autonumber
+ Alice->>John: Hello John, how are you?
+ loop Healthcheck
+ John->>John: Fight against hypochondria
+ end
+ Note right of John: Rational thoughts!
+ John-->>Alice: Great!
+ John->>Bob: How about you?
+ Bob-->>John: Jolly good!
+```
+
+## Actor Menus
+
+Actors can have popup-menus containing individualized links to external pages. For example, if an actor represented a web service, useful links might include a link to the service health dashboard, repo containing the code for the service, or a wiki page describing the service.
+
+This can be configured by adding one or more link lines with the format:
+
+```
+link <actor>: <link-label> @ <link-url>
+```
+
+```mmd
+sequenceDiagram
+ participant Alice
+ participant John
+ link Alice: Dashboard @ https://dashboard.contoso.com/alice
+ link Alice: Wiki @ https://wiki.contoso.com/alice
+ link John: Dashboard @ https://dashboard.contoso.com/john
+ link John: Wiki @ https://wiki.contoso.com/john
+ Alice->>John: Hello John, how are you?
+ John-->>Alice: Great!
+ Alice-)John: See you later!
+```
+
+#### Advanced Menu Syntax
+
+There is an advanced syntax that relies on JSON formatting. If you are comfortable with JSON format, then this exists as well.
+
+This can be configured by adding the links lines with the format:
+
+```
+links <actor>: <json-formatted link-name link-url pairs>
+```
+
+An example is below:
+
+```mermaid-example
+sequenceDiagram
+ participant Alice
+ participant John
+ links Alice: {"Dashboard": "https://dashboard.contoso.com/alice", "Wiki": "https://wiki.contoso.com/alice"}
+ links John: {"Dashboard": "https://dashboard.contoso.com/john", "Wiki": "https://wiki.contoso.com/john"}
+ Alice->>John: Hello John, how are you?
+ John-->>Alice: Great!
+ Alice-)John: See you later!
+```
+
+## Styling
+
+Styling of a sequence diagram is done by defining a number of css classes. During rendering these classes are extracted from the file located at src/themes/sequence.scss
+
+### Classes used
+
+| Class | Description |
+| ------------ | ----------------------------------------------------------- |
+| actor | Style for the actor box at the top of the diagram. |
+| text.actor | Styles for text in the actor box at the top of the diagram. |
+| actor-line | The vertical line for an actor. |
+| messageLine0 | Styles for the solid message line. |
+| messageLine1 | Styles for the dotted message line. |
+| messageText | Defines styles for the text on the message arrows. |
+| labelBox | Defines styles label to left in a loop. |
+| labelText | Styles for the text in label for loops. |
+| loopText | Styles for the text in the loop box. |
+| loopLine | Defines styles for the lines in the loop box. |
+| note | Styles for the note box. |
+| noteText | Styles for the text on in the note boxes. |
+
+### Sample stylesheet
+
+```css
+body {
+ background: white;
+}
+
+.actor {
+ stroke: #ccccff;
+ fill: #ececff;
+}
+text.actor {
+ fill: black;
+ stroke: none;
+ font-family: Helvetica;
+}
+
+.actor-line {
+ stroke: grey;
+}
+
+.messageLine0 {
+ stroke-width: 1.5;
+ stroke-dasharray: '2 2';
+ marker-end: 'url(#arrowhead)';
+ stroke: black;
+}
+
+.messageLine1 {
+ stroke-width: 1.5;
+ stroke-dasharray: '2 2';
+ stroke: black;
+}
+
+#arrowhead {
+ fill: black;
+}
+
+.messageText {
+ fill: black;
+ stroke: none;
+ font-family: 'trebuchet ms', verdana, arial;
+ font-size: 14px;
+}
+
+.labelBox {
+ stroke: #ccccff;
+ fill: #ececff;
+}
+
+.labelText {
+ fill: black;
+ stroke: none;
+ font-family: 'trebuchet ms', verdana, arial;
+}
+
+.loopText {
+ fill: black;
+ stroke: none;
+ font-family: 'trebuchet ms', verdana, arial;
+}
+
+.loopLine {
+ stroke-width: 2;
+ stroke-dasharray: '2 2';
+ marker-end: 'url(#arrowhead)';
+ stroke: #ccccff;
+}
+
+.note {
+ stroke: #decc93;
+ fill: #fff5ad;
+}
+
+.noteText {
+ fill: black;
+ stroke: none;
+ font-family: 'trebuchet ms', verdana, arial;
+ font-size: 14px;
+}
+```
+
+## Configuration
+
+Is it possible to adjust the margins for rendering the sequence diagram.
+
+This is done by defining `mermaid.sequenceConfig` or by the CLI to use a json file with the configuration.
+How to use the CLI is described in the [mermaidCLI](../config/mermaidCLI) page.
+`mermaid.sequenceConfig` can be set to a JSON string with config parameters or the corresponding object.
+
+```javascript
+mermaid.sequenceConfig = {
+ diagramMarginX: 50,
+ diagramMarginY: 10,
+ boxTextMargin: 5,
+ noteMargin: 10,
+ messageMargin: 35,
+ mirrorActors: true,
+};
+```
+
+### Possible configuration parameters:
+
+| Parameter | Description | Default value |
+| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------ |
+| mirrorActors | Turns on/off the rendering of actors below the diagram as well as above it | false |
+| bottomMarginAdj | Adjusts how far down the graph ended. Wide borders styles with css could generate unwanted clipping which is why this config param exists. | 1 |
+| actorFontSize | Sets the font size for the actor's description | 14 |
+| actorFontFamily | Sets the font family for the actor's description | "Open Sans", sans-serif |
+| actorFontWeight | Sets the font weight for the actor's description | "Open Sans", sans-serif |
+| noteFontSize | Sets the font size for actor-attached notes | 14 |
+| noteFontFamily | Sets the font family for actor-attached notes | "trebuchet ms", verdana, arial |
+| noteFontWeight | Sets the font weight for actor-attached notes | "trebuchet ms", verdana, arial |
+| noteAlign | Sets the text alignment for text in actor-attached notes | center |
+| messageFontSize | Sets the font size for actor<->actor messages | 16 |
+| messageFontFamily | Sets the font family for actor<->actor messages | "trebuchet ms", verdana, arial |
+| messageFontWeight | Sets the font weight for actor<->actor messages | "trebuchet ms", verdana, arial |
diff --git a/vdocs/syntax/stateDiagram.md b/vdocs/syntax/stateDiagram.md
new file mode 100644
index 0000000000..e28819e7a2
--- /dev/null
+++ b/vdocs/syntax/stateDiagram.md
@@ -0,0 +1,260 @@
+# State diagrams
+
+> "A state diagram is a type of diagram used in computer science and related fields to describe the behavior of systems. State diagrams require that the system described is composed of a finite number of states; sometimes, this is indeed the case, while at other times this is a reasonable abstraction." Wikipedia
+
+Mermaid can render state diagrams. The syntax tries to be compliant with the syntax used in plantUml as this will make it easier for users to share diagrams between mermaid and plantUml.
+
+```mermaid-example
+stateDiagram-v2
+ [*] --> Still
+ Still --> [*]
+
+ Still --> Moving
+ Moving --> Still
+ Moving --> Crash
+ Crash --> [*]
+```
+
+Older renderer:
+
+```mermaid-example
+stateDiagram
+ [*] --> Still
+ Still --> [*]
+
+ Still --> Moving
+ Moving --> Still
+ Moving --> Crash
+ Crash --> [*]
+```
+
+In state diagrams systems are described in terms of its states and how the systems state can change to another state via a transitions. The example diagram above shows three states **Still**, **Moving** and **Crash**. You start in the state of Still. From Still you can change the state to Moving. In Moving you can change the state either back to Still or to Crash. There is no transition from Still to Crash.
+
+## States
+
+A state can be declared in multiple ways. The simplest way is to define a state id as a description.
+
+```mermaid-example
+stateDiagram-v2
+ s1
+```
+
+Another way is by using the state keyword with a description as per below:
+
+```mermaid-example
+stateDiagram-v2
+ state "This is a state description" as s2
+```
+
+Another way to define a state with a description is to define the state id followed by a colon and the description:
+
+```mermaid-example
+stateDiagram-v2
+ s2 : This is a state description
+```
+
+## Transitions
+
+Transitions are path/edges when one state passes into another. This is represented using text arrow, "\-\-\>".
+
+When you define a transition between two states and the states are not already defined the undefined states are defined with the id from the transition. You can later add descriptions to states defined this way.
+
+```mermaid-example
+stateDiagram-v2
+ s1 --> s2
+```
+
+It is possible to add text to a transition. To describe what it represents.
+
+```mermaid-example
+stateDiagram-v2
+ s1 --> s2: A transition
+```
+
+## Start and End
+
+There are two special states indicating the start and stop of the diagram. These are written with the [\*] syntax and the direction of the transition to it defines it either as a start or a stop state.
+
+```mermaid-example
+stateDiagram-v2
+ [*] --> s1
+ s1 --> [*]
+```
+
+## Composite states
+
+In a real world use of state diagrams you often end up with diagrams that are multi-dimensional as one state can
+have several internal states. These are called composite states in this terminology.
+
+In order to define a composite state you need to use the state keyword followed by an id and the body of the composite state between \{\}. See the example below:
+
+```mermaid-example
+stateDiagram-v2
+ [*] --> First
+ state First {
+ [*] --> second
+ second --> [*]
+ }
+```
+
+You can do this in several layers:
+
+```mermaid-example
+stateDiagram-v2
+ [*] --> First
+
+ state First {
+ [*] --> Second
+
+ state Second {
+ [*] --> second
+ second --> Third
+
+ state Third {
+ [*] --> third
+ third --> [*]
+ }
+ }
+ }
+```
+
+You can also define transitions also between composite states:
+
+```mermaid-example
+stateDiagram-v2
+ [*] --> First
+ First --> Second
+ First --> Third
+
+ state First {
+ [*] --> fir
+ fir --> [*]
+ }
+ state Second {
+ [*] --> sec
+ sec --> [*]
+ }
+ state Third {
+ [*] --> thi
+ thi --> [*]
+ }
+```
+
+_You can not define transitions between internal states belonging to different composite states_
+
+## Choice
+
+Sometimes you need to model a choice between two or more paths, you can do so using <<choice>>.
+
+```mermaid-example
+stateDiagram-v2
+ state if_state <<choice>>
+ [*] --> IsPositive
+ IsPositive --> if_state
+ if_state --> False: if n < 0
+ if_state --> True : if n >= 0
+```
+
+## Forks
+
+It is possible to specify a fork in the diagram using <<fork>> <<join>>.
+
+```mermaid-example
+ stateDiagram-v2
+ state fork_state <<fork>>
+ [*] --> fork_state
+ fork_state --> State2
+ fork_state --> State3
+
+ state join_state <<join>>
+ State2 --> join_state
+ State3 --> join_state
+ join_state --> State4
+ State4 --> [*]
+```
+
+## Notes
+
+Sometimes nothing says it better then a Post-it note. That is also the case in state diagrams.
+
+Here you can choose to put the note to the _right of_ or to the _left of_ a node.
+
+```mermaid-example
+ stateDiagram-v2
+ State1: The state with a note
+ note right of State1
+ Important information! You can write
+ notes.
+ end note
+ State1 --> State2
+ note left of State2 : This is the note to the left.
+```
+
+## Concurrency
+
+As in plantUml you can specify concurrency using the -- symbol.
+
+```mermaid-example
+stateDiagram-v2
+ [*] --> Active
+
+ state Active {
+ [*] --> NumLockOff
+ NumLockOff --> NumLockOn : EvNumLockPressed
+ NumLockOn --> NumLockOff : EvNumLockPressed
+ --
+ [*] --> CapsLockOff
+ CapsLockOff --> CapsLockOn : EvCapsLockPressed
+ CapsLockOn --> CapsLockOff : EvCapsLockPressed
+ --
+ [*] --> ScrollLockOff
+ ScrollLockOff --> ScrollLockOn : EvScrollLockPressed
+ ScrollLockOn --> ScrollLockOff : EvScrollLockPressed
+ }
+```
+
+## Setting the direction of the diagram
+
+With state diagrams you can use the direction statement to set the direction which the diagram will render like in this example.
+
+```mermaid-example
+stateDiagram
+ direction LR
+ [*] --> A
+ A --> B
+ B --> C
+ state B {
+ direction LR
+ a --> b
+ }
+ B --> D
+```
+
+## Comments
+
+Comments can be entered within a state diagram chart, which will be ignored by the parser. Comments need to be on their own line, and must be prefaced with `%%` (double percent signs). Any text after the start of the comment to the next newline will be treated as a comment, including any diagram syntax
+
+```mmd
+stateDiagram-v2
+ [*] --> Still
+ Still --> [*]
+%% this is a comment
+ Still --> Moving
+ Moving --> Still %% another comment
+ Moving --> Crash
+ Crash --> [*]
+```
+
+## Styling
+
+Styling of the a state diagram is done by defining a number of css classes. During rendering these classes are extracted from the file located at src/themes/state.scss
+
+## Spaces in state names
+
+Spaces can be added to a state by defining it at the top and referencing the acronym later.
+
+```mermaid-example
+stateDiagram-v2
+ Yswsii: Your state with spaces in it
+ [*] --> Yswsii
+```
diff --git a/vdocs/syntax/userJourney.md b/vdocs/syntax/userJourney.md
new file mode 100644
index 0000000000..3476088aba
--- /dev/null
+++ b/vdocs/syntax/userJourney.md
@@ -0,0 +1,22 @@
+# User Journey Diagram
+
+> User journeys describe at a high level of detail exactly what steps different users take to complete a specific task within a system, application or website. This technique shows the current (as-is) user workflow, and reveals areas of improvement for the to-be workflow. (Wikipedia)
+
+Mermaid can render user journey diagrams:
+
+```mermaid-example
+journey
+ title My working day
+ section Go to work
+ Make tea: 5: Me
+ Go upstairs: 3: Me
+ Do work: 1: Me, Cat
+ section Go home
+ Go downstairs: 5: Me
+ Sit down: 5: Me
+```
+
+Each user journey is split into sections, these describe the part of the task
+the user is trying to complete.
+
+Tasks syntax is `Task name: <score>: <comma separated list of actors>`
diff --git a/vdocs/vite.config.ts b/vdocs/vite.config.ts
new file mode 100644
index 0000000000..bc88526914
--- /dev/null
+++ b/vdocs/vite.config.ts
@@ -0,0 +1,35 @@
+import { defineConfig } from 'vite';
+import path from 'path';
+import { SearchPlugin } from 'vitepress-plugin-search';
+
+const virtualModuleId = 'virtual:mermaid-config';
+const resolvedVirtualModuleId = '\0' + virtualModuleId;
+
+export default defineConfig({
+ plugins: [
+ SearchPlugin(),
+ {
+ // TODO: will be fixed in the next vitepress release.
+ name: 'fix-virtual',
+
+ async resolveId(id) {
+ if (id === virtualModuleId) {
+ return resolvedVirtualModuleId;
+ }
+ },
+ async load(this, id) {
+ if (id === resolvedVirtualModuleId) {
+ return `export default ${JSON.stringify({
+ securityLevel: 'loose',
+ startOnLoad: false,
+ })};`;
+ }
+ },
+ },
+ ],
+ resolve: {
+ alias: {
+ mermaid: path.join(__dirname, '../dist/mermaid.esm.min.mjs'), // Use this one to build
+ },
+ },
+});