draw.io VS mermaid

Check this: https://github.com/jgraph/drawio

Awesome! Next please add a collaborative/multiplayer mode ❤️ In every team you want to have the chance to work together on a flow diagram. Even draw.io does not support it until now, so if you get it working that would be huge news and a USP for Svelvet: https://github.com/jgraph/drawio/issues/1396

You can. I run it in docker, but you can do without it, check the repo https://github.com/jgraph/drawio

Drawio pull requests

Draw.io itself is self hostable by the looks of it https://github.com/jgraph/drawio

I draw all of my diagrams in a free application called diagrams.net (formerly draw.io). When building critical path diagrams, I put each data flow in its own layer. I then add buttons in the key that toggle the visibility of the layer, making it easy to show/hide entire flows.

More Power Users: Ad-free episodes with regular bonus segmentsAllison Sheridan (@podfeet) / TwitterPodfeet PodcastsNew Calendar Tricks Webinar - MacSparkyMacSparky's Calendar TricksControl Panel on Gray Icon Print by Susan Kare – Kare PrintsiThoughts - Mind Map on the App StoreDiagrams.netHas Apple Lost Steve Jobs's Vision of the Simple 2x2 Matrix? – More Diagrams - Podfeet PodcastsKnit Like a Programmer - Podfeet PodcastsOn the 20th Anniversary Mac – 512 PixelsApple Twentieth Anniversary Macintosh Computer Used By Jerry In Seinfeld Season 9 Episode 9 "The Apology" (1997)Why the Black MacBook Cost More – 512 PixelsUlyssesMarsEdit 4How to Add Elapsed Time in Excel - Podfeet PodcastsRogue Amoeba | Audio HijackRogue Amoeba | LoopbackHindenburgRogue Amoeba | SoundSourcemimoLiveWave XLRAutomating Audio Hijack 4 with Shortcuts and JavaScript – Six ColorsFolgeVisual Studio CodeHSXKPasswdTelegram Messenger

I’d look into how draw.io/jgraph open sources. They are open source - not open contribution. Easy way for your team to allow people to do what you want without additional governance. Appreciate the open dialogue! Link: draw.io github

Another solution which I prefer is - maintaining diagrams as code which live in the same repos as the code. There are many tools these days which help us author diagrams from code. My favorites are Mermaid and PlantUML. Now your code can live in the repo and evolve along with the codebase. You might need to do additional setup if you'd like the diagrams to be generated as part of your CI/CD. I like to maintain these in a /docs folder within the project repo.

Individual diagrams have their grammar in a .jison file.

Flowchart: https://github.com/mermaid-js/mermaid/blob/develop/packages/...

A single grammar to support all the different use cases would be challenging. But we did have some plans to introduce guidelines to make different diagram syntaxes more consistent.

This would really be a good UX improvement.

But the implementation might be a little tricky.

Please raise an issue so we can discuss further, and add it to roadmap if feasible.

https://github.com/mermaid-js/mermaid/issues/new

This is so cool. It reminds me of Markdown and Mermaid (https://github.com/mermaid-js/mermaid), which can do a similar thing within a plain text file. Keep it up; looking forward to trying it out.

KeenWrite[0], the FOSS Markdown text editor I’ve been working on, includes the ability to render plain text diagrams via Kroki[1]†. See the screenshots[2] for examples. Here’s a sample Markdown document that was typeset[3] using ConTeXt[4] (and an early version of the Solare[5] theme).

One reason I developed KeenWrite was to use variables inside of plain text diagrams. In the genealogy diagram, when any character name (that’s within the diagram) is updated, the diagram regenerates automatically. (The variables are defined in an external YAML file, allowing for integration with build pipelines.)

Version 3.x containerizes the typesetting system, which greatly simplifies the installation instructions that allow typesetting Markdown into PDF files. It also opens the door to moving Kroki into the container so that diagram descriptions aren’t pushed over the Internet to be rendered.

†Kroki, ergo KeenWrite, supports BlockDiag (BlockDiag, SeqDiag, ActDiag, NwDiag, PacketDiag, RackDiag), BPMN, Bytefield, C4 (with PlantUML), Ditaa, Erd, Excalidraw, GraphViz, Nomnoml, Pikchr, PlantUML, Structurizr, SvgBob, UMLet, Vega, Vega-Lite, and WaveDrom.

Note that Mermaid diagrams generate non-conforming SVG[6], so they don’t render outside of web browsers. There is work being done to address[7] this problem.

[0]: https://github.com/DaveJarvis/keenwrite

[1]: https://kroki.io/

[2]: https://github.com/DaveJarvis/keenwrite/blob/main/docs/scree...

[3]: https://pdfhost.io/v/4FeAGGasj_SepiSolar_Highlevel_Software_...

[4]: https://wiki.contextgarden.net/Main_Page

[5]: https://github.com/DaveJarvis/keenwrite-themes/

[6]: https://github.com/mermaid-js/mermaid/issues/2485

[7]: https://github.com/yuzutech/kroki/issues/1410

Useful resources: GitHub repository Package size: 24.9 MB License: MIT

Or, this one: https://github.com/mermaid-js/mermaid