For anyone interested in generating diagrams from text, I recommend also taking a look at Graphviz[1] and PlantUML[2]. Graphviz excels at box-and-arrow kind of diagrams as well as graphs, I frequently use it to visually map out dependencies, processes and state transitions, etc. There's an online version here[3]. PlantUML I use less, both because it's slower (you pay the JVM startup tax on every invocation) and because I have less use for the kind of diagrams it specializes in.<p>[1] <a href="https://graphviz.com" rel="nofollow">https://graphviz.com</a><p>[2] <a href="http://plantuml.com" rel="nofollow">http://plantuml.com</a><p>[3] <a href="https://dreampuf.github.io/GraphvizOnline/" rel="nofollow">https://dreampuf.github.io/GraphvizOnline/</a>
We used mermaid.js for a while. I didn't like the fact that it worked only in a browser, and installing phantom.js (which installed a whole pre-compiled binary of Chromium) was painful.<p>We also ran into some limitations on how we could control the final display.<p>So we moved all our diagrams to PlantUML and found ourselves quite happy with it.
Thanks for sharing! Just tried some UML sequence diagrams and this looks like it’ll be a lot more convenient than other UML tools.<p>Here’s the syntax guide: <a href="https://github.com/mermaidjs/mermaid-gitbook/blob/master/content/sequenceDiagram.md" rel="nofollow">https://github.com/mermaidjs/mermaid-gitbook/blob/master/con...</a><p>Edit: And here’s a plugin for VS Code that adds a live render pane to the text editor - <a href="https://marketplace.visualstudio.com/items?itemName=vstirbu.vscode-mermaid-preview" rel="nofollow">https://marketplace.visualstudio.com/items?itemName=vstirbu....</a>
typora.io renders mermaid and some others in markdown documents<p><a href="https://support.typora.io/Draw-Diagrams-With-Markdown/" rel="nofollow">https://support.typora.io/Draw-Diagrams-With-Markdown/</a>
I’ve used mermaid for documentation, through plugins for mkdocs and Sphinx. What’s great about it is that the diagrams are stored as readable source text in the documentation, which is easy to diff and modify along with the rest of the doc (search and replace when renaming a component etc).<p>That’s a huge benefit compared to storing rendered bitmaps, with a source file next to them. There’s much more friction involved in keeping those up to date, the changes don’t display usefully in PRs etc. They’re almost never up to date as a result.<p>Another thing mermaid lets you easily do is generate sequence diagrams from code such as testcases, because the format is so simple and line-driven.
The outpout can also be included in documentation as samples, and is guaranteed to be up-to-date.
We use this to diagram our systems at a high level in documentation. It can be fiddly to get it exactly how you want it but it's a lot faster and easier to version control then, say, PowerPoint.
Has anyone managed to make decent looking org charts using Mermaid or one of the other text-based diagram generators mentioned in this thread? I've been looking for a way to make it easier for the one person we have who is working in HR to update the org chart each time we make a new hire. As bureaucratic as an org chart can be, keeping our up-to-date makes it easier for new people to figure out who everyone else is, and also helps existing staff figure out where newer employees fit in.