GitHub/mermaid
1
0
Fork 0
mirror of https://github.com/mermaid-js/mermaid.git synced 2025-01-14 06:43:25 +08:00
Code Issues Projects Releases Wiki Activity

Update n00b-overview.md

Browse Source
This commit is contained in:
erelling 2019-11-08 01:06:20 +01:00 committed by GitHub
parent 6d90f87b2f
commit 7a2a8cffbb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/n00b-overview.md
View File

@ -17,7 +17,9 @@ And end up getting this in the documentation:
Most of the stuff I need to visualize can be scripted like this, with a varitety of different symbols and chart types. Since the diagram source is text based, it can be part of production scripts (and other pieces of code). So less time needs be spent on documenting as a separate task.
Comparing with Visio and similar applications, mermaid is a really fast and simple way to create good visualizations when writing documentation. This is especially apparent when a complex visualisation needs to be edited, which could take hours in a desktop application. With mermaid I can spend a fraction of that time automating the diagram generation and end up saving even more time. I love it!
Comparing with Visio and similar applications, mermaid is a really fast and simple way to create good visualizations. This is especially apparent when a complex visualisation needs to be edited, which could take me hours in a desktop application.
With mermaid I can spend a fraction of that time automating the diagram generation and end up saving even more time. I love it!
However, a lot of the mermaid documentation is geared to professional developers and presumes a skill set which I do not have.