Add support for Graphviz diagrams #2052

dscho · 2025-09-07T12:05:48Z

Changes

This adds support for Graphviz diagrams and replaces the .pngs in https://git-scm.com/about/distributed with scalable versions.

Context

Over in #2049, we discussed various options how to add elegant diagrams, and settled on Graphviz ones. I broke this out so that I don't have to derail the discussion about the cheat sheet anymore.

The solution presented here uses viz.js, a WebAssembly version of Graphviz. Since it weighs a bit much (1.4MB), this is used client-side only when developing the page locally; When the site gets deployed, the SVGs are "pre-rendered", i.e. generated and inserted in place of the <pre class="graphviz"> blocks.

To demonstrate this new feature, I replaced the diagrams in https://git-scm.com/about/distributed with Graphviz ones:

before	after

The changes of this PR can also be seen in action in my fork: https://dscho.github.io/git-scm.com/about/distributed

dscho · 2025-09-07T12:07:48Z

layouts/_default/baseof.html

+<script type="text/javascript">
+  (() => {
+    let vizInstance
+    [...document.querySelectorAll("pre[class=graphviz]")].forEach(async (x) => {
+      if (!vizInstance) vizInstance = await Viz.instance()
+      const options = {
+        graphAttributes: {
+          bgcolor: "transparent",
+        },
+        engine: x.getAttribute("engine") || "dot",
+      }
+      const svg = vizInstance.renderSVGElement(x.innerText, options)
+      svg.classList.add("graphviz")
+      x.parentNode.insertBefore(svg, x);
+      x.style.display = 'none'
+    });
+  })();
+</script>


Oh, I guess there's a point to be made about moving this logic to application.js and only keep a call to Graphviz.render() here, right? I'll do that real quick.

jvns · 2025-09-07T12:30:35Z

assets/sass/dark-mode.css

@@ -152,6 +152,10 @@
            #l10n-versions-dropdown footer a {
                color: #6969dd;
            }
+
+            svg.graphviz {
+                filter: invert(60%);


I noticed this is different from the existing dark mode filter on the about/distributed page, which is brightness(.9)contrast(.6)invert(1). I think the existing dark mode looks better.

I saw that, and changed it from 60% to 67%, maybe you also like that better?

Well, I did implement the <svg> -> <img> patch, and now things like quite different:

jvns · 2025-09-07T12:34:31Z

content/about/distributed.html

+      edge [fontname="Helvetica", penwidth=3];
+
+      // Nodes
+      blessed_repo [label="blessed\nrepository", fillcolor=teal, fontcolor=white, pos="6,4!"];


Maybe match the design of the existing diagrams a bit more closely? For example the "blessed repository" node used to be very big and now it's small. Also I think I liked the gray arrows better with the smaller arrowheads, the black is a bit harsh and draws attention to the arrows instead of the nodes.

Okay, I can see what I can do. But as you probably noticed, I am much better with Node.JS trickery than with graphical design ;-)

totally! personally I kind of enjoy trying to copy an existing design as closely as possible as a way to try to improve my marginal design skills, maybe I'll give it a shot later.

Seems that adding margin="0.3" in the blessed_repo nodes' attributes does the trick.

Here are screenshots of the current version:

I think I liked the gray arrows better with the smaller arrowheads, the black is a bit harsh and draws attention to the arrows instead of the nodes.

Oy, I had forgotten to address this valuable feedback. Pushed now!

The most impressive difference, I find, is in workflow C:

before after

assets/sass/layout.scss

jvns · 2025-09-07T12:41:00Z

This is awesome! I noticed the images lost their alt text, even if it was pretty minimal to begin with. Should that be an option to the {{ graphviz }}?

