* docs: boost search ranking for single-word title pages
Apply `boost: 3` to English pages whose H1 / frontmatter title is a single word (e.g. "Assistant", "Quickstart", "Cards"). Short titles tend to be canonical landing pages for a topic, so users searching the exact term should land on them first.
* docs: drop boost on websocket-playground stub to keep canonical Playground ranking
`api-playground/websocket-playground.mdx` is an auto-generated AsyncAPI stub with no body content but shares the title "Playground" with `api-playground/overview.mdx`. Boosting both equally diluted the canonical overview page in search for the query "playground". Drop the boost on the stub.
* docs: document .mintlify/skills/ directory for multiple custom skills
* fix: indent list items inside Tip component to fix MDX parse error
* Test symlinked .mintlify/skills pointing to skills/ directory
* docs: document symlink support for .mintlify/skills directory
* docs: document .mintlify/skills/ directory for multiple custom skills
* Add .mintlify/skills/ directory with docs and API skills
* docs: apply copy suggestions from review
* fix: indent list items inside Tip component to fix MDX parse error
* Improve SEO descriptions across 47 pages
Curated descriptions from two bot-generated PRs (#3908, #3949),
selecting the best approach for each page:
- Added missing title and description frontmatter to 10 API reference pages
- Benefit-focused descriptions for integration pages (not implementation-heavy)
- Accurate REST-aligned titles for API endpoints (Export, List, Trigger, etc.)
- Expanded short descriptions to 50–160 character range throughout
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* copyedit
* Update custom-domain.mdx
* Fix analytics API page titles to match spec summaries
"Export" was inaccurate — spec uses "Get" for both endpoints.
Also updated descriptions to use "Retrieve" for consistency.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* Document YAML frontmatter fields for custom skill.md files
- Add comprehensive frontmatter documentation with all supported fields
- Clarify metadata as string key-value pairs (addresses review feedback)
- Specify allowed-tools as space-delimited experimental feature (addresses review feedback)
- Use mintlify-docs name to avoid collisions (addresses review feedback)
- Make frontmatter requirement explicit, not optional
Addresses all feedback from PR #2847 review comments.
* Documentation edits made through Mintlify web editor
* Documentation edits made through Mintlify web editor
* Documentation edits made through Mintlify web editor
* Documentation edits made through Mintlify web editor
---------
Co-authored-by: mintlify-development[bot] <109878554+mintlify-development[bot]@users.noreply.github.com>
Co-authored-by: cdxker <32852291+cdxker@users.noreply.github.com>
mintlify[bot]