ezmdpage VS argdown

One of the things I recommend to the startups I advise is to include documentation within the repository. I always try to have a /doc directory which includes Markdown (I like using [1] self rendering markdown pages) and MermaidJS (For which I also created a dumb self rendering script [2]).

That way Merge Requests can be blocked for lack of documentation, or lack of documentation update.

MermaidJS have been a godsend for documentation.

[1] https://github.com/jcbhmr/ezmdpage

```

You'd then be able to interleave prose and graph structures in a single file rather than dealing with two separate parsing structures. Even better, the end result would still be Markdown compliant.

[0]: https://argdown.org/

Having a diagram helped me multiple times. I'm aware of different types and I'm quite interested in visualisation, but... it never really mattered. A diagram showing what you want is good, others are not, regardless of whether it has an official name.

One specific non-SW type I consciously use is an argument map, if you're after decision making. See argdown https://argdown.org/

Does someone know about https://argdown.org/ syntax and has some ideas on how it could be related (implemented) to Obsidian Canvas?