Global Settings
Configure your documentation using the docs.json
file
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:
And run the new upgrade
command in your docs repository:
This will generate a docs.json
based off of your mint.json
. Then, please delete the mint.json
file from your repository.
Properties
Customization
The layout theme of the project. Check out the Themes page for more information.
The name of the project, organization, or product Minimum length: 1
Optional description used for SEO and LLM indexing
Styling
The colors to use in your documentation. At the very least, you must define the primary color. For example:
The logo (for both light and dark mode)
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 configurations
Icon library settings
Light / dark mode toggle settings
Background color and decoration settings
Structure
Navbar content and settings
The navigation structure of the content
Footer configurations
Banner configurations
API Configurations
API reference configuration and playground settings
SEO & Search
SEO indexing configurations
Search display settings
Integrations
Configurations for official integrations
Errors
Best Practices
When configuring your docs.json
file, consider these best practices:
- Keep the configuration organized by grouping related settings together
- Use meaningful names for groups and pages in your navigation structure
- Provide complete paths for all assets (logos, favicons, etc.)
- Test your configuration in both light and dark modes
- Verify all external links and integrations are correctly configured
- Use appropriate color contrasts for accessibility
- 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:
mint.json
(Legacy)
Documentation for the legacy `mint.json` config file
Documentation for the legacy `mint.json` config file
Every Mintlify site needs a mint.json
file with the core configuration
settings. Learn more about the properties or from an
example
Properties
Styling
Name of your company or project. Used for the global title.
Path to logo image or object with path to “light” and “dark” mode logo images, and where the logo links to. SVG format is recommended. It does not pixelate and the file size is generally smaller.
Path to the favicon image. For example: /path/to/favicon.svg
Hex color codes for your global theme
The global layout style of the documentation.
Set a decorative background.
Set a custom background image to be displayed behind every page.
Custom fonts. Apply globally or set different fonts for headings and the body text.
Example:
Customize the dark mode toggle.
Customize the styling of components within the sidebar.
Styling configurations for the topbar.
The location options for the search bar.
The style of the rounded edges.
The style of the code block.
Structure
An array of groups with all the pages within that group
Array of names and urls of links you want to include in the topbar
Array of version names. Only use this if you want to show different versions of docs with a dropdown in the navigation bar.
Versions can be leveraged for localization. You can store translated content
under a version, and once you specify the locale
any fixed text in Mintlify,
such as ‘Was this page helpful?’, will automatically be translated based on the
locale. We currently support localization in English, Chinese, Spanish, French,
Japanese, and Portuguese.
Localization auto-translates the UI and fixed assets in the docs, such as “Was this page helpful?”. You must translate the content of the pages yourself.
For more information, please refer to our versioning & localization documentation.
Example:
An array of the anchors, includes the icon, color, and url.
Override the default configurations for the top-most anchor. Note: if you have tabs configured, this does not apply.
An array of navigational tabs.
Example:
An object to configure the footer with socials and links. Example:
Configurations to enable feedback buttons
Configurations to change the search prompt
API Configurations
Configuration for API settings. Learn more about API pages at API Components.
A string or an array of strings of URL(s) or relative path(s) pointing to your OpenAPI file.
Examples:
Integrations
Configurations to add third-party integrations (excluding analytics integrations)
Configurations to add third-party analytics integrations. See full list of supported analytics here.
Redirects
An array of paths you want to configure to permanently redirect to another path
Example:
Search Engine Optimization
Settings for Search Engine Optimization.
Example:
Example mint.json
Click on the following dropdown to view a sample configuration file
View Example Configuration
View Example Configuration