Swastika/mint docs/new pages#2071
Conversation
Greptile SummaryThis PR bootstraps the Mintlify docs site for DimOS by adding
Confidence Score: 5/5Documentation-only change adding Mintlify config and two new MDX pages — no runtime code is touched. All navigation slugs in docs.json map to real files on disk after multiple fix commits addressing the originally broken paths. Card hrefs in both MDX pages resolve to existing documents. The change is entirely additive and isolated to the docs directory. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[docs.json] --> B[Getting Started]
A --> C[Usage]
A --> D[Capabilities]
A --> E[Platforms]
A --> F[Development]
A --> G[For Agents]
B --> B1[introduction.mdx]
B --> B2[quickstart.mdx]
B --> B3[requirements.md]
B --> B4[installation/ubuntu\ninstallation/osx\ninstallation/nix]
C --> C1[usage/README\nblueprints, modules, cli, ...]
C --> C2[Data Streams group]
C --> C3[Sensor Streams group]
C --> C4[Transports group]
D --> D1[capabilities/agents/readme]
D --> D2[Navigation group\nnavigation/readme + native/index]
D --> D3[Manipulation group]
D --> D4[Memory group]
D --> D5[capabilities/perception/readme]
E --> E1[platforms/quadruped/go2/index]
E --> E2[platforms/humanoid/g1/index]
F --> F1[development/docker\ntesting, profiling, ...]
G --> G1[agents/index\nagents/style\nagents/testing\nagents/docs/*]
Reviews (5): Last reviewed commit: "fix greptile error: remove duplicate pat..." | Re-trigger Greptile |
| First replay failing? Most issues are network or LFS related. See [Replay troubleshooting](/troubleshooting/replay). | ||
| </Note> |
There was a problem hiding this comment.
Broken link to non-existent troubleshooting page
/troubleshooting/replay is linked in the live quickstart content but this page does not exist in the file system or in the docs.json navigation. Users who hit a replay failure and follow the link will land on a 404. A troubleshooting/ group should be added to the navigation, or this sentence should be removed/replaced with a GitHub Issues link until the page is written.
| "pages": [ | ||
| "platforms/quadruped-go2", | ||
| "platforms/humanoid-g1" | ||
| ] |
There was a problem hiding this comment.
Platform nav paths don't match the actual directory structure
The navigation uses platforms/quadruped-go2 and platforms/humanoid-g1, but the existing files live at platforms/quadruped/go2/index.md and platforms/humanoid/g1/index.md. Mintlify resolves slugs from file paths, so both sidebar links will 404. Either rename the directories to platforms/quadruped-go2/ and platforms/humanoid-g1/, or update the nav entries to platforms/quadruped/go2 and platforms/humanoid/g1.
| "group": "Navigation", | ||
| "pages": [ | ||
| "capabilities/navigation/overview", | ||
| "capabilities/navigation/native-go2" |
There was a problem hiding this comment.
Navigation path doesn't match the existing file
capabilities/navigation/native-go2 references a file that doesn't exist. The actual file is docs/capabilities/navigation/native/index.md, which Mintlify would serve at the slug capabilities/navigation/native. Until the file is renamed or moved, this nav entry will 404.
| "usage/data_streams/overview", | ||
| "usage/data_streams/reactivex", | ||
| "usage/data_streams/advanced_streams", | ||
| "usage/data_streams/quality_filter", | ||
| "usage/data_streams/temporal_alignment", | ||
| "usage/data_streams/storage_replay" |
There was a problem hiding this comment.
overview sub-pages don't exist for Data Streams or Sensor Streams
Both usage/data_streams/overview and usage/sensor_streams/overview are listed in the nav, but neither overview.md nor overview.mdx exists in those directories — only README.md. Mintlify maps README.md to the directory-level slug (usage/data_streams), not to a child overview path. These entries will produce 404s. The same pattern repeats in the Sensor Streams group and in several other groups referencing overview pages that haven't been created yet.
| "light": "#1682a3", | ||
| "dark": "#1682a3" | ||
| }, | ||
| "favicon": "/favicon.svg", |
| "logo": { | ||
| "light": "/assets/dimensional-logo-master-transparent.png", | ||
| "dark": "/assets/dimensional-logo-master-transparent.png" | ||
| }, |
There was a problem hiding this comment.
Same transparent logo for both light and dark themes
light and dark both point to the same transparent PNG. If the logo has dark-coloured text or elements, it will be invisible on a dark background, and vice versa. Consider supplying a white/inverted version for the dark key, or use an SVG logo that adapts via CSS currentColor.
| "pages": [ | ||
| "platforms/quadruped-go2", | ||
| "platforms/humanoid-g1" | ||
| ] |
There was a problem hiding this comment.
Inconsistent indentation inside the Platforms
pages array
platforms/quadruped-go2 is missing its leading spaces, making the array visually inconsistent and potentially confusing to future editors.
| "pages": [ | |
| "platforms/quadruped-go2", | |
| "platforms/humanoid-g1" | |
| ] | |
| "pages": [ | |
| "platforms/quadruped-go2", | |
| "platforms/humanoid-g1" | |
| ] |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
|
||
| <Columns cols={2}> | ||
| <Card title="Navigation & mapping" icon="map" href="/capabilities/navigation/overview"> | ||
| **SLAM**, dynamic obstacle avoidance, route planning, and autonomous exploration- via both DimOS native and ROS integrations. |
There was a problem hiding this comment.
Broken
/capabilities/navigation/overview and /capabilities/memory/overview links
Neither capabilities/navigation/overview.md nor capabilities/memory/overview.md exists in the repository. The actual navigation file lives at capabilities/navigation/readme.md (nav slug capabilities/navigation/readme) and the memory landing page is capabilities/memory/index.md (nav slug capabilities/memory/index). Both card hrefs will 404 immediately in the live docs.
| <Card title="Quickstart" icon="rocket" href="/quickstart"> | ||
| Install DimOS, run your first blueprint, and inspect the running system. | ||
| </Card> | ||
| <Card title="DimOS concepts" icon="diagram-project" href="/usage/concepts"> |
There was a problem hiding this comment.
| dimos run unitree-go2 | ||
| ``` | ||
|
|
||
| Do not skip the platform guide - latency, time sync, and safety habits matter: [Unitree Go2](/platforms/quadruped-go2). |
There was a problem hiding this comment.
/platforms/quadruped-go2 slug doesn't match the actual file path
The file lives at docs/platforms/quadruped/go2/index.md, which Mintlify serves at platforms/quadruped/go2/index. The slug /platforms/quadruped-go2 used here (and again in the CardGroup below) has no matching file, so both links will 404. The docs.json nav already uses the correct nested path.
| Do not skip the platform guide - latency, time sync, and safety habits matter: [Unitree Go2](/platforms/quadruped-go2). | |
| Do not skip the platform guide - latency, time sync, and safety habits matter: [Unitree Go2](/platforms/quadruped/go2/index). |
| <Card title="Capabilities" href="/capabilities/agents/readme" icon="bolt"> | ||
| Navigation, perception, spatial memory, and manipulation. | ||
| </Card> |
There was a problem hiding this comment.
The "Capabilities" card duplicates the same
href as the "Add an LLM agent" card directly above it — both point to /capabilities/agents/readme. The description ("Navigation, perception, spatial memory, and manipulation") clearly intends a broader capabilities landing page. Users clicking "Capabilities" will land on the Agents readme instead, which is confusing and makes one of the two cards redundant. A reasonable target would be /capabilities/navigation/readme (the first top-level capability page in the nav) or a dedicated capabilities overview if/when one is created.
| <Card title="Capabilities" href="/capabilities/agents/readme" icon="bolt"> | |
| Navigation, perception, spatial memory, and manipulation. | |
| </Card> | |
| <Card title="Capabilities" href="/capabilities/navigation/readme" icon="bolt"> | |
| Navigation, perception, spatial memory, and manipulation. | |
| </Card> |
Merge order: 1/3- This PR can be merged independently.
Problem
Docs folder has no Mintlify configuration and is missing logo, introduction and quickstart pages.
Solution
Added docs.json with Mintlify config (theme, colors, logo, sidebar) and full navigation structure accounting for upcoming docs restructuring.
Added Dimensional logo in assets folder for Mintlify light/dark theme.
Added introduction.mdx - overview of DimOS with capabilities at a glance.
Added quickstart.mdx - install instructions, replay/simulation/real robot setup, CLI and MCP usage, featured runfiles.
How to Test
Contributor License Agreement