While Mermaid diagrams are more and more common on the internet, thanks to GitHub's support in their GitHub-flavored Markdown codeblocks, it is often frustratingly difficult to make elegant diagrams with them and to avoid overlapping or unnecessarily long edges. Graphviz, in contrast, allows much more control over the layout. The downside is that Graphviz is a command-line program, not a JavaScript library, and would require the diagrams to be pre-rendered and committed into the repository (a recipe for out-of-sync files). Enter `viz.js` (https://github.com/mdaines/viz-js). Essentially, it is a WebAssembly build of Graphviz. Therefore, it _does_ run in the browser. The downside, compared to Mermaid, is the size: While `mermaid.min.js` weighs around 25 kB, `viz-global.js` weighs around 1.4 MB. And I did not find any CDN that serves a current version, therefore I had to download it: VIZ_VERSION=3.17.0 npm pack @viz-js/viz@$VIZ_VERSION tar Oxvf viz-js-viz-$VIZ_VERSION.tgz package/dist/viz-global.js \ >static/js/viz-global.js With this commit, Graphviz dot diagrams can be added like this: {{< graphviz >}} digraph { a -> b -> c } {{< /graphviz >}} While I tried to make it as painless to work on these diagrams locally, there are more efficient ways than editing the HTML files, running Hugo and then reloading the page, for example Graphviz Online: https://dreampuf.github.io/GraphvizOnline/?engine=neato. This page works entirely in the browser, and uses a slightly outdated version of `viz.js`. Signed-off-by: Johannes Schindelin <[email protected]>

There are some issues when adding SVGs inside <svg> HTML elements, e.g. that positioning can be harder than with <img> ones, as pointed out at git#2052 (comment). Let's use <img> elements instead, passing the SVG via data URLs. There are more benefits to that: For example, most modern browsers allow copying an image into the clipboard that is specified as an `<img>` element, but not `<svg>` ones. Likewise, the "Open Image in New Tab" functionality typically only works with the former but not with the latter. Signed-off-by: Johannes Schindelin <[email protected]>

No need to set a background color, is there? Signed-off-by: Johannes Schindelin <[email protected]>

This can be done like so: {{< graphviz engine="neato" >}} Signed-off-by: Johannes Schindelin <[email protected]>

dscho · 2025-09-07T15:34:01Z

Range-diff

1: 514678d ! 1: cda28bd Add support for Graphviz dot diagrams

@@ Commit message
       }
       {{< /graphviz >}}
 
+    While I tried to make it as painless to work on these diagrams locally,
+    there are more efficient ways than editing the HTML files, running Hugo
+    and then reloading the page, for example Graphviz Online:
+    https://dreampuf.github.io/GraphvizOnline/?engine=neato. This page works
+    entirely in the browser, and uses a slightly outdated version of
+    `viz.js`.
+
     Signed-off-by: Johannes Schindelin <[email protected]>
 
  ## assets/js/application.js ##

2: 59e13e3 < -: --------- graphviz: make the diagrams' background transparent by default
3: 3a36663 < -: --------- graphviz: render the generated SVGs pleasantly in dark mode
-: --------- > 2: a7cac47 graphviz: use elements instead of ones
-: --------- > 3: f2d5b6f graphviz: make the diagrams' background transparent by default

4: 8e03288 ! 4: d9f9c5b graphviz: allow overriding the engine

@@ assets/js/application.js: var Graphviz = {
          },
 +        engine: x.getAttribute("engine") || "dot",
        }
-       const svg = vizInstance.renderSVGElement(x.innerText, options)
-       svg.classList.add("graphviz")
+       const svg = vizInstance.renderString(x.innerText, options)
+       const img = document.createElement('img')
 
  ## layouts/shortcodes/graphviz.html ##
 @@

5: 1c6bf1d ! 5: f2413fd Optionally pre-render the Graphviz diagrams

@@ Metadata
 Author: Johannes Schindelin <[email protected]>
 
  ## Commit message ##
-    Optionally pre-render the Graphviz diagrams
+    graphviz: optionally pre-generate the SVGs
 
     Since the WebAssembly version of Graphviz is not exactly light (1.4MB at
     the time of writing), and since it is a waste to let everybody re-render
@@ script/graphviz-ssr.js (new)
 +        },
 +        engine,
 +      })
-+      pre.replaceWith(`<svg class="graphviz"${svg.substring(svg.indexOf("<svg") + 4)}`)
++      const dataURL = `data:image/svg+xml;base64,${Buffer.from(svg).toString("base64")}`
++      pre.replaceWith(`<img src="${dataURL}"`)
 +    }
 +    console.log(`Rewriting ${path}`)
 +    writeFileSync(`${path}`, html.toString())

-: --------- > 6: d04135c graphviz: support the alt attribute
6: 4291c11 = 7: 0de205f deploy/ci: pre-render the Graphviz diagrams

7: cf7fe87 ! 8: 3f412a7 Replace the diagrams in about/distributed with Graphviz versions

@@ content/about/distributed.html: aliases:
      </p>
      <p class="center">
 -    <img src="{{< relurl "images/about/[email protected]" >}}" width="415" height="209" alt="Workflow A">
