Navigation

Design information architecture that aligns with user needs.

The navigation property in docs.json controls the structure and information hierarchy of your documentation.

With proper navigation configuration, you can organize your content so that users can find exactly what they’re looking for.

Choose one primary organizational pattern at the root level of your navigation. Once you’ve chosen your primary pattern, you can nest other navigation elements within it.

Pages

Pages are the most fundamental navigation component. Each page is an MDX file in your documentation repository.

In the navigation object, pages is an array where each entry must reference the path to a page file.

{
  "navigation": {
    "pages": [
      "settings",
      "pages",
      "navigation",
      "themes",
      "custom-domain"
    ]
  }
}

Groups

Use groups to organize your sidebar navigation into sections. Groups can be nested within each other, labeled with tags, and styled with icons.

In the navigation object, groups is an array where each entry is an object that requires a group field and a pages field. The icon, tag, and expanded fields are optional.

{
  "navigation": {
    "groups": [
      {
        "group": "Getting started",
        "icon": "play",
        "pages": [
          "quickstart",
          {
            "group": "Editing",
            "expanded": false,
            "icon": "pencil",
            "pages": [
              "installation",
              "editor"
            ]
          }
        ]
      },
      {
        "group": "Writing content",
        "icon": "notebook-text",
        "tag": "NEW",
        "pages": [
          "writing-content/page",
          "writing-content/text"
        ]
      }
    ]
  }
}

Default expanded state

Use the expanded property to control the default state of a nested group in the navigation sidebar.

• expanded: true: Group is expanded by default.
• expanded: false or omitted: Group is collapsed by default.

The expanded property only affects nested groups—groups within groups. Top-level groups are always expanded and cannot be collapsed.

{
  "group": "Getting started",
  "pages": [
    "quickstart",
    {
      "group": "Advanced",
      "expanded": false,
      "pages": ["installation", "configuration"]
    }
  ]
}

Tags and labels

Use tags to highlight important navigation items and draw attention to new, updated, or deprecated content. Tags appear as small labels next to group names in the sidebar navigation.

Add a tag to any group by including the tag field in your navigation configuration. Tags work with all navigation elements that support groups, including tabs, anchors, dropdowns, and products.

{
  "navigation": {
    "groups": [
      {
        "group": "Getting started",
        "pages": ["quickstart", "installation"]
      },
      {
        "group": "New features",
        "tag": "NEW",
        "pages": ["features/ai-search", "features/analytics"]
      },
      {
        "group": "Beta features",
        "tag": "BETA",
        "pages": ["beta/webhooks", "beta/graphql"]
      },
      {
        "group": "Legacy API",
        "tag": "DEPRECATED",
        "pages": ["legacy/v1-endpoints"]
      }
    ]
  }
}

Common tag use cases

Use tags strategically to guide users through your documentation:

NEW - Highlight recently added features or documentation sections:

{
  "group": "AI capabilities",
  "tag": "NEW",
  "icon": "sparkles",
  "pages": ["ai/semantic-search", "ai/recommendations"]
}

BETA - Mark experimental or preview features:

{
  "group": "Experimental APIs",
  "tag": "BETA",
  "icon": "flask",
  "pages": ["experimental/streaming", "experimental/batch"]
}

DEPRECATED - Indicate legacy content users should migrate away from:

{
  "group": "Legacy authentication",
  "tag": "DEPRECATED",
  "icon": "triangle-exclamation",
  "pages": ["legacy/api-keys", "legacy/basic-auth"]
}

UPDATED - Show recently refreshed documentation:

{
  "group": "Security guide",
  "tag": "UPDATED",
  "icon": "shield",
  "pages": ["security/oauth", "security/permissions"]
}

PREVIEW - Indicate upcoming features available for early access:

{
  "group": "Preview features",
  "tag": "PREVIEW",
  "icon": "eye",
  "pages": ["preview/real-time-sync", "preview/webhooks-v2"]
}

Tags with nested groups

Tags work with nested groups, allowing you to mark specific subsections within your navigation hierarchy:

