Skip to content

chore(docs): MDX 3 compat (HTML→JSX comments, drop {#anchor} in introduction) (#41 follow-up)#182

Merged
ChrisonSimtian merged 1 commit into
mainfrom
chore/docs-mdx-compat
May 25, 2026
Merged

chore(docs): MDX 3 compat (HTML→JSX comments, drop {#anchor} in introduction) (#41 follow-up)#182
ChrisonSimtian merged 1 commit into
mainfrom
chore/docs-mdx-compat

Conversation

@ChrisonSimtian
Copy link
Copy Markdown
Owner

Summary

Pre-landing the mechanical MDX-compat changes to `docs/` so the Docusaurus 3 build for #41 can run against `main` without local patches. Splits out cleanly from #181 (closed; CF Pages was the wrong architecture).

Changes (8 files)

File Change
`docs/introduction.md` HTML→JSX comment + drop `{#fast-track}` / `{#coming-from-cake}` heading IDs
`docs/01-getting-started/02-setup.md` HTML→JSX comments (2× MSBuild commented examples)
`docs/02-fundamentals/05-targets.md` HTML→JSX comments (3× annotation lines)
`docs/02-fundamentals/06-parameters.md` HTML→JSX comments (6× snippet markers)
`docs/02-fundamentals/10-logging.md` HTML→JSX comments (snippet markers)
`docs/03-common/03-paths.md` HTML→JSX comments
`docs/03-common/05-repository.md` HTML→JSX comments (snippet markers)
`docs/03-common/08-cli-tools.md` HTML→JSX comments

Why MDX 3 needs this

Docusaurus 3 (latest) parses every `.md` / `.mdx` file through MDX 3. MDX 3 treats `` as an attempted JSX tag and errors out (it's not valid JSX). The documented replacement is `{/* ... */}` — same effect (invisible in output), MDX-parsable. The anchor-ID removal is for the same reason — MDX 3 sees `{#fast-track}` after a heading and tries to parse it as a JS expression; `#` isn't valid in expressions, so it fails. Slugs auto-generate from heading text instead.

Verified

Follow-up

  • Falloutdocs repo with the actual Docusaurus scaffold + deploy workflow (next).

Closes

🤖 Generated with Claude Code

…#anchor} in introduction)

Mechanical compatibility pass so the docs/ tree compiles under MDX 3
(the parser used by Docusaurus 3 — needed by the upcoming docs-site
work tracked in #41).

## Changes

- `<!-- ... -->` → `{/* ... */}` across 8 files. MDX 3 parses HTML
  comments as JSX expressions and fails; the JSX comment form is the
  documented replacement. Inner content is unchanged. Rendered output
  is unaffected (comments are not visible).
- `introduction.md`: drop the two explicit `{#anchor}` IDs on H2
  headings (Fast Track, Coming from Cake). Docusaurus auto-generates
  slugs from heading text, so inbound `#fast-track` / `#coming-from-cake`
  fragment links will need a one-time refresh if anything points at
  them. Nothing in-repo does today.

## Why now

These touch-ups are needed before any Docusaurus 3 build can succeed,
regardless of where the rendered site is hosted. Pre-landing them so
the downstream docs-site work (#41) can pull from main without local
patches.

Refs #41
@ChrisonSimtian ChrisonSimtian merged commit 860e80a into main May 25, 2026
1 check passed
@ChrisonSimtian ChrisonSimtian deleted the chore/docs-mdx-compat branch May 25, 2026 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant