New releases and improvements
https://yourdomain.com/docs
, authentication now works seamlessly<h1-6>
tag conversion issue that was incorrectly transforming them into Heading components and disrupting custom stylingnavigation
data in each page’s rsc
payload—performance gains most noticeable with high page counts or complex navigation structureswebhook
pages in docs navigation from OpenAPI specs/
to prevent navigation breakageCtrl+K
link shortcut in monorepo dashboard Editor that was prepending docs repo path and creating broken linksllms.txt
and llms-full.txt
support—add to docs repo root to serve at /llms.txt
and /llms-full.txt
endpoints for LLM customizationllms.txt
and llms-full.txt
to ensure correct servingh{1-4}
tags for applying custom heading stylesh{1-4}
tags rendering as Heading
components with chips in custom page modeVSCode
to VS Code
in contextual menu when enabledCannot convert undefined or null to object
when encountering empty OpenAPI JSON filesdocs.json
open-graph metatags being overwritten by generated onesdocs.json
so you don’t need public: true
on each page (learn more)logoutURL
in OAuth configuration to delete upstream cookies and complete sign-outlogoutURL
to restart the auth flowhttps://
from URLs in OAuth/JWT auth configuration to prevent misconfigurationopenapi
and asyncapi
files are now served at their specified paths (e.g. https://mydocsurl.extension/{openapi-or-file-name}.json
)x-mint
field in your openapi files to override generated fields, customize preface content, or change endpoint URLs in code samplesx-mcp
is now x-mint.mcp
in OpenAPI configurations to control which routes are exposed as MCP tools/mcp/...
pages after the hosted MCP servers release from last week/assets/marketing/my-logo.png
in your repo, it will be available at https://mydocsurl.extension/assets/marketing/my-logo.png
.type
in navigator.write
contentDirectory
files are missingmultipart/form-data
file upload functionality in the API playground#ask-ai
channelmint update
mint update
to update your CLI.docs.json
docs.json
schema as a replacement for mint.json
, to support better multi-level versioning, easier visual comprehension, and more consistent terminology. For more information on what’s changed, check out our blog.Upgrade from mint.json
to docs.json
with the following steps:mint.json
file and push your changes.md
to the URL. This makes it easier for LLMs to ingest individual pages from your documentation.docs.json
file editinglocale
to a version and fixed content in Mintlify like “Was this page helpful?” will also match the locale.{}
and specify line numbers or ranges separated by commas.docs.json
:suggestEdit
not showing up even when enabled.img
property to a card to display an image on the top of the card. Learn more about it here.sidenav
.disableProxy
to disable this behavior and support request types like file
uploads.Pro
users, we introduced Mintlify Widget, an extension of your docs to
answer your users’ questions when and where they asked. You can add this
AI-powered chatbot to any web page: your landing page, inside your product, or
on your existing documentation pages.docs.json
file and it’ll update your docs styling.openapi
field to an object in tabs or anchors arrays in the docs.json
.