{
  "navigation": {
    "groups": [
      {
        "group": "API reference",
        "pages": [
          "api/overview",
          {
            "group": "REST endpoints",
            "pages": ["api/users", "api/projects"]
          },
          {
            "group": "GraphQL API",
            "tag": "NEW",
            "pages": ["api/graphql/queries", "api/graphql/mutations"]
          }
        ]
      }
    ]
  }
}

Tags in different navigation contexts

Tags can be applied to groups within any navigation element:

Tabs with tagged groups

{
  "navigation": {
    "tabs": [
      {
        "tab": "Documentation",
        "groups": [
          {
            "group": "Core concepts",
            "pages": ["concepts/auth", "concepts/data"]
          },
          {
            "group": "Advanced topics",
            "tag": "NEW",
            "pages": ["advanced/caching", "advanced/optimization"]
          }
        ]
      }
    ]
  }
}

Best practices for tags

Follow these guidelines to use tags effectively:

• Be consistent - Use the same tag text across your documentation (e.g., always use “NEW” rather than mixing “New”, “NEW”, and “Latest”)
• Keep tags short - Limit tags to 1-2 words for better readability
• Use sparingly - Too many tags reduce their effectiveness. Reserve tags for truly important items
• Update regularly - Remove “NEW” tags after content has been available for a while (typically 30-90 days)
• Combine with icons - Pair tags with relevant icons to create stronger visual cues
• Consider your audience - Use tags that match your users’ mental models (e.g., “PREVIEW” for early-access features)

Styling considerations

Tags inherit your documentation’s primary color scheme by default. The tag appearance automatically adapts to light and dark modes based on your theme configuration.

For consistent visual hierarchy:

• Tags appear to the right of group names in the sidebar
• Tag text is automatically capitalized and styled for emphasis
• Tags maintain proper spacing and alignment with navigation items
• Multiple tags on the same level create a clear visual pattern

Tabs

Tabs create distinct sections of your documentation with separate URL paths. Tabs create a horizontal navigation bar at the top of your documentation that lets users switch between sections.

In the navigation object, tabs is an array where each entry is an object that requires a tab field and can contain other navigation fields such as groups, pages, icons, or links to external pages.

{
  "navigation": {
    "tabs": [
      {
        "tab": "API reference",
        "icon": "square-terminal",
        "pages": [
          "api-reference/get",
          "api-reference/post",
          "api-reference/delete"
        ]
      },
      {
        "tab": "SDKs",
        "icon": "code",
        "pages": [
          "sdk/fetch",
          "sdk/create",
          "sdk/delete"
        ]
      },
      {
        "tab": "Blog",
        "icon": "newspaper",
        "href": "https://external-link.com/blog"
      }
    ]
  }
}

Menus

Menus add dropdown navigation items to a tab. Use menus to help users go directly to specific pages within a tab.

In the navigation object, menu is an array where each entry is an object that requires an item field and can contain other navigation fields such as groups, pages, icons, or links to external pages.

Menu items can only contain groups, pages, and external links.

{
  "navigation": {
    "tabs": [
      {
        "tab": "Developer tools",
        "icon": "square-terminal",
        "menu": [
          {
            "item": "API reference",
            "icon": "rocket",
            "groups": [
              {
                "group": "Core endpoints",
                "icon": "square-terminal",
                "pages": [
                  "api-reference/get",
                  "api-reference/post",
                  "api-reference/delete"
                ]
              }
            ]
          },
          {
            "item": "SDKs",
            "icon": "code",
            "description": "SDKs are used to interact with the API.",
            "pages": [
              "sdk/fetch",
              "sdk/create",
              "sdk/delete"
            ]
          }
        ]
      }
    ]
  }
}

Anchors

Anchors add persistent navigation items to the top of your sidebar. Use anchors to section your content, provide quick access to external resources, or create prominent calls to action.

In the navigation object, anchors is an array where each entry is an object that requires an anchor field and can contain other navigation fields such as groups, pages, icons, or links to external pages.

