Crates.io | mdbook-graphviz |
lib.rs | mdbook-graphviz |
version | 0.2.1 |
source | src |
created_at | 2019-11-01 16:29:40.907556 |
updated_at | 2024-08-10 05:37:06.575543 |
description | mdbook preprocessor to add graphviz support |
homepage | https://github.com/dylanowen/mdbook-graphviz |
repository | https://github.com/dylanowen/mdbook-graphviz |
max_upload_size | |
id | 177397 |
size | 113,277 |
cargo install mdbook-graphviz
Install Graphviz
brew install graphviz
book.toml
[preprocessor.graphviz]
command = "mdbook-graphviz"
output-to-file = false # defaults to false, change to true to create SVG files instead of rendering them inline
Just dot
is supported, but any of the other graphviz tools would be easy to add.
dot
Code Block For Processing```dot process
digraph {
"processed" -> "graph"
}
```
<div class="mdbook-graphviz-output"><svg>...</svg></div>
The class
attribute gives you the chance to apply a common style to all
the output images (e.g. center all of them).
dot
Code Blocks Without The process
Flag Are Ignored```dot
digraph {
"processed" -> "graph"
}
```
```dot
digraph {
"processed" -> "graph"
}
```
The default is to embed the SVG as HTML in the Markdown, however if this causes problems or if the actual files are
needed you can disable this via the output-to-file
flag:
[preprocessor.graphviz]
output-to-file = true
or
MDBOOK_preprocessor__graphviz__output_to_file="true" mdbook build
This .gitignore
should cover the generated SVG files.
*.generated.svg
When using output-to-file
, links can be added to the images via the link-to-file
flag:
[preprocessor.graphviz]
output-to-file = true
link-to-file = true
or
MDBOOK_preprocessor__graphviz__output_to_file="true" MDBOOK_preprocessor__graphviz__link_to_file="true" mdbook build
Sometimes you don't want to write dot code, but instead include it from a file:
```dot
{{#include path/to/file.dot}}
```
In this case, you might want to modify the order of preprocessors, so the include directives get resolved before it's passed to Graphviz.
In that case, make sure your [preprocessor.graphviz]
section in the config
orders itself after links
:
[preprocessor.graphviz]
after = ["links"]
info-string
Some tools prefer a specific annotation for dot/graphviz diagrams.
For compatability with these tools mdbook-graphviz
can support a custom value for marking diagrams it should process.
This is via the info-string
flag:
[preprocessor.graphviz]
info-string = "graphviz"
or
MDBOOK_preprocessor__graphviz__info_string="graphviz" mdbook build
More information about preprocessors and ordering can be found here.