mermaid-diagram-authoring

To render Mermaid diagrams into SVG for Pandoc, this workflow extracts diagram blocks from a centralized CATALOG.md, renders them via mmdc, and uses a Pandoc Lua filter to inject the SVG output while maintaining bilingual caption and ID consistency.

Managing Mermaid syntax regressions in technical writing requires a catalog-driven pipeline that centralizes diagrams in CATALOG.md, extracts them to individual files, and applies CI linting to validate diagram syntax and ensure 1:1 ID consistency.

A catalog-driven approach handles bilingual documentation by centralizing all Mermaid diagrams in a single CATALOG.md, allowing the same diagram to be shared across languages while a Pandoc Lua filter manages caption and ID consistency for both KO and EN outputs.

Yes, you need mmdc and Puppeteer to automate Mermaid SVG rendering, as the pipeline relies on mmdc to convert extracted diagram files into SVG format before injecting them into the final Pandoc document output.

Yes, you can validate Mermaid diagram syntax and check for 1:1 ID consistency during CI linting by using standard text processing tools like grep, awk, xargs, and diff to compare extracted diagrams against the centralized catalog.

Mermaid diagrams break across multiple languages due to syntax regressions and inconsistent diagram IDs, which this pipeline solves by centralizing diagrams in CATALOG.md and applying strict CI linting to validate syntax and enforce 1:1 ID consistency.