Skip to content

Fix titled admonitions rendering as literal text - #7

Merged
tanglearncode merged 1 commit into
mainfrom
docs/fix-admonition-titles
Jul 12, 2026
Merged

tanglearncode merged 1 commit into
mainfrom
docs/fix-admonition-titles

Conversation

@tanglearncode

Copy link
Copy Markdown
Contributor

Problem

Every titled admonition (:::tip Title, :::info Title, …) renders as raw ::: text on docs.neatcontext.com instead of a styled callout box. Confirmed against the live HTML: on the intro page the title-less :::note renders correctly while :::tip Quick hands-on demo falls through as a literal <p>:::tip …</p>.

Root cause

The site enables the faster build pipeline (future.v4: true + @docusaurus/faster), which uses the Rust mdx-rs MDX parser. That parser only accepts the canonical directive-label form :::type[Title]. The legacy space-separated :::type Title form isn't recognized, so the directive silently fails to parse and is emitted as a literal paragraph. Title-less admonitions parse fine in both parsers, which is why the lone :::note still worked.

Fix

Convert all 17 titled admonitions across the docs to the bracket form, e.g. :::tip Quick hands-on demo:::tip[Quick hands-on demo]. This is spec-correct and renders under both parsers.

Verification

  • npm run build succeeds.
  • Built HTML now has 0 literal ::: occurrences and proper theme-admonition boxes on the affected pages (intro, getting-started, and the rest).

🤖 Generated with Claude Code

The faster build pipeline (future.v4 + @docusaurus/faster) uses the Rust
mdx-rs parser, which only accepts the canonical `:::type[Title]` directive
label form. The legacy space-separated `:::type Title` form silently fell
through as a literal paragraph, so every titled admonition rendered as raw
`:::` text on docs.neatcontext.com. Convert all 17 titled admonitions to the
bracket form so they render as callout boxes under both parsers.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@tanglearncode
tanglearncode merged commit 7fee4b9 into main Jul 12, 2026
1 check passed
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