-+    {{< graphviz >}}
++    {{< graphviz alt="workflow A" >}}
 +    digraph dev_workflow {
 +      layout=neato;
 +      overlap=false;
@@ content/about/distributed.html: aliases:
      </p>
      <p class="center">
 -    <img src="{{< relurl "images/about/[email protected]" >}}" width="407" height="164" alt="Workflow B">
-+    {{< graphviz >}}
++    {{< graphviz alt="workflow B" >}}
 +    digraph workflow {
 +      layout=neato;
 +      overlap=false;
@@ content/about/distributed.html: aliases:
 +      edge [penwidth=3];
 +
 +      // Nodes
-+      blessed_repo [label="blessed\nrepository", fillcolor=teal, fontcolor=white, pos="0,3!"];
++      blessed_repo [label="blessed\nrepository", fillcolor=teal, fontcolor=white, margin="0.3", pos="0,3!"];
 +      integration_manager [label="integration\nmanager", fillcolor=orange, fontcolor=white, pos="0,1!"];
 +
 +      dev_pub1 [label="developer\npublic", fillcolor="#CCAA00", fontcolor=black, pos="2,3!"];
@@ content/about/distributed.html: aliases:
      </p>
      <p class="center">
 -    <img src="{{< relurl "images/about/[email protected]" >}}" width="562" height="303" alt="Workflow C">
-+    {{< graphviz >}}
++    {{< graphviz alt="workflow C" >}}
 +    digraph workflow {
 +      layout=neato;
 +      overlap=false;
@@ content/about/distributed.html: aliases:
 +      edge [fontname="Helvetica", penwidth=3];
 +
 +      // Nodes
-+      blessed_repo [label="blessed\nrepository", fillcolor=teal, fontcolor=white, pos="6,4!"];
++      blessed_repo [label="blessed\nrepository", fillcolor=teal, fontcolor=white, margin="0.3", pos="6,4!"];
 +      dictator [label="dictator", fillcolor=red, fontcolor=white, pos="0,4!"];
 +
 +      lieutenant1 [label="lieutenant", fillcolor="#CCAA00", fontcolor=white, pos="0,2.5!"];

dscho · 2025-09-07T15:34:48Z

This is awesome! I noticed the images lost their alt text, even if it was pretty minimal to begin with. Should that be an option to the {{ graphviz }}?

I added that in d04135c and 3f412a7

jnavila · 2025-09-07T15:38:54Z

This may also be interesting for Progit indeed.

dscho · 2025-09-07T15:45:41Z

This may also be interesting for Progit indeed.

@jnavila but ProGit2 uses AsciiDoc, where I would not really know how to integrate the Graphviz step. But seeing as AsciiDoc needs to be run "server-side", anyway, Graphviz diagrams should be much easier to integrate into that process than they were here, with a Hugo-based process (I did spend 3 dozen hours on this).

The major caveat I'd like to call out is that git-scm.com post-processes the AsciiDoc sources from ProGit2 in a quite "home-grown" way, via a Ruby script, and any changes you make in ProGit2 would require changes to that script, too. Unless you integrate Graphviz in a way that the AsciiDoc refers already to the Graphviz output, in which case nothing really changes for downstream users like git-scm.com.

To1ne

@dscho This is nice work. To be honest, I like the graphs more than the original. They are more consistent.

I've added some thoughts and questions.

content/diagram-list.html

script/graphviz-ssr.js

layouts/shortcodes/graphviz.html

The WebAssembly version of Graphviz is not exactly light (1.4 megabytes at the time of writing). And it wasteful to let everybody re-render the SVG client-side over and over again even though the diagram's definition hasn't changed. So let's add a script that performs that rendering "on the server side" (more precisely: during deployment). This script takes no arguments and post-processes the output of Hugo in `public/`. For performance reasons, it requires the list of files that contain Graphviz diagrams. With other sites, it might not matter much because there might only be a handful pages. However, on git-scm.com there _are_ thousands of files that do not contain any Graphviz diagrams, and therefore it is a necessary optimization to process only the files that _do_ contain Graphviz diagrams. To get that list, a new layout and page are added that Hugo processes, identifying said list of files and writing the result to `public/diagram-list.html`. Since this script runs via Node.JS and therefore lacks the convenient built-in HTML parser of browser-based JavaScript engines, a prerequisite is to run `npm install` so that the `node-html-parser` package is available. A note about the slightly inelegant way the `graphviz` class is added to the generated SVGs: Sadly, `node-html-parser` is not smart enough to handle `element.classList.add(...)` followed by `element.toString()` correctly, and as a result the output would _not_ have the added class. But there's always crude string processing to save the day. Signed-off-by: Johannes Schindelin <[email protected]>

Since we're generating `<img>` elements anyway, might just as well keep that accessibility support. Signed-off-by: Johannes Schindelin <[email protected]>

This avoids the 1.4MB download on the client-side, in favor of inlined, small SVG elements. Signed-off-by: Johannes Schindelin <[email protected]>

This topic corresponds to git#2052. Signed-off-by: Johannes Schindelin <[email protected]>

dscho · 2025-09-10T15:36:10Z

Range-diff

1: f2413fd ! 1: e458803 graphviz: optionally pre-generate the SVGs

@@ Metadata
  ## Commit message ##
     graphviz: optionally pre-generate the SVGs
 
-    Since the WebAssembly version of Graphviz is not exactly light (1.4MB at
-    the time of writing), and since it is a waste to let everybody re-render
-    the SVG client-side over and over again even though the diagram's
-    definition hasn't changed, let's add a script that performs that
-    rendering "on the server side" (more precisely: during deployment).
+    The WebAssembly version of Graphviz is not exactly light (1.4 megabytes
+    at the time of writing). And it wasteful to let everybody re-render the
+    SVG client-side over and over again even though the diagram's definition
+    hasn't changed. So let's add a script that performs that rendering "on
+    the server side" (more precisely: during deployment).
 
-    This script takes no arguments and post-processes the output of Hugo in
-    `public/`.
+    This script takes no arguments and post-processes the output of Hugo
+    in `public/`.
 
     For performance reasons, it requires the list of files that contain
-    Graphviz diagrams. With this here site, it might not matter much because
-    there are only a handful images here. However, I want to reuse the same
-    method on git-scm.com where there _are_ thousands of files that do not
-    contain any Graphviz diagrams, and therefore it is a necessary
-    optimization to process only the files that _do_ contain Graphviz
-    diagrams.
+    Graphviz diagrams. With other sites, it might not matter much because
+    there might only be a handful pages. However, on git-scm.com there _are_
+    thousands of files that do not contain any Graphviz diagrams, and
+    therefore it is a necessary optimization to process only the files that
+    _do_ contain Graphviz diagrams.
 
     To get that list, a new layout and page are added that Hugo processes,
-    identifyng said list of files and writing the result to
+    identifying said list of files and writing the result to
     `public/diagram-list.html`.
 
     Since this script runs via Node.JS and therefore lacks the convenient
@@ Commit message
  ## content/diagram-list.html (new) ##
 @@
 +---
-+layout: diagram-list
++outputs:
++  - json
 +---
 
- ## layouts/diagram-list.html (new) ##
+ ## hugo.yml ##
+@@ hugo.yml: markup:
+   goldmark:
+     renderer:
+       unsafe: true
++mediaTypes:
++  application/json:
++    suffixes:
++    - json
+ module:
+   mounts:
+   - source: content
+
+ ## layouts/_default/single.json.json (new) ##
 @@
-+<pre>
-+{{ range .Site.Pages -}}
-+  {{- if in .RawContent "{{< graphviz" -}}
-+     public{{ .Path }}.html{{ "\n" -}}
-+  {{- end -}}
-+{{- end -}}
-+</pre>
++{{- $diagram_list := where .Site.Pages "RawContent" "like" "{{< graphviz" -}}
++{{- $diagram_list | jsonify -}}
+ \ No newline at end of file
 
  ## package.json ##
 @@
@@ script/graphviz-ssr.js (new)
 + * via `viz-js`.
 + */
 +;(async () => {
-+  for (const path of readFileSync("public/diagram-list.html", "utf-8")
-+    .split("\n")
-+    .filter((x) => x.startsWith("public/"))) {
++  for (const { Path: pathInPublic } of JSON.parse(readFileSync("public/diagram-list.json", "utf-8"))) {
++    const path = `public${pathInPublic}.html`
 +    const contents = readFileSync(path, "utf-8")
 +    const html = parse(contents)
 +    const vizImport = html.querySelector('script[src$="viz-global.js"]')
@@ script/graphviz-ssr.js (new)
 +        engine,
 +      })
 +      const dataURL = `data:image/svg+xml;base64,${Buffer.from(svg).toString("base64")}`
-+      pre.replaceWith(`<img src="${dataURL}"`)
++      pre.replaceWith(`<img src="${dataURL}" />`)
 +    }
 +    console.log(`Rewriting ${path}`)
 +    writeFileSync(`${path}`, html.toString())

2: d04135c ! 2: 66d59f7 graphviz: support the alt attribute

@@ script/graphviz-ssr.js: import Viz from "../static/js/viz-global.js"
 +      const alt = pre.getAttribute("alt")
 +      const altAttr = !alt ? '' : ` alt='${alt.replaceAll("&", "&amp;").replaceAll("'", "&#39;")}'`
        const dataURL = `data:image/svg+xml;base64,${Buffer.from(svg).toString("base64")}`
--      pre.replaceWith(`<img src="${dataURL}"`)
-+      pre.replaceWith(`<img${altAttr} src="${dataURL}"`)
+-      pre.replaceWith(`<img src="${dataURL}" />`)
++      pre.replaceWith(`<img${altAttr} src="${dataURL}" />`)
      }
      console.log(`Rewriting ${path}`)
      writeFileSync(`${path}`, html.toString())

3: 0de205f = 3: 4f58ebc deploy/ci: pre-render the Graphviz diagrams
4: 3f412a7 = 4: 884b895 Replace the diagrams in about/distributed with Graphviz versions

This topic corresponds to git#2052. Signed-off-by: Johannes Schindelin <[email protected]>

dscho · 2025-09-10T19:48:49Z

I noticed the images lost their alt text, even if it was pretty minimal to begin with. Should that be an option to the {{ graphviz }}?

I wanted to reply to this earlier, to say that I implemented this in 66d59f7

To1ne

@dscho Tiny comment on the last commit message. From my point of view it's ready to ship.

To1ne · 2025-09-12T08:02:00Z

content/about/distributed.html

@@ -27,22 +27,101 @@ <h4>Subversion-Style Workflow</h4>
    A centralized workflow is very common, especially from people transitioning from a centralized system. Git will not allow you to push if someone has pushed since the last time you fetched, so a centralized model where all developers push to the same server works just fine.
    </p>
    <p class="center">


From the commit message:

With this change, the text in those diagrams is copy/paste-able.

@dscho That no longer seems to be the case now <svg> is no longer is inlined. It's a nitpick on the commit message, I don't consider this an issue that it's not the case. Do you think it worthy to edit the commit message?

True. I force-pushed a fix:

Range-diff

1: a2c59d6 ! 1: 352dbbf Replace the diagrams in about/distributed with Graphviz versions

@@ Commit message Replace the diagrams in `about/distributed` with Graphviz versions This commit recreates those diagrams that have been provided as `.png` - files before. - - With this change, the text in those diagrams is copy/paste-able. But of - course that's not the real reason I made this change, the real reason is + files before. Of course, this is not strictly necessary because the + previous `.png` diagrams served their purpose well enough. But I wanted to show off that we can now use Graphviz diagrams on git-scm.com. + Note: When developing this patch, I had considered inlining the SVGs as + `<svg>` instead of `<img>`. That would have had the following + advantages: + + - The text in those diagrams would have been copy/paste-able. + + - We could have defined explicit colors for dark mode, as the `<style>` + element would have been able to refer to the HTML document's `:root` + element's dark mode definitions. + + However, having SVGs embedded in `<img>` elements have a few benefits: + + - Current browsers allow to `Open Image in New Tab` (where the text + would be copy/paste-able again). + + - Current browsers allow to `Save Image` (even if there is no way to + specify a filename, see https://github.com/whatwg/html/issues/2722). + + - By using `<img>` elements, we can reuse the previous work on images in + dark mode. + Signed-off-by: Johannes Schindelin <[email protected]> ## content/about/distributed.html ##

This commit recreates those diagrams that have been provided as `.png` files before. Of course, this is not strictly necessary because the previous `.png` diagrams served their purpose well enough. But I wanted to show off that we can now use Graphviz diagrams on git-scm.com. Note: When developing this patch, I had considered inlining the SVGs as `<svg>` instead of `<img>`. That would have had the following advantages: - The text in those diagrams would have been copy/paste-able. - We could have defined explicit colors for dark mode, as the `<style>` element would have been able to refer to the HTML document's `:root` element's dark mode definitions. However, having SVGs embedded in `<img>` elements have a few benefits: - Current browsers allow to `Open Image in New Tab` (where the text would be copy/paste-able again). - Current browsers allow to `Save Image` (even if there is no way to specify a filename, see whatwg/html#2722). - By using `<img>` elements, we can reuse the previous work on images in dark mode. Signed-off-by: Johannes Schindelin <[email protected]>

This topic corresponds to git#2052. Signed-off-by: Johannes Schindelin <[email protected]>

dscho · 2025-09-13T12:10:45Z

@jvns please let me know if you want me to rebase #2049.

dscho requested review from To1ne and jvns September 7, 2025 12:05

dscho self-assigned this Sep 7, 2025

dscho commented Sep 7, 2025

View reviewed changes

dscho force-pushed the graphviz-diagrams branch from 02adff6 to a3d3ba3 Compare September 7, 2025 12:21

jvns reviewed Sep 7, 2025

View reviewed changes

assets/sass/layout.scss Outdated Show resolved Hide resolved

dscho force-pushed the graphviz-diagrams branch from a3d3ba3 to cf7fe87 Compare September 7, 2025 12:40

dscho added 4 commits September 7, 2025 17:24

graphviz: make the diagrams' background transparent by default

f2d5b6f

No need to set a background color, is there? Signed-off-by: Johannes Schindelin <[email protected]>

graphviz: allow overriding the engine

d9f9c5b

This can be done like so: {{< graphviz engine="neato" >}} Signed-off-by: Johannes Schindelin <[email protected]>

dscho force-pushed the graphviz-diagrams branch from cf7fe87 to 3f412a7 Compare September 7, 2025 15:34

dscho mentioned this pull request Sep 7, 2025

Add a Git cheat sheet #2049

Open

To1ne reviewed Sep 8, 2025

View reviewed changes

content/diagram-list.html Show resolved Hide resolved

script/graphviz-ssr.js Outdated Show resolved Hide resolved

script/graphviz-ssr.js Show resolved Hide resolved

layouts/shortcodes/graphviz.html Show resolved Hide resolved

dscho added 3 commits September 10, 2025 17:29

graphviz: support the alt attribute

66d59f7

Since we're generating `<img>` elements anyway, might just as well keep that accessibility support. Signed-off-by: Johannes Schindelin <[email protected]>

deploy/ci: pre-render the Graphviz diagrams

4f58ebc

This avoids the 1.4MB download on the client-side, in favor of inlined, small SVG elements. Signed-off-by: Johannes Schindelin <[email protected]>

dscho added a commit to dscho/git-scm.com that referenced this pull request Sep 10, 2025

Merge branch 'graphviz-diagrams' into gh-pages

ac074a2

This topic corresponds to git#2052. Signed-off-by: Johannes Schindelin <[email protected]>

dscho force-pushed the graphviz-diagrams branch from 3f412a7 to 884b895 Compare September 10, 2025 15:32

dscho added a commit to dscho/git-scm.com that referenced this pull request Sep 10, 2025

Merge branch 'graphviz-diagrams' into gh-pages

e15d5cc

This topic corresponds to git#2052. Signed-off-by: Johannes Schindelin <[email protected]>

dscho force-pushed the graphviz-diagrams branch from 884b895 to a2c59d6 Compare September 10, 2025 19:45

To1ne approved these changes Sep 12, 2025

View reviewed changes

dscho added a commit to dscho/git-scm.com that referenced this pull request Sep 13, 2025

Merge branch 'graphviz-diagrams' into gh-pages

2bbe54d

This topic corresponds to git#2052. Signed-off-by: Johannes Schindelin <[email protected]>

dscho force-pushed the graphviz-diagrams branch from a2c59d6 to 352dbbf Compare September 13, 2025 11:36

dscho merged commit 992366e into git:gh-pages Sep 13, 2025
1 check passed

dscho deleted the graphviz-diagrams branch September 13, 2025 12:10

Add support for Graphviz diagrams #2052

Add support for Graphviz diagrams #2052

Uh oh!

Conversation

dscho commented Sep 7, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Context

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

jvns commented Sep 7, 2025

Uh oh!

dscho commented Sep 7, 2025

Uh oh!

dscho commented Sep 7, 2025

Uh oh!

jnavila commented Sep 7, 2025

Uh oh!

dscho commented Sep 7, 2025

Uh oh!

To1ne left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

dscho commented Sep 10, 2025

Uh oh!

dscho commented Sep 10, 2025

Uh oh!

To1ne left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

dscho commented Sep 13, 2025

Uh oh!

Uh oh!

dscho commented Sep 7, 2025 •

edited

Loading