I'm thinking of taking on a new open source project. This would be a native desktop application distributed under something like GPL or MPL2.<p>As a software engineer I do a lot of architecture and process diagrams but I find existing web editors for things like D2 and Mermaid somewhat cumbersome. I was thinking of building a dedicated, native editor.<p>Some features I'm thinking of:<p>- autocomplete and macros for faster composition<p>- wizards for common diagram types<p>- save diagrams as editable PNGs / editable SVGs<p>- generate code for git "architecture" repositories<p>- create themes for diagrams<p>- offline documentation for language syntax<p>- generate diagrams from json (nodes / edges lists)<p>- some form of LLM assistant integration, e.g. to bootstrap diagrams with a prompt<p>What features would make something like this worth using, to you?
I use Mermaid a lot, and my biggest gripe is the lack of normalized syntax. Everytime I want to create a new type of diagram, it's like learning a new language. I'm a big diagram-as-code proponent (<a href="https://ashwinsundar.com/posts/diagrams-as-code/" rel="nofollow">https://ashwinsundar.com/posts/diagrams-as-code/</a>) - however, I get the impression that no one at Mermaid is really talking to each other when making new features. There doesn't seem to be much thought for how to make the syntax cohesive or easy-to-grok
I love that Mermaid is portable, but I hate its syntax. I wish I could just define the things graphically, dragging nodes around an auto layout canvas, and then have it generate the corresponding code that I could then further edit.<p>In other words, the graphical output wouldn't just be a preview of the code, but an editable canvas like Figma or SVG editors.<p>Mermaid is so terrible to work with I usually have to use ChatGPT to make all but the simplest diagrams. It is not very good at it though and will frequently hallucinate invalid syntax, especially for less common charts like sankeys.