{
  "navigation": {
    "anchors": [
      {
        "anchor": "Documentation",
        "icon": "book-open",
        "pages": [
          "quickstart",
          "development",
          "navigation"
        ]
      },
      {
        "anchor": "API reference",
        "icon": "square-terminal",
        "pages": [
          "api-reference/get",
          "api-reference/post",
          "api-reference/delete"
        ]
      },
      {
        "anchor": "Blog",
        "href": "https://external-link.com/blog"
      }
    ]
  }
}

Global anchors

Use global anchors for external links that should appear on all pages, regardless of which section of your navigation the user is viewing. Global anchors are particularly useful for linking to resources outside your documentation, such as a blog, community forum, or support portal.

Global anchors must include an href field pointing to an external URL. They cannot contain relative paths.

{
  "navigation": {
    "global":  {
      "anchors": [
        {
          "anchor": "Community",
          "icon": "house",
          "href": "https://slack.com"
        },
        {
          "anchor": "Blog",
          "icon": "pencil",
          "href": "https://mintlify.com/blog"
        }
      ]
    },
    "tabs": /*...*/
  }
}

Dropdowns

Dropdowns are contained in an expandable menu at the top of your sidebar navigation. Each item in a dropdown directs to a section of your documentation.

In the navigation object, dropdowns is an array where each entry is an object that requires a dropdown field and can contain other navigation fields such as groups, pages, icons, or links to external pages.

{
  "navigation": {
    "dropdowns": [
      {
        "dropdown": "Documentation",
        "icon": "book-open",
        "pages": [
          "quickstart",
          "development",
          "navigation"
        ]
      },
      {
        "dropdown": "API reference",
        "icon": "square-terminal",
        "pages": [
          "api-reference/get",
          "api-reference/post",
          "api-reference/delete"
        ]
      },
      {
        "dropdown": "Blog",
        "href": "https://external-link.com/blog"
      }
    ]
  }
}

Products

Products create a dedicated navigation division for organizing product-specific documentation. Use products to separate different offerings, services, or major feature sets within your documentation.

In the navigation object, products is an array where each entry is an object that requires a product field and can contain other navigation fields such as groups, pages, icons, or links to external pages.

{
  "navigation": {
    "products": [
      {
        "product": "Core API",
        "description": "Core API description",    
        "icon": "api",
        "groups": [
          {
            "group": "Getting started",
            "pages": [
              "core-api/quickstart",
              "core-api/authentication"
            ]
          },
          {
            "group": "Endpoints",
            "pages": [
              "core-api/users",
              "core-api/orders"
            ]
          }
        ]
      },
      {
        "product": "Analytics Platform",
        "description": "Analytics Platform description",
        "icon": "chart-bar",
        "pages": [
          "analytics/overview",
          "analytics/dashboard",
          "analytics/reports"
        ]
      },
      {
        "product": "Mobile SDK",
        "description": "Mobile SDK description",
        "icon": "smartphone",
        "href": "https://mobile-sdk-docs.example.com"
      }
    ]
  }
}

OpenAPI

Integrate OpenAPI specifications directly into your navigation structure to automatically generate API documentation. Create dedicated API sections or place endpoint pages within other navigation components.

Set a default OpenAPI specification at any level of your navigation hierarchy. Child elements will inherit this specification unless they define their own specification.

When you add the openapi property to a navigation element (such as an anchor, tab, or group) without specifying any pages, Mintlify automatically generates pages for all endpoints defined in your OpenAPI specification.

To control which endpoints appear, explicitly list the desired endpoints in a pages array.

For more information about referencing OpenAPI endpoints in your docs, see the OpenAPI setup.

{
  "navigation": {
    "groups": [
      {
        "group": "API reference",
        "openapi": "/path/to/openapi-v1.json",
        "pages": [
          "overview",
          "authentication",
          "GET /users",
          "POST /users",
          {
            "group": "Products",
            "openapi": "/path/to/openapi-v2.json",
            "pages": [
              "GET /products",
              "POST /products"
            ]
          }
        ]
      }
    ]
  }
}

