Skip to content

docs: align Mintlify navigation with index.md pages and front matter#2560

Open
swstica wants to merge 5 commits into
mainfrom
swastika/fix/mint-pages-format
Open

docs: align Mintlify navigation with index.md pages and front matter#2560
swstica wants to merge 5 commits into
mainfrom
swastika/fix/mint-pages-format

Conversation

@swstica

@swstica swstica commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Problem

  1. Mintlify was rendering duplicate headings and failing to parse README.md / readme.md pages. instead of Mintlify’s index.md convention.
  2. docs.json was out of date: broken agents/ paths (folder is coding-agents/), missing overview pages for Usage/Capabilities sections, and several existing docs not listed in the sidebar causing missing/broken nav entries.

Solution

  1. Renamed readme.md pages to index.md. This change occurs for GH preview as well but we don't have any option if we want to keep same docs for GH and mintlify.
  2. Added Mintlify front matter title: xyz across 52 docs pages. Mintlify takes file name as default title if not mentioned. eg: it will take 'index' as a page name for 'index.md' file, which would be confusing.
  3. Update docs.json for nav.

How to Test

cd docs && npx mint dev

Contributor License Agreement

  • I have read and approved the CLA.

@greptile-apps

greptile-apps Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR renames all readme.md/README.md files under docs/ to index.md, adds Mintlify title: frontmatter to 52 documentation pages, and updates docs.json to fix the broken agents/coding-agents/ path prefix, add newly-renamed index pages to navigation, and register several previously-unlisted pages.

  • Frontmatter title: fields were added across 52 files so Mintlify uses human-readable titles instead of bare filenames (especially important for index.md pages where the default would show "index" in the sidebar).
  • docs.json navigation was corrected: the agents/ path prefix was fixed to coding-agents/, new overview pages (usage/index, data_streams/index, sensor_streams/index, capabilities/agents/index, capabilities/perception/index, capabilities/manipulation/index) were added, and new pages (coding-agents/worktrees, development/releasing) were added to their respective groups.

Confidence Score: 4/5

Safe to merge for the navigation and frontmatter fixes; existing broken links in the new index pages (flagged in earlier review rounds) still need a follow-up.

The coding-agents path fix, readme→index renames, and frontmatter additions all look correct. Two nav entries (coding-agents/worktrees and development/releasing) were added to docs.json without receiving the same frontmatter treatment as the rest of the PR, so Mintlify will derive their sidebar labels from the raw filenames. The broken internal-link format in usage/index.md, data_streams/index.md, and sensor_streams/index.md was already noted in earlier review rounds and remains unresolved.

docs/coding-agents/worktrees.md and docs/development/releasing.md — both newly exposed in the sidebar but missing title frontmatter. The three index files under docs/usage/ that carry broken Mintlify-incompatible link paths.

Important Files Changed

Filename Overview
docs/docs.json Navigation updated: fixes broken coding-agents paths, adds missing index pages and new entries (worktrees, releasing). Two newly-added nav entries (coding-agents/worktrees, development/releasing) reference files that lack title frontmatter, unlike all other files touched by this PR.
docs/usage/index.md New index page with title frontmatter added, but all internal links use the /docs/usage/…filename.md format which produces 404s in Mintlify (already flagged in previous review thread).
docs/usage/data_streams/index.md README.md renamed to index.md with title frontmatter added; internal guide links use the wrong /docs/usage/… path format (already flagged in previous review thread).
docs/usage/sensor_streams/index.md README.md renamed to index.md with title frontmatter added; internal guide links use the wrong /docs/usage/… path format (already flagged in previous review thread).
docs/capabilities/agents/index.md readme.md renamed to index.md, title frontmatter added, correctly added to docs.json under capabilities/agents/index.
docs/capabilities/perception/index.md readme.md deleted, new index.md created with title frontmatter, correctly referenced in docs.json navigation.
experimental/docs/cmu_nav.md Title frontmatter added to replace bare H1; file is intentionally not listed in docs.json (hidden page in experimental/) which is acceptable Mintlify behavior.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[readme.md / README.md files] -->|renamed to| B[index.md files]
    B -->|frontmatter added| C[title: in frontmatter]
    C -->|registered in| D[docs.json navigation]

    E[agents/ paths in docs.json] -->|fixed to| F[coding-agents/ paths]
    F --> D

    G[New pages added to nav] --> D
    G --> G1[usage/index]
    G --> G2[data_streams/index]
    G --> G3[sensor_streams/index]
    G --> G4[capabilities/agents/index]
    G --> G5[capabilities/perception/index]
    G --> G6[coding-agents/worktrees no frontmatter]
    G --> G7[development/releasing no frontmatter]

    D -->|renders| H[Mintlify sidebar with correct titles]
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[readme.md / README.md files] -->|renamed to| B[index.md files]
    B -->|frontmatter added| C[title: in frontmatter]
    C -->|registered in| D[docs.json navigation]

    E[agents/ paths in docs.json] -->|fixed to| F[coding-agents/ paths]
    F --> D

    G[New pages added to nav] --> D
    G --> G1[usage/index]
    G --> G2[data_streams/index]
    G --> G3[sensor_streams/index]
    G --> G4[capabilities/agents/index]
    G --> G5[capabilities/perception/index]
    G --> G6[coding-agents/worktrees no frontmatter]
    G --> G7[development/releasing no frontmatter]

    D -->|renders| H[Mintlify sidebar with correct titles]
Loading

Reviews (7): Last reviewed commit: "Merge branch 'main' into swastika/fix/mi..." | Re-trigger Greptile

