Hi Amit!

I came across your project recently and really liked the fact that you're using yamls for vega specs instead of json. That's much better for us humans indeed!

After some further browsing, I discovered that an atom/vscode plugin called markdown-preview-ehnacend also supports vega and vega-lite inside markdown, both as json and yaml:
https://shd101wyy.github.io/markdown-preview-enhanced/#/diagrams?id=vega-and-vega-lite

The functionality is taken from an upstream library called mume, which is a rather standard nodejs package. See vega.ts and vega-lite.ts there.

I'm not involved in those projects, just walking past thinking that the world can become an even better place if you join forces :–) Thanks for what you've already done and good luck in future!

Hey, first: this is great stuff, thanks for making it!

Now, vega-lite looks amazing, but at the moment it does not support interactive stuff yet; I know it's planned but I'm a bit impatient. So I was just wondering how hard it would be to replace vega-lite with vega in this build process you outlined on the Google groups message:

It uses the following three libraries
yaml -> json (using yaml.js)

json -> vega-lite -> svg (using vegalite.js)

markdown -> html (using marked.js)

My hunch is that it just requires tweaking this line but I've only just discovered vega and vega-lite and still have to dig down into the specs and such.

A number of my colleagues like this.
We think it might be useful to wrap this as an electron app so you can preview visdown file offline.
Then you can make the app open a special variation of markdown (e.g., *.v.md files) for your app.

The reason for .v.md is that the file will still be recognized by other editors as markdown.

(We are using *.vl.json and *.vg.json for Vega-Lite and Vega apps too.)

See https://github.com/mjbvz/vscode-markdown-mermaid for an example