viz.js VS markup

Generally, you're best off with Viz.js, an emscripten transcompile of GraphViz

Other resources - Graphviz and Viz.js helped me a lot in in creating graphing app I built before I knew of these other libraries. "Graph visualization" was what I was searching for.

To modify it, go to http://viz-js.com/, select Engine: circo and paste the following code: ``` digraph G { // Colors. See https://graphviz.org/doc/info/colors.html. Pikemen, MenAtArms [style=filled, fillcolor=lightskyblue1] Archers, Crossbowmen [style=filled, fillcolor=khaki] Horsemen, Knights [style=filled, fillcolor=lawngreen] Rams, Springalds, Mangonels, Trebuchets [style=filled, fillcolor=plum]

This might fit the bill in js land http://viz-js.com/

> but the bundle is enormous - over a megabyte of data

If only DOT layout engine and JSON output format is enabled at compile time it is about 600KiB, or less than 200KiB Gzipped. https://github.com/rapidlua/viz.js

> A nice thing about having an SVG render is that it's very easy to attach events, and inline SVGs can be styled with CSS.

Indeed it’s super handy! I’m using this approach in https://LuaJIT.me to produce an interactive visualisation of a graph of traces in a JIT compiler.

Btw github supports more than just markdown: https://github.com/github/markup#markups

I'm not sure 4. works for colors/styling, style attributes are stripped: https://github.com/github/markup/issues/119

I found this issue, which does not show much traction: https://github.com/github/markup/issues/994

For sharing settings and lore with players, GitHub wiki. Understands Org and several other formats thanks to GitHub Markup, so I can copy in (and trim down) my original notes without much fuss.

Re: https://github.com/github/markup/issues/533

I’m the main author of KeenWrite (see screenshots), a type of desktop Markdown editor that supports diagrams. It’s encouraging to see that Mermaid diagrams are being supported in GitHub. There are a few drawbacks on the syntax and implications of using MermaidJS.

First, only browser-based SVG renderers can correctly parse Mermaid diagrams. I’ve tested Apache Batik, svgSalamander, resvg, rsvg-convert, svglib, CairoSVG, ConTeXt, and QtSVG. See issue 2485. This implies that typesetting Mermaid diagrams is not currently possible. In effect, by including Mermaid diagrams, many documents will be restricted to web-based output, excluding the possibility of producing PDF documents based on GitHub markdown documents (for the foreseeable future).

Second, there are numerous text-to-diagram facilities available beyond Mermaid. The server at https://kroki.io/ supports Mermaid, PlantUML, Graphviz, byte fields, and many more. While including MermaidJS is a great step forward, supporting Kroki diagrams would allow a much greater variety. (Most diagrams produced in MermaidJS can also be crafted in Graphviz, albeit with less terse syntax.)

Third, see the CommonMark discussion thread referring to a syntax for diagrams. It’s unfortunate that a standard “namespace” concept was not proposed.

Fourth, KeenWrite integrates Kroki. To do so, it uses a variation on the syntax:

    ``` diagram-mermaid

I thought it only rendered files in the repo (match by extension). Does GH also allow asciidoc(tor) syntax in comments and issues?

* Note: Sadly, include is not supported on GH. https://github.com/github/markup/issues/1095