Swastika/mint docs/md parse fix#2221
Conversation
Greptile SummaryThis PR makes the
Confidence Score: 4/5Safe to merge with awareness that the h1→h2 heading demotions and backtick-wrapped hyperlinks from earlier review threads remain unaddressed in the changed files. The MDX compatibility fixes are correct and complete across all changed files — no HTML comments remain in any .md file, the details splits are properly done, and all navigation paths in docs.json resolve to existing files. The unresolved items from prior review threads (heading demotions in ubuntu/osx/nix/blueprints and broken link rendering in docker.md) are still present in this diff. docs/installation/ubuntu.md, docs/installation/osx.md, docs/installation/nix.md, docs/usage/blueprints.md (h1 demoted to h2), and docs/development/docker.md (backtick-wrapped hyperlinks) Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[.mintignore: remove **/*.md] --> B[All .md files now parsed by Mintlify MDX]
B --> C{MDX-incompatible syntax?}
C -- "HTML comments" --> D["Convert to results blocks / JSX comments"]
C -- "details+summary on one line" --> F["Split to two lines"]
C -- "Raw img with attrs" --> G["Convert to Markdown image — loses width attr"]
C -- "Heading levels h1 to h2" --> H["Pages lose their h1 title anchor"]
D --> I[MDX-compatible]
F --> I
G --> J[MDX-compatible but style regression]
H --> K[Page title may fall back to filename]
I --> L[docs.json: add full nav tree]
J --> L
K --> L
L --> M[Mintlify build can proceed]
Reviews (12): Last reviewed commit: "fix link and code block title" | Re-trigger Greptile |
| @@ -1,4 +1,4 @@ | |||
| # System Dependencies Install (Ubuntu 22.04 or 24.04) | |||
| ## System Dependencies Install (Ubuntu 22.04 or 24.04) | |||
There was a problem hiding this comment.
Demoting # to ## removes the document's only h1 heading. Mintlify (and GitHub preview) derive the page title from the frontmatter or the first h1; without one, the page title will fall back to the filename. The same applies to osx.md and nix.md, which also had their h1 changed to h2 in this PR. If these files are included in Mintlify navigation without frontmatter title fields, they will show generic titles.
| @@ -1,4 +1,4 @@ | |||
| # Blueprints | |||
| ## Blueprints | |||
| # Ignore dependency trees under the docs workspace (would otherwise be scanned as pages). | ||
| node_modules/ |
There was a problem hiding this comment.
Untouched files still contain MDX-incompatible HTML comments
Removing **/*.md from .mintignore exposes all markdown files to Mintlify's MDX parser, but three files in docs/agents/docs/ were not fixed and still contain <!--Result:--> comment syntax that the MDX parser will reject: docs/agents/docs/codeblocks.md (11 occurrences), docs/agents/docs/index.md (5 occurrences), and docs/agents/docs/doclinks.md (2 functional <!-- doclinks-ignore-* --> markers). The Mintlify build will fail on these files after this PR lands. They need the same <!--Result:--> → ```results treatment applied to the other files in this PR, or the docs/agents/docs/ path should be added to .mintignore.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
| "usage/modules", | ||
| "usage/blueprints", | ||
| "usage/configuration", | ||
| "usage/lcm", |
There was a problem hiding this comment.
Many of these titles are not rendered correctly. For example this shows up as Lcm instead of LCM. Same for others, like PythonApi instead of Python API.
There was a problem hiding this comment.
mintlify takes up the file name as title by default, I've changed the file names in next PR.
| "usage/lcm", | ||
| "usage/transforms", | ||
| "usage/visualization", | ||
| "usage/cli", |
There was a problem hiding this comment.
| { | ||
| "group": "Memory", | ||
| "pages": [ | ||
| "capabilities/memory/index", |
There was a problem hiding this comment.
same with this, mintlify takes up the file name as title by default. didn't want to touch folder structure in this PR to avoid confusion. changed the names and flattened the nested folder in the next PR.






Problem
Existing markdown files syntax is incompatible with mintlify's MDX parser- HTML comments, raw image syntax, unclosed tags cause parsing errors during build.
Solution
<!-- -->comments.<details>/<summary>blocks