mintlify

You can build a documentation site by authoring MDX content and converting it into structured pages using Mintlify. This approach centralizes navigation configuration and site maintenance directly within a Git-based workflow.

The best way to configure site-wide documentation settings is through the docs.json schema. This file centralizes navigation, frontmatter-driven page settings, and built-in component configurations across your entire project.

You can add an API reference and custom components by utilizing optional assets and built-in components within your MDX files. This extends your documentation to support interactive API endpoints alongside standard pages.

Yes, Mintlify is designed specifically for a Git-based workflow, allowing teams to consistently create, organize, and maintain comprehensive documentation while reducing ambiguity and rework through reusable patterns.

You need frontmatter-driven pages when you want to apply consistent metadata and structure across multiple MDX documents. This ensures standardized navigation and page configuration within your Mintlify site.

Your MDX documentation site needs a docs.json configuration file to define site-wide settings and the navigation schema. It serves as the central source of truth for structuring and organizing your documentation pages.