Every documentation site requires a docs.json file that contains the core configuration settings. This file controls everything from styling and navigation to integrations and analytics.
If you’re currently using the legacy mint.json configuration file, please update the CLI:
npm i -g mintlify@latest
And run the new upgrade command in your docs repository:
mintlify upgrade
This will generate a docs.json based off of your mint.json. Then, please delete the mint.json file from your repository.

Properties

Customization

theme
"mint" | "maple" | "palm" | "willow" | "linden"
required
The layout theme of the project. Check out the Themes page for more information.
name
string
required
The name of the project, organization, or product Minimum length: 1
description
string
Optional description used for SEO and LLM indexing

Styling

colors
object
required
The colors to use in your documentation. At the very least, you must define the primary color. For example:
{
  "colors": {
    "primary": "#ff0000"
  }
}
The logo (for both light and dark mode)
favicon
string or object
The path to your favicon file in the docs folder, including the file extension. The file will automatically be resized to appropriate favicon sizes. Can be a single file or a pair for light and dark mode. Example: /favicon.png
styling
object
Styling configurations
icons
object
Icon library settings
fonts
object
appearance
object
Light / dark mode toggle settings
background
object
Background color and decoration settings

Structure

navbar
object
Navbar content and settings
navigation
object
required
The navigation structure of the content
Footer configurations
banner
object
Banner configurations
redirects
array of object
contextual
object

API Configurations

api
object
API reference configuration and playground settings
seo
object
SEO indexing configurations
Search display settings

Integrations

integrations
object
Configurations for official integrations

Errors

errors
object

Best Practices

When configuring your docs.json file, consider these best practices:
  1. Keep the configuration organized by grouping related settings together
  2. Use meaningful names for groups and pages in your navigation structure
  3. Provide complete paths for all assets (logos, favicons, etc.)
  4. Test your configuration in both light and dark modes
  5. Verify all external links and integrations are correctly configured
  6. Use appropriate color contrasts for accessibility
  7. Configure SEO settings for better search engine visibility

Validation

The docs.json file is validated against a JSON schema to ensure proper configuration. You can reference the schema by including:
{
  "$schema": "https://mintlify.com/docs.json"
}

mint.json (Legacy)