* Remove Stainless integration page and fix Speakeasy config examples
Stainless was acquired by Anthropic (announced 2026-05-18) and wound down
all hosted products, including the SDK generator: "new signups, projects,
and SDKs will not be available." The integration page documented a
hosted-platform flow (Studio -> Release tab -> Setup OpenAPI publishing)
that no new reader can complete, so it is removed and redirected to the
vendor-neutral x-codeSamples page.
Speakeasy is still operating and the integration still works, but its
docs.json examples used the pre-docs.json schema (top-level "anchors"/
"tabs" keyed on "name"/"url"). Updated to the current navigation.anchors
/ navigation.tabs shape so the snippets are copy-pasteable.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Collapse Speakeasy page into the Add SDK examples page
With Stainless removed, the Integrations > SDKs group held a single page.
Fold the Speakeasy setup steps into api-playground/adding-sdk-examples.mdx
as a "Generate examples with Speakeasy" section and drop the group.
The page now covers both routes to x-codeSamples: writing samples by hand
and pulling autogenerated ones from a Speakeasy combined spec. Old page
paths redirect to the new section anchor.
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>
* use steps
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs: close reader-question gaps in automations, go-live, and Osano pages
Reworks the English-only subset of #6954 after review.
- automations/create.mdx: replace the redundant "review the output" tip
with a "Test your automation" section. Drops #6954's advice to test
before relying on "a schedule or event"; per /automations/manage most
automations can run manually only with a schedule trigger. Links the
run history section rather than the raw dashboard URL so credit usage
and run statuses stay documented in one place.
- migration-services/go-live-checklist.mdx: add the preview-URL and
mint broken-links steps to the existing Content validation section
instead of a new section. #6954's auth and page-access bullets
duplicated the Security section, and its redirects bullet is folded
into the existing one.
- integrations/privacy/osano.mdx: add a Verify the banner section and
note that content-directory .js files need no docs.json entry.
Excludes #6954's editor/tutorial.mdx prerequisites: the Editor group
root already documents editor access and roles, and the connected-repo
bullet is wrong for projects that skipped Git setup during onboarding.
The network-access.mdx lockout section is held pending confirmation of
what support can do for a locked-out org. Translations omitted; they
are generated after merge.
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>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs: clarify PostHog API key is safe to commit
Users were avoiding committing the apiKey out of caution, unaware
it's a client-side token already exposed in every browser request.
Fixes DOC-415 / mintlify/docs#609
* 💅
* docs: standardize documentation writing style
* docs: apply brand tone and style fixes
* docs: refine brand tone and writing style
* Revert changelog.mdx changes
The changelog is generated content and shouldn't be rewritten by the
brand tone and writing style pass.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Update ai/model-context-protocol.mdx
* Update ai/model-context-protocol.mdx
---------
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: fix contextual menu query field and add Speakeasy verification steps
* docs: translate contextual menu and Speakeasy changes to es, fr, zh
---------
Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
* fix: reduce Vale false positives via vocab and config updates
- Make English-word vocab entries case-insensitive so sentence-start
capitalization and normal prose usage stop flagging (agents, rest,
cursor, setup, endpoints, etc.)
- Add vocab entries for filenames and code identifiers that appear in
frontmatter and JSX contexts (docs.json, llms.txt, CLAUDE.md, etc.)
- Ignore openapi frontmatter lines, filenames, JSX attributes, email
addresses, and internal link targets via TokenIgnores
- Skip inline code scope and indented code fences
- Add Headings exceptions for proper nouns (Claude Code, GitHub
Actions, Route 53, GA4, etc.)
- Disable linting for the all-code vercel-json-generator snippet
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix: resolve all Vale warnings and errors across docs
Content fixes:
- Reword sentences using 'will', first person, spaced em dashes,
'e.g.', Latin abbreviations, and hyphenated adverbs
- Sentence-case headings that started with dotted filenames
- Backtick literal API values instead of bolding them
- Move periods inside quotation marks
- Fix Oxford comma rule misfires by restructuring sentences
False-positive suppression:
- Vale toggles around example user questions, keyboard shortcut keys
(Cmd+I), UI labels, and code samples in JSX contexts that Vale
misparses
- Exclude vale toggle comments from the brace Token/BlockIgnores so
in-document commands actually reach Vale (the greedy brace pattern
was also silently swallowing large regions; now lazy)
- Vocab entries for code identifiers (internal_id, handleSubmit, etc.)
- Per-file rule disables for component docs with dotted JSX names and
files where link-target linting ignores in-document toggles
Result: vale --minAlertLevel warning is clean repo-wide; only
suggestion-level items (Passive, Semicolons, Acronyms) remain.
mint broken-links passes.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix: correct WordList rule instead of degrading prose
- Restore sentence-start "Email" in advanced-support; the rule now
only flags hyphenated e-mail/E-mail forms
- Restore the idiom "above all else"; the above->preceding swap now
exempts "above all"
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix: restore deliberate prose flagged by blunt rules
- Restore spatial 'above the navbar' / 'above a page title' in
custom-scripts; the above->preceding swap now exempts 'above
the/a/an'
- Restore the '= ...' in the react-components named-export example
(the ellipsis is inside inline code) with an Ellipses toggle
- Restore SLA phrasing 'will use commercially reasonable efforts'
with a Will toggle
- Restore the quoted developer question in the GEO guide intro with a
FirstPerson toggle, matching the file's other example questions
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix: remove WordList swaps that flag legitimate English
- Drop tablet->device and firewalls->firewall rules; both words are
correct in ordinary prose
- Narrow touch->tap to UI-instruction phrasing (touch the/a) so
'keep in touch' and 'touch devices' stop flagging
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix: reposition vale toggles to wrap whole blocks
Toggle comments placed between list items split the lists (restarting
ol numbering in deployments) and comments flush against tables risked
breaking GFM table parsing. Wrap entire lists/tables with blank-line
separation instead. Verified rendering with mint dev: single ol with
two items, tables intact, no comments in visible DOM.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* refactor: prune accept.txt to load-bearing entries
Empirically removed 166 vocab entries (575 -> 409) whose removal
causes no Vale flags across all 908 English pages: dictionary words
that never needed listing (agents, setup, endpoints, webhooks, yaml),
lowercase entries the speller already accepts, and filename entries
made redundant by inline vale toggles.
Kept every case-enforcing entry (API, JSON, GitHub, ...) so casing
policy is unchanged, plus entries that double as capitalization
exceptions for headings (mcp, md, auth, cursor, txt).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Update ai/mintlify-mcp.mdx
* Update api/agent/v2/create-agent-job.mdx
* chore: alphabetize Headings exceptions and accept.txt
Case-insensitive sort, ignoring the (?i) prefix; also drops a
duplicate Scala entry.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix: re-apply OxfordComma rewrite lost in branch merge
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs: resolve Vale suggestions batch 1 (acronyms, semicolons, passive voice)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs: resolve remaining Vale suggestions (passive voice batch 2)
Rewrite ~90 passive constructions to active voice across deploy,
guides, migration-services, and organize docs. Toggle the deliberate
passive examples in the style-and-tone guide ('by zombies' test).
Add axios/lodash vocab entries for a repositioned code example.
vale . is now fully clean: 0 errors, 0 warnings, 0 suggestions.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* docs: update hosted docs domain to mintlify.site
* docs: complete mintlify.site migration across remaining pages
Updates 45 files that PR 6282 had originally changed but were
reverted by PR 6285 and not re-addressed in this PR:
- snippets/vercel-json-generator.mdx (all 4 locales): rewrite
destinations now use mintlify.site, consistent with deploy/vercel.mdx
- assistant/use.mdx: example deep-link URLs
- ai/skillmd.mdx: agent card subdomain reference
- guides/assistant-embed.mdx: docsURL code example
- guides/codex.mdx: MCP URL example
- deploy/authentication-setup.mdx: example Mintlify subdomain
- discovery-openapi.json: domain identifier URL descriptions (4 occurrences)
- integrations/privacy/osano.mdx: managed rule domain
- editor/branching-and-publishing.mdx: branch preview URL format
- customize/themes.mdx: theme demo site links
- guides/help-center.mdx: live example link
- zh/editor/collaborate.mdx: branch preview URL format
All changes mirrored across es, fr, and zh locales.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
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 Sonnet 4.6 <noreply@anthropic.com>
* clarify MCP returns MD
* Fix doc issues surfaced by user feedback
- Fix claude mcp add --header argument order: the flag must come after
the positional <name> and <url> args because --header is variadic and
otherwise consumes everything that follows it, causing the "missing
required argument 'name'" error users reported.
- Add tip to wrap iframes in Frame component to prevent overflow (user
suggestion on image-embeds page).
- Fix broken anchor link in quickstart CLI tab: /cli/install has no
#clone-your-repository section; replaced with inline git clone
instructions and a correct link to /deploy/github.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Document wide-mode behavior for side panel
Wide mode hides the entire side panel (not just the TOC), including
Panel components and OpenAPI request/response examples. This was
undocumented and actively confused a user who couldn't understand why
their OpenAPI example panels disappeared on wide-mode pages.
- Fix the wide mode description in organize/pages.mdx (it previously
said only the TOC was hidden, but ContentSideLayout.tsx returns null
for wide/center/custom modes entirely)
- Add a Note to components/panel.mdx calling out that the side panel
is absent on wide, center, and custom pages
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Resolve user feedback: clarify path formats, load timing, and analytics config
- react-components: add Constraints section (hooks pre-injected, no npm, no default exports)
- posthog: fix default host from app.posthog.com to ph.mintlify.com (confirmed via source)
- plausible: add ParamField descriptions including server field explanation
- create/text: note that internal links require root-relative paths without file extensions
- create/image-embeds: clarify image paths are root-relative, relative paths unsupported
- create/redirects: show redirects as top-level field in full docs.json example
- customize/custom-scripts: note that custom JS runs after page is interactive, applies globally
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* 💅
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* Standardize style: 'Click' to 'Select' for Mintlify UI; split long sentences
Generated-By: mintlify-agent
* Revert 'select' back to 'click' for UI interactions
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Fix select→click for UI elements across docs
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
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 Sonnet 4.6 <noreply@anthropic.com>
* 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.
* 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>
Rewording to use active voice per Vale style guide
Generated-By: mintlify-agent
Co-authored-by: mintlify-development[bot] <109878554+mintlify-development[bot]@users.noreply.github.com>
mintlify[bot]