Co-authored-by: Cursor <cursoragent@cursor.com>
@swstica swstica force-pushed the swastika/fix/mint-pages-format branch from add1470 to 40ec0b6 Compare June 23, 2026 02:49
Comment thread docs/usage/index.md
Comment on lines 9 to 13
- [Modules](/docs/usage/modules.md): The primary units of deployment in DimOS, modules run in parallel and are python classes.
- [Streams](/docs/usage/sensor_streams/README.md): How modules communicate, a Pub / Sub system.
- [Streams](/docs/usage/sensor_streams/index.md): How modules communicate, a Pub / Sub system.
- [Blueprints](/docs/usage/blueprints.md): a way to group modules together and define their connections to each other.
- [RPC](/docs/usage/blueprints.md#calling-the-methods-of-other-modules): how one module can call a method on another module (arguments get serialized to JSON-like binary data).
- [Skills](/docs/usage/blueprints.md#defining-skills): An RPC function, except it can be called by an AI agent (a tool for an AI).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 partner All links in this new index page also use the /docs/usage/…filename.md pattern, which will resolve to docs/docs/usage/… in Mintlify and produce 404s. The .md extension and the /docs/ prefix both need to be removed. The blueprints.md page is also not listed in docs.json navigation — linking to it is fine (Mintlify will serve hidden pages by URL), but it won't appear in the sidebar.

Suggested change
- [Modules](/docs/usage/modules.md): The primary units of deployment in DimOS, modules run in parallel and are python classes.
- [Streams](/docs/usage/sensor_streams/README.md): How modules communicate, a Pub / Sub system.
- [Streams](/docs/usage/sensor_streams/index.md): How modules communicate, a Pub / Sub system.
- [Blueprints](/docs/usage/blueprints.md): a way to group modules together and define their connections to each other.
- [RPC](/docs/usage/blueprints.md#calling-the-methods-of-other-modules): how one module can call a method on another module (arguments get serialized to JSON-like binary data).
- [Skills](/docs/usage/blueprints.md#defining-skills): An RPC function, except it can be called by an AI agent (a tool for an AI).
- [Modules](/usage/modules): The primary units of deployment in DimOS, modules run in parallel and are python classes.
- [Streams](/usage/sensor_streams/index): How modules communicate, a Pub / Sub system.
- [Blueprints](/usage/blueprints): a way to group modules together and define their connections to each other.
- [RPC](/usage/blueprints#calling-the-methods-of-other-modules): how one module can call a method on another module (arguments get serialized to JSON-like binary data).
- [Skills](/usage/blueprints#defining-skills): An RPC function, except it can be called by an AI agent (a tool for an AI).

@codecov

codecov Bot commented Jun 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

@@           Coverage Diff            @@
##             main    #2560    +/-   ##
========================================
  Coverage   71.34%   71.34%            
========================================
  Files         891      891            
  Lines       80517    80517            
  Branches     7323     7462   +139     
========================================
+ Hits        57443    57446     +3     
+ Misses      21144    21142     -2     
+ Partials     1930     1929     -1     
Flag Coverage Δ
OS-ubuntu-24.04-arm 63.82% <ø> (ø)
OS-ubuntu-latest 66.52% <ø> (ø)
Py-3.10 66.51% <ø> (ø)
Py-3.11 66.50% <ø> (-0.01%) ⬇️
Py-3.12 66.51% <ø> (-0.01%) ⬇️
Py-3.13 66.52% <ø> (+<0.01%) ⬆️
Py-3.14 66.52% <ø> (+<0.01%) ⬆️
Py-3.14t 66.52% <ø> (+<0.01%) ⬆️
SelfHosted-Large 29.96% <ø> (+0.02%) ⬆️
SelfHosted-Linux 37.30% <ø> (-0.01%) ⬇️
SelfHosted-macOS 36.15% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 3 files with indirect coverage changes

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions github-actions Bot added the ready-to-merge Required CI checks have passed on this PR label Jun 23, 2026
@mintlify

mintlify Bot commented Jun 30, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
dimensional 🟢 Ready View Preview Jun 30, 2026, 7:35 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@github-actions github-actions Bot removed the ready-to-merge Required CI checks have passed on this PR label Jun 30, 2026
@github-actions github-actions Bot added the ready-to-merge Required CI checks have passed on this PR label Jun 30, 2026
@swstica swstica added the backport:skip Skip creating a backport to any release branches label Jul 1, 2026
@github-actions github-actions Bot added ready-to-merge Required CI checks have passed on this PR and removed ready-to-merge Required CI checks have passed on this PR labels Jul 1, 2026
@spomichter

Copy link
Copy Markdown
Contributor

@greptile quick check

Comment thread docs/docs.json
Comment on lines +103 to +107
"group": "Agents",
"pages": [
"capabilities/agents/index"
]
},

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 partner Mapping group points to a non-existent file

The new "Mapping" group references "capabilities/mapping/relocalization", but no file at docs/capabilities/mapping/relocalization.md exists in the repository. The capabilities/mapping/ directory itself doesn't exist. Mintlify will render a broken sidebar entry and a 404 page. The relocalization content already lives at capabilities/navigation/relocalization.md, which is listed under the "Navigation" group — this entry may be a mistaken duplicate of that path.

@github-actions github-actions Bot removed the ready-to-merge Required CI checks have passed on this PR label Jul 1, 2026
@github-actions github-actions Bot added the ready-to-merge Required CI checks have passed on this PR label Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip Skip creating a backport to any release branches ready-to-merge Required CI checks have passed on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants