Having spent some time studying the Goat and Markdeep projects, and reading both code bases, it seems to me the way to greatest value for users of Goat is not in striving for completeness in implementing Markdeep's diagram functionality, but rather in compatibility with Markdown and other existing documentation solutions.
The attached changes to the top-level README try to lay out a direction that I think could lead to greater takeup of Goat by projects on Github, and elsewhere.
Having spent some time studying the Goat and Markdeep projects, and reading both code bases, it seems to me the way to greatest value for users of Goat is not in striving for completeness in implementing Markdeep's diagram functionality, but rather in compatibility with Markdown and other existing documentation solutions.
The attached changes to the top-level README try to lay out a direction that I think could lead to greater takeup of Goat by projects on Github, and elsewhere.