> ## Documentation Index
> Fetch the complete documentation index at: https://dotnetdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Documentation Collections
> Learn how the Mintlify provider intelligently restructures combined documentation for seamless multi-project experiences
When combining multiple documentation projects into a unified site, the Mintlify provider goes beyond simple file copying. It automatically restructures
content, relocates shared resources, and rewrites internal paths to ensure everything works seamlessly together.
## The Challenge
Documentation projects (especially Mintlify-targeted ones) are typically designed as standalone sites. They reference images, snippets, and internal pages
using absolute paths like `/images/logo.png` or `/guides/quickstart`. When you combine multiple projects, these paths collide:
```plaintext Without intelligent handling theme={"dark"}
/images/logo.png <- Which project's logo?
/snippets/Hero.jsx <- Which project's component?
/guides/quickstart <- Which project's guide?
```
## How Mintlify Collections Work
The `MintlifyDocReferenceHandler` solves this by performing three key operations during the build process:
Shared resource directories (`images/`, `snippets/`) are moved to central locations with project-specific namespacing:
```plaintext theme={"dark"}
/images/{DestinationPath}/logo.png
/snippets/{DestinationPath}/Hero.jsx
```
All absolute paths in MDX files are automatically rewritten to reference the relocated resources and prefixed pages:
| Original Path | Rewritten Path |
| -------------------- | ------------------------------ |
| `/images/logo.png` | `/images/product-1/logo.png` |
| `/snippets/Hero.jsx` | `/snippets/product-1/Hero.jsx` |
| `/guides/quickstart` | `/product-1/guides/quickstart` |
The referenced project's navigation is merged into the parent's `docs.json`, appearing as a Tab or Product based on your configuration.
## Supported Path Patterns
The handler rewrites paths in all common MDX patterns:
```jsx theme={"dark"}
// Before
import { Hero } from '/snippets/Hero.jsx';
// After
import { Hero } from '/snippets/product-1/Hero.jsx';
```
```markdown theme={"dark"}
// Before
[Getting Started](/guides/quickstart)
// After
[Getting Started](/product-1/guides/quickstart)
```
```jsx theme={"dark"}
// Before
// After
```
```jsx theme={"dark"}
// Before
// After
```
Paths inside fenced code blocks are **not** rewritten, ensuring your documentation examples remain accurate.
## Output Structure
After processing, your collection has a clean, conflict-free structure:
```plaintext theme={"dark"}
docs/
├── docs.json # Unified navigation
├── index.mdx # Collection landing page
├── images/
│ ├── collection-logo.png # Collection's own images
│ ├── product-1/ # Product 1's images
│ │ ├── logo.png
│ │ └── screenshots/
│ │ └── demo.png
│ └── product-2/ # Product 2's images
│ └── banner.png
├── snippets/
│ ├── SharedComponent.jsx # Collection's components
│ ├── product-1/ # Product 1's snippets
│ │ └── Hero.jsx
│ └── product-2/ # Product 2's snippets
│ └── Features.jsx
├── product-1/ # Product 1's content
│ ├── index.mdx
│ └── guides/
│ └── quickstart.mdx
└── product-2/ # Product 2's content
├── index.mdx
└── api/
└── overview.mdx
```
## Configuration Example
```xml MyPlatform.docsproj theme={"dark"}
Mintlify
My Platform
maple
index;quickstart
```
## Best Practices
Choose short, URL-friendly names like `product-1` rather than full project names. These become part of every URL in the referenced content.
Keep images and snippets in their respective directories. The handler specifically looks for `images/` and `snippets/` folders to relocate.
After building, verify that imports, images, and links resolve correctly. Check the browser console for 404 errors.
Since code blocks aren't rewritten, your documentation examples will show the original paths - which is usually what you want for copy-paste accuracy.
## Comparison with Base Markdown
The Mintlify handler extends the base `MarkdownDocReferenceHandler` with additional patterns:
| Feature | Markdown Handler | Mintlify Handler |
| --------------- | ---------------- | ---------------- |
| Markdown images | Yes | Yes |
| Markdown links | Yes | Yes |
| ES imports | No | Yes |
| JSX src/href | No | Yes |
| CSS url() | No | Yes |
| .mdx files | No | Yes |
## See Also
Complete guide to Documentation Collections including configuration, integration types, and troubleshooting
Complete reference for the DocumentationReference tag and its properties
Learn how navigation from multiple projects is merged