🧜‍♀️ Create images of mermaid diagrams for static exports

.changeset/cool-pigs-deny.md

@@ -0,0 +1,5 @@
+---
+'myst-common': patch
+---
+
+Added `options?: PluginOptions` to `TransformSpec` type. Enables passing configuration options to transform plugins.

.changeset/orange-rockets-relate.md

@@ -0,0 +1,8 @@
+---
+'myst-cli': patch
+---
+
+Integrated transform loading from options with proper plugin utilities.
+
+Added mermaid transform import and configuration
+Integrated mermaid transform into Typst build pipeline.

.changeset/stale-ghosts-drum.md

@@ -0,0 +1,5 @@
+---
+'myst-spec-ext': patch
+---
+
+Added `label`, `identifier`, and `html_id` to `Image` type

docs/diagrams.md

@@ -24,3 +24,32 @@ flowchart LR
 :::{note}
 Both GitHub and JupyterLab ([#101](https://github.com/jupyter/enhancement-proposals/pull/101)) support the translation of a code-block ` ```mermaid ` to a mermaid diagram directly, this can also be used by default in MyST.
 :::
+
+## Rendering for Static Exports
+
+MyST supports static rendering of Mermaid diagrams for static export formats (PDF, Word, LaTeX, Typst). This feature converts Mermaid syntax to base64-encoded SVG or PNG images during the build process, ensuring consistent rendering across all static output formats.
+
+:::{important} Prerequisites
+To use static Mermaid rendering, you need the Mermaid CLI installed:
+
+```bash
+npm install -g @mermaid-js/mermaid-cli
+```
+
+:::
+
+:::{note .dropdown} For CI Environments
+
+The Mermaid CLI uses Puppeteer which may require special configuration in CI environments. MyST automatically handles this by detecting the `CI` environment variable or you can manually control it:
+
+```bash
+# Automatic detection (recommended for CI)
+CI=true npm run build
+
+# Manual control
+MERMAID_NO_SANDBOX=true npm run build
+```
+
+This automatically creates a Puppeteer configuration file with `--no-sandbox` flag to resolve sandbox issues in Linux CI environments.
+
+:::