Skip to main content
The docs.json file lets you turn a collection of Markdown files into a navigable, customized documentation site. This required configuration file controls styling, navigation, integrations, and more. Think of it as the blueprint for your documentation. Settings in docs.json apply globally to all pages.

Setting up your docs.json

To get started, you only need to specify theme, name, colors.primary, and navigation. Other fields are optional and you can add them as your documentation needs grow. For the best editing experience, include the schema reference at the top of your docs.json file. This enables autocomplete, validation, and helpful tooltips in most code editors:

Reference

This section contains the full reference for the docs.json file.

Customization

required
The layout theme of your site.One of the following: mint, maple, palm, willow, linden, almond, aspen.See Themes for more information.
string
required
The name of your project, organization, or product.
object
required
The colors used in your documentation. Colors are applied differently across themes. If you only provide a primary color, it will be used for all color elements.
string
Description of your site for SEO and AI indexing.
Your logo for both light and dark mode.
string or object
Path to your favicon file, including the file extension. Automatically resized to appropriate favicon sizes. Can be a single file or separate files for light and dark mode. Example: /favicon.png
object
Thumbnail customization for social media and page previews.
object
Visual styling configurations.
object
Icon library settings.
object
Font configuration for your documentation. The default font is Inter.
object
Light/dark mode toggle settings.
object
Background color and decoration settings.

Structure

object
Navigation bar items to external links.
object
required
The navigation structure of your content.
object
User interaction settings for navigation elements.
Footer content and social media links.
object
Site-wide banner displayed at the top of pages.
array of object
Redirects for moved, renamed, or deleted pages.
object
Contextual menu for AI-optimized content and integrations.

API Configurations

object
API documentation and interactive playground settings.
object
SEO indexing configurations.
Search display settings.

Integrations

object
Third-party integrations.

Errors

object
Error handling settings.

Examples

docs.json

Upgrading from mint.json

If your docs project uses the deprecated mint.json file, follow these steps to upgrade to docs.json.
1

Install or update the CLI

If you haven’t installed the CLI, install it now:
If you already have the CLI installed, make sure it is up to date:
2

Create your docs.json file

In your docs repository, run:
This command will create a docs.json file from your existing mint.json. Review the generated file to ensure all settings are correct.
3

Delete your mint.json file

After verifying your docs.json is configured properly, you can safely delete your old mint.json file.