fix(docs): render the HMA diagram — memory.md → memory.mdx #82
Reference in New Issue
Block a user
Delete Branch "fix/memory-page-mdx-render"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Memory Architecture page showed the HMA diagram as missing. Root cause: the page embedded it with a JSX
tag, but the file was plain .md, so the renderer printed the tag as literal text (the page showed the raw
markup). The SVG itself renders perfectly and is served 200. Every other diagram page (concepts.mdx, index.mdx) uses the identical
pattern and works because they are .mdx. Rename memory.md → memory.mdx (body verified MDX-safe; URL unchanged) so the JSX parses and the diagram renders.
The Memory Architecture page embedded the HMA diagram with a JSX <img src="/diagrams/memory-hma.svg" style={{...}} /> tag, but the file was a plain `.md`, so the Fumadocs renderer printed the tag as LITERAL TEXT instead of rendering the image (the page showed the raw <img ...> markup, hence the "missing diagram"). The SVG itself is correct and served fine. Every other diagram page (concepts.mdx, index.mdx) uses the identical `<img ... style={{ width:'100%' }} />` pattern and renders correctly because they are `.mdx`. Rename memory.md → memory.mdx to match the convention so the JSX parses. The body has zero MDX-incompatible content (no bare `{}`/`<x>` in prose, verified), and Fumadocs maps both .md and .mdx to the same /docs/architecture/memory route, so the URL is unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>Renders the HMA diagram: the page embedded a JSX
in a plain .md so it printed as literal text; renaming to .mdx (matching concepts.mdx/index.mdx; body verified MDX-safe; URL unchanged) makes it parse. The SVG itself renders perfectly. Approve.