Skip to content

fix(compose): serve the child pages, not the overview - #101

Merged
a-essawy merged 1 commit into
mainfrom
fix/compose-nav-index
Sep 24, 2026
Merged

a-essawy merged 1 commit into
mainfrom
fix/compose-nav-index

Conversation

@a-essawy

Copy link
Copy Markdown
Contributor

Every page under /docs/jobs/compose/ served the overview in production. The sitemap and llms.txt listed all 25, so the build saw them; the routes resolved to the parent. mint dev did not reproduce it.

Cause: jobs/compose.mdx sat beside the jobs/compose/ directory, and the group carried root: "jobs/compose". Every other section with children in this repo uses <dir>/index.mdx as the first page and no root — storage/index, automation/index — and both resolve their children correctly on the live site. Compose now matches them.

/docs/jobs/compose still serves the overview, so no inbound link moves: the changelog entries, the redirects and the apex all keep working.

Trade-off worth stating: root was what made clicking the Compose parent open the overview and hold the child highlight. Dropping it puts compose back to how Storage and Automation behave. A broken section beats a nav nicety, and a fix for the nav can come separately once it is tested against a real Mintlify build rather than mint dev.

Every page under /docs/jobs/compose/ served the overview in production. The
sitemap and llms.txt listed all 25, so the build saw them, but the routes
resolved to the parent. `mint dev` did not reproduce it.

`jobs/compose.mdx` sat beside the `jobs/compose/` directory and the group
carried `root: "jobs/compose"`. Every other section with children here uses
`<dir>/index.mdx` as its first page and no `root` (storage, automation), and
both resolve children correctly in production. Compose now matches.

`/docs/jobs/compose` still serves the overview, so no inbound link moves.
@a-essawy
a-essawy merged commit 1f3e987 into main Sep 24, 2026
1 check passed
@a-essawy
a-essawy deleted the fix/compose-nav-index branch September 24, 2026 13:42
a-essawy added a commit that referenced this pull request Sep 24, 2026
…103)

A generated table cell held `[{time:0,value:0},{time:1,value:1}]`; MDX reads a
bare `{...}` as a JSX expression, the page failed to parse, and Mintlify served
the section root as the body of all 24 child pages while reporting every deploy
a success. Generator fixed in rendobar/rendobar#798; these are the regenerated
pages.

Also reverts two changes I shipped on a wrong diagnosis: #101 (moving the
overview to index.mdx and dropping `root`, which cost the nav behaviour) and
#102 (a validator rule for a collision that was never the cause).

Adds `validate:build` = `mint validate`, the only check that sees a build
error, and the one that was missing.
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