Mermaid diagrams are not rendered in the SDK guide

[embano1]

It seems that the documentation page does not support rendering mermaid diagrams. None of the pages using mermaid code tags render e.g.,

https://docs.aws.amazon.com/durable-execution/testing/runner/

[yaythomas]

that used to work 😬

[yaythomas]

Zensical does not bundle Mermaid. At runtime it points at https://unpkg.com/mermaid@11/dist/mermaid.min.js for the mermaid transform script.

The docs.aws.amazon.com CSP doesn't allow unpkg and blocks this script.

it works in test/staging because these do not have the same CSP restrictions. Which is what I was thinking of with the "used to work", but it never worked here in prod.

Still investigating options, but likely solution is

Self-host Mermaid's "tiny" build (@mermaid-js/tiny), which ships as a single UMD file (mermaid.tiny.js) with no lazy-loaded chunks. All five current diagrams are supported types (flowchart, sequence diagram, state diagram,
class diagram, ER diagram). Unsupported types under tiny: mindmap, architecture, KaTeX math (all unused). https://mermaid.ai/open-source/config/usage.html#tiny-mermaid

Implementation:

1. Download a pinned version (e.g.@mermaid-js/tiny@11.6.0/dist/mermaid.tiny.js) into
   docs/assets/javascripts/mermaid.tiny.js. Record the SHA-256.
2. Add a small init script docs/javascripts/mermaid-init.js that calls mermaid.initialize({ startOnLoad: false, securityLevel: 'strict' }).
3. Register both files under extra_javascript in zensical.toml. Zensical's existing integration picks up window.mermaid automatically when present.
4. Verify locally with zensical serve, then deploy and confirm the five pages render under the CSP.

as for vendoring, either
a) package.json with a pinned dependency that installs client-side or with CI so it's not source controlled, or
b) commit the tiny minifed js with .gitattributes binary