mkcli VS argdown

I had a go at this a while ago, uses the markdown AST to build a program descriptor:

https://github.com/mkdoc/mkcli

I think docopt is a better choice as it has more traction but this experiment showed me a pure markdown implementation is feasible.

I had a crack at this here:

https://github.com/mkdoc/mkcli

One of these days i would like to rewrite it in Go or Rust.

I even got around to generating bash/zsh completion scripts from the generated program descriptor.

```

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?