Why I built a mind-mapping tool where Markdown is the actual file format

Most mind-mapping tools treat Markdown as an export option — something you get out at the end, one-way. I wanted the opposite: I wanted my mind map to just be a Markdown outline, so I could drop into a text editor for fast bulk edits and still get a proper diagram back.

That one constraint ended up shaping most of what makes MindSpark different.

Suggested structure for the rest:

The sync problem — what breaks (folding, word wrap, syntax highlighting) once the text view has to stay perfectly in sync with a live canvas, and how each got solved.
The formula engine — an unusual feature for this category, and why a mind map benefits from SUM(children)-style rollups.
The ownership philosophy — why self-hosting and the GitHub-repo-as-storage static mode mattered enough to build both.
What’s next — roadmap, and an invitation to file issues or contribute.

Here is the link:
https://github.com/prasadpatil25/mindspark