Versions

Partition your navigation into different versions. Versions are selectable from a dropdown menu.

In the navigation object, versions is an array where each entry is an object that requires a version field and can contain any other navigation fields.

{
  "navigation": {
    "versions": [
      {
        "version": "1.0.0",
        "groups": [
          {
            "group": "Getting started",
            "pages": ["v1/overview", "v1/quickstart", "v1/development"]
          }
        ]
      },
      {
        "version": "2.0.0",
        "groups": [
          {
            "group": "Getting started",
            "pages": ["v2/overview", "v2/quickstart", "v2/development"]
          }
        ]
      }
    ]
  }
}

Languages

Partition your navigation into different languages. Languages are selectable from a dropdown menu.

In the navigation object, languages is an array where each entry is an object that requires a language field and can contain any other navigation fields, including language-specific banner configurations.

We currently support the following languages for localization:

Arabic (ar)

Czech (cs)

Chinese (cn)

Chinese (zh-Hant)

Dutch (nl)

English (en)

French (fr)

German (de)

Hebrew (he)

Hindi (hi)

Indonesian (id)

Italian (it)

Japanese (jp)

Korean (ko)

Latvian (lv)

Norwegian (no)

Polish (pl)

Portuguese (pt-BR)

Romanian (ro)

Russian (ru)

Spanish (es)

Swedish (sv)

Turkish (tr)

Ukrainian (ua)

Uzbek (uz)

Vietnamese (vi)

{
  "navigation": {
    "languages": [
      {
        "language": "en",
        "banner": {
          "content": "🚀 Version 2.0 is now live! See our [changelog](/en/changelog) for details.",
          "dismissible": true
        },
        "groups": [
          {
            "group": "Getting started",
            "pages": ["en/overview", "en/quickstart", "en/development"]
          }
        ]
      },
      {
        "language": "es",
        "banner": {
          "content": "🚀 ¡La versión 2.0 ya está disponible! Consulta nuestro [registro de cambios](/es/changelog).",
          "dismissible": true
        },
        "groups": [
          {
            "group": "Getting started",
            "pages": ["es/overview", "es/quickstart", "es/development"]
          }
        ]
      }
    ]
  }
}

For automated translations, contact our sales team to discuss solutions.

Nesting

Navigation elements can be nested within each other to create complex hierarchies. You must have one root-level parent navigation element such as tabs, groups, or a dropdown. You can nest other types of navigation elements within your primary navigation pattern.

Each navigation element can contain one type of child element at each level of your navigation hierarchy. For example, a tab can contain anchors that contain groups, but a tab cannot contain both anchors and groups at the same level.

Tabs containing anchors

{
  "navigation": {
    "tabs": [
      {
        "tab": "Documentation",
        "anchors": [
          {
            "anchor": "Guides",
            "icon": "book-open",
            "pages": ["quickstart", "tutorial"]
          },
          {
            "anchor": "API Reference",
            "icon": "code",
            "pages": ["api/overview", "api/endpoints"]
          }
        ]
      },
      {
        "tab": "Resources",
        "groups": [
          {
            "group": "Help",
            "pages": ["support", "faq"]
          }
        ]
      }
    ]
  }
}

Breadcrumbs

Breadcrumbs display the full navigation path at the top of pages. Some themes have breadcrumbs enabled by default and others do not. You can control whether breadcrumbs are enabled for your site using the styling property in your docs.json.

Display full breadcrumbs

"styling": {
  "eyebrows": "breadcrumbs"
}

Interaction configuration

Control how users interact with navigation elements using the interaction property in your docs.json.

Enable auto-navigation for groups

When a user expands a navigation group, some themes will automatically navigate to the first page in the group. You can override a theme’s default behavior using the drilldown option.

• Set to true to force automatic navigation to the first page when a navigation group is selected.
• Set to false to prevent navigation and only expand or collapse the group when it is selected.
• Leave unset to use the theme’s default behavior.

Force navigation

"interaction": {
  "drilldown": true  // Force navigation to first page when a user expands a dropdown
}