docs.json is picked up as-is, and mint.json projects are converted automatically (navigation, tabs, anchors, topbar links, CTA button, footer socials, and the mode toggle all map over).
This page lists the differences so you can audit a migration quickly.
Fully supported
docs.jsonand legacymint.json, including$refresolution inside the config.- Navigation:
groups,tabs,anchors,dropdowns,products,versions,languages,menu, nested groups,hidden,expanded,icon,tag,root, external links, and global anchors. Version and language content stays in its own selector scope. - Page frontmatter:
title,sidebarTitle,description,icon,tag,mode(default,frame,custom,center,wide),hidden,noindex,canonical,keywords,related, and more. See Frontmatter. - The component library: callouts, Cards, Tabs, Steps, Accordions, CodeGroup, Frame, ParamField/ResponseField, Update, Tree/FileTree, and others. See Components.
- Snippets (
<Snippet file="…" />and MDX imports),{{variable}}substitution, custom.jsxcomponents. - Code blocks: titles, icons, line highlighting and focus, diff markers, line numbers, wrap, expandable. Mermaid diagrams and LaTeX math also work.
- OpenAPI reference pages and the interactive API playground in all the usual declaration styles. See API references.
- Redirects (
redirectsindocs.json),seo.metatags, custom fonts, themes, banners, custom CSS files.
Differences to know about
Unknown
docs.json keys and unknown MDX components never fail a build: unrecognized config is ignored, and unrecognized components render as inert placeholders and are listed as build warnings.
Redirects without the rule cap
Docs7 ships redirects as code inside the site worker rather than Cloudflare’s static_redirects table, so there is no 2,000-rule cap. Projects with tens of thousands of redirect rules deploy fine. See Redirects.