Mintlify Directory
This directory contains the documentation frontend powered by Mintlify. It renders the OpenAPI specification fromSpec/ into a user-facing API reference website.
Layout
docs.json— Mintlify site configuration (navigation, theme, metadata)api-reference/— Bundled OpenAPI spec consumed by Mintlify (bundled.yaml)*.mdx(at this directory’s root) — Custom documentation pages. Each file maps 1:1 to a URL (getting-started.mdx→/getting-started).icons/— Custom icon assetsscripts/— Post-bundle transforms (see below)Dockerfile— Container setup for the documentation site
Key Files
api-reference/bundled.yaml— The bundled OpenAPI spec; regenerate withnpm run bundlefrom the repo root*.mdx— Additional hand-written documentation pages beyond the auto-generated API reference
Workflow
- Edit the source specification in
Spec/ - Run
npm run bundleto produce the bundled spec - The bundled output lands in
api-reference/bundled.yamland Mintlify renders it
Post-bundle transforms
Spec/’s npm run bundle runs redocly bundle and then chains node ../Mintlify/scripts/apply-coming-soon.js bundled.yaml.
scripts/apply-tag-hierarchy.js— reads the OpenAPI 3.2 tag hierarchy (kind: navsections +parent:on endpoint tags), rewrites theAPI Documentationgroup indocs.jsoninto one nested group per section, then downgrades the bundle to 3.1 and strips the section tags and theparent/kind/summaryfields — Mintlify supports 3.0/3.1 only and rejects those fields. It also badges any group whose operations are allx-newwithtag: "NEW", which is why it runs beforeapply-new.js(that script strips the flags). Delete this script when Mintlify supports 3.2; the spec is already correct.scripts/apply-coming-soon.js— for every operation flaggedx-coming-soon: <timing>inSpec/paths/, prepends a Mintlify<Warning>callout to the operationdescriptionand strips the flag from the bundled output. The flag value is the release-timing phrase, interpolated into the banner sentence. Delete the script and the flags wholesale at GA.