Mintlify

Add documentation about whether the Linear integration supports bidirectional status sync, specifically whether closing a Linear issue automatically resolves the originating docs feedback comment.

Add technical documentation specifying the Slack agent's context window limits (e.g., number of messages or token limit) and clarify whether broadcast messages in threads are treated differently than direct replies for context purposes.

Create a dedicated limits or quotas documentation page that specifies rate limits for agent queries per workspace, with clear differentiation between Pro and Enterprise plan limits. This should be linked from the agent setup pages and pricing page.

Add documentation explaining whether skill.md files can be versioned alongside API releases, how to maintain multiple skill.md versions for different API versions, or if agents can be pinned to specific git tags/versions of the skill.md file.

Add documentation for `mintlify dev` CLI behavior regarding port assignment, concurrent usage by multiple engineers, and whether local previews can be isolated per branch or require port coordination.

Create a dedicated documentation page for Notion migration/import that explicitly describes how database relations, rollups, and other Notion-specific properties are handled during sync — whether preserved as metadata, flattened, or otherwise transformed.

Mintlify should document whether there are any configuration options (e.g., frontmatter flags, docs.json settings) to exclude specific pages from auto-generated llms.txt without fully overriding to a manual file. If no such options exist, explicitly state that the choice is binary: automatic generation (all navigation pages) or custom file (full manual control).

Add explicit documentation confirming whether the cookie-based authentication in the API playground supports httpOnly cookies and whether session persistence across page navigation works for cookie-based sessions (not just localStorage-based keys). The current docs explain how to enable cookies but don't clarify the security properties or persistence behavior.

Add explicit documentation about OpenAPI 3.1 discriminator schema support in the API playground, including any limitations or workarounds for polymorphic response rendering.

Add explicit documentation on whether the CLI supports multiple config files in subdirectories, or clarify the recommended architecture for monorepos with multiple independent documentation sites (e.g., workspace/monorepo patterns, separate Mintlify projects, or CI orchestration examples).

The React components page explains the `/snippets/` folder approach but never addresses npm package imports, which is a common enterprise need for design systems. Add explicit guidance on whether npm imports (private or public) are supported, or clearly state the limitation if only local `/snippets/` components work.

Add explicit documentation about CSS/styling migration from GitBook, specifically addressing: (1) whether custom CSS is preserved, (2) how GitBook CSS classes map to Mintlify selectors, and (3) recommended approach for rebuilding API reference styling using Mintlify's component system and custom CSS capabilities.

Add explicit qualification criteria for Enterprise tier (minimum seats, annual contract value, or company size thresholds) to the pricing page or a dedicated Enterprise plan details page.