* docs: add help center article on advertising an external MCP server
* docs: translate external MCP help center page and tighten SEO metadata
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
* docs: add help center article on changing the workspace icon
* docs: shorten French description to meet SEO length limit
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
* Document className and Tailwind arbitrary value support
All built-in components now accept a className prop (mint#10540), and
dynamic Tailwind utilities work in className on MDX components
(mint#6737). Two pages stated the opposite.
- Correct the claims that Tailwind arbitrary values are unsupported in
customize/custom-scripts and guides/custom-layouts
- Add className and arbitrary value guidance to the Tailwind section of
custom-scripts, including the runtime-class limitation and the Tab
content-panel caveat
- Add a Style components section to the components overview
- Add className property rows to every component reference page that
supports it, and note the three components that do not
- Document inline Markdown support in component title props
- Correct the callouts page, which said typed callouts accept only
children
- Replace inline style resizing with Tailwind classes in image embeds
- Add a help center article for Tailwind classes not applying in the
editor's live preview, and note the limitation in custom-layouts
- Point skill.md at className before custom.css
- Accept className, keyframes, and unstyled in the Vale vocabulary
Resolves DOC-316, DOC-317
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Apply batched suggestions from code review
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
* Apply batched suggestions from code review
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs: add help center page for agent IP allow list failures
* docs: add English anchor IDs to translated headings
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
* docs: update search settings section name after dashboard rebuild
* docs: use deployment name terminology after general settings rebuild
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
* docs: document web editor branch list visibility rule and workarounds
* docs: add fr/es/zh translations for branch visibility updates
* docs: correct editor branch list rule and scope the URL workaround
The visibility rule as first written covered only branches pushed
directly to a Git provider. Verified against the editor branch code:
records are also soft-deleted when a pull request is merged or closed
(editorBranch.service.ts), the list defaults to PR states none/draft/open
(editorBranch.validators.ts), and cross-repository (fork) pull requests
are filtered out. Those cases match the support threads about branches
disappearing after publishing, so document them.
Also scope the URL workaround: without an editor branch record,
autocommit is skipped, the branch diff fails, and rename/delete return
404. It is a view-and-edit fallback, not an equivalent to opening a
pull request.
Drop the hand-written es/fr/zh pages and locale nav entries; those are
generated after merge.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Apply suggestion from @ethanpalm
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs: add help center article on renaming deployments and organizations
* docs: apply translation heading anchors and tighten SEO descriptions
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
* docs: clarify preview API does not support fork branches
* docs: translate fork preview clarification and tighten SEO description
* Apply suggestion from @ethanpalm
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
* docs: add help center article for private repo missing in second deployment onboarding
* docs: translate second-deployment private repo help article and tighten English title
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
* docs: add help center article for static file 404 troubleshooting
* docs: translate static-file-not-served help center article to es, fr, zh
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
* docs: add troubleshooting for OpenAPI URL fetch failures during build
* docs: translate OpenAPI fetch-failure troubleshooting to es/fr/zh
* docs: move OpenAPI fetch diagnostics to first help-center page
Split the troubleshooting accordion: the curated page keeps a complete,
compact answer, and the deep diagnostic walkthrough moves to a new
help-center page that is searchable but excluded from the sidebar.
- Add hidden + searchable "Help center" group to docs.json
- Revert es/fr/zh edits so the translation pipeline regenerates them
- Broaden the allowlist vocabulary entry to cover inflected forms
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* make help center a hidden tab
* 💅
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
mintlify[bot]