From 1b65181f902a48217dd89153decb5a241a45a424 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Sat, 5 Sep 2026 08:09:54 +0000 Subject: [PATCH] fix: revert hosted docs URLs to mintlify.site domain --- ai/skillmd.mdx | 2 +- assistant/use.mdx | 4 +- changelog.mdx | 2 +- customize/themes.mdx | 18 ++++----- deploy/authentication-setup.mdx | 2 +- deploy/cloudflare.mdx | 8 ++-- deploy/csp-configuration.mdx | 12 +++--- deploy/reverse-proxy.mdx | 64 +++++++++++++++--------------- deploy/route53-cloudfront.mdx | 18 ++++----- deploy/vercel.mdx | 12 +++--- discovery-openapi.json | 8 ++-- editor/review.mdx | 2 +- es/deploy/vercel.mdx | 10 ++--- fr/deploy/vercel.mdx | 10 ++--- guides/assistant-embed.mdx | 4 +- guides/codex.mdx | 2 +- guides/help-center.mdx | 2 +- integrations/privacy/osano.mdx | 2 +- poc-onboarding.mdx | 4 +- quickstart.mdx | 8 ++-- reference/concepts.mdx | 2 +- reference/glossary.mdx | 2 +- snippets/setup-agent-prompt.mdx | 2 +- snippets/vercel-json-generator.mdx | 10 ++--- zh/deploy/vercel.mdx | 10 ++--- 25 files changed, 110 insertions(+), 110 deletions(-) diff --git a/ai/skillmd.mdx b/ai/skillmd.mdx index 4cee41cfc0..71b2dc78f0 100644 --- a/ai/skillmd.mdx +++ b/ai/skillmd.mdx @@ -246,7 +246,7 @@ A2A-compatible agents fetch `/.well-known/agent-card.json` to discover your site | `capabilities` | Feature flags. Currently `{ streaming: false, pushNotifications: false }`. | | `skills` | The skills exposed at `/.well-known/agent-skills/`. | -URLs in the card (`url`, `documentationUrl`, `provider.url`, and each skill URL) use your configured custom domain, so the published card always advertises the canonical domain instead of the `*.mintlifysite.com` subdomain. +URLs in the card (`url`, `documentationUrl`, `provider.url`, and each skill URL) use your configured custom domain, so the published card always advertises the canonical domain instead of the `*.mintlify.site` subdomain. If you use a [reverse proxy](/deploy/reverse-proxy), configure it to forward `/.well-known/agent-card.json` to your Mintlify subdomain. diff --git a/assistant/use.mdx b/assistant/use.mdx index cb61ba3e54..51d44250e4 100644 --- a/assistant/use.mdx +++ b/assistant/use.mdx @@ -75,8 +75,8 @@ Open the assistant from any page on your documentation site by adding the `?assi - `?assistant=`: Open the assistant chat panel and submit `` as the user's first message. URL-encode the value so spaces and special characters survive the request. ```text Examples -https://yourdocs.mintlifysite.com/quickstart?assistant -https://yourdocs.mintlifysite.com/quickstart?assistant=How%20do%20I%20get%20started%3F +https://yourdocs.mintlify.site/quickstart?assistant +https://yourdocs.mintlify.site/quickstart?assistant=How%20do%20I%20get%20started%3F ``` ## Highlight text diff --git a/changelog.mdx b/changelog.mdx index 45ecbc82b4..fa3ddf15a3 100644 --- a/changelog.mdx +++ b/changelog.mdx @@ -377,7 +377,7 @@ noindex: true ## Bug fixes - - Fixed OAuth redirect URIs on preview deployments so authenticated docs sign-in works on `.mintlifysite.com` preview hosts. + - Fixed OAuth redirect URIs on preview deployments so authenticated docs sign-in works on `.mintlify.site` preview hosts. - Fixed an MDX caching issue so that after a parse failure, subsequent edits recover cleanly. - MCP server "copy primary URL" button now shows a confirmation toast. - AsyncAPI playground correctly sends header-based auth as the `Sec-WebSocket-Protocol` subprotocol. diff --git a/customize/themes.mdx b/customize/themes.mdx index a671acdee2..d5fd08cce9 100644 --- a/customize/themes.mdx +++ b/customize/themes.mdx @@ -44,23 +44,23 @@ export const ThemeCard = ({ title, value, description, href }) => {
- + - + - + - + - + - + - + - + - +
diff --git a/deploy/authentication-setup.mdx b/deploy/authentication-setup.mdx index 843451c4a4..0e5b9eaeaa 100644 --- a/deploy/authentication-setup.mdx +++ b/deploy/authentication-setup.mdx @@ -16,7 +16,7 @@ Authentication requires users to log in before accessing your content. You can configure full authentication for all pages or partial authentication where some pages are public and others require authentication. -Authentication is only available for sites hosted on a custom domain or Mintlify subdomain. For example, `docs.example.com` or `example.mintlifysite.com`. Authentication is **not supported** for sites with a [custom subpath](/deploy/docs-subpath). For example, `example.com/docs`. +Authentication is only available for sites hosted on a custom domain or Mintlify subdomain. For example, `docs.example.com` or `example.mintlify.site`. Authentication is **not supported** for sites with a [custom subpath](/deploy/docs-subpath). For example, `example.com/docs`. To identify visitors while keeping pages public, use [personalization](/create/personalization). Personalization supports custom subpaths and can prefill API playground inputs without requiring visitors to authenticate before viewing a page. diff --git a/deploy/cloudflare.mdx b/deploy/cloudflare.mdx index 5d05e6e922..49fda4198d 100644 --- a/deploy/cloudflare.mdx +++ b/deploy/cloudflare.mdx @@ -46,7 +46,7 @@ While Cloudflare automatically handles many verification rules, creating additio #### Header forwarding requirements -Ensure that your Worker sets the `Host` header to your `.mintlifysite.com` target, as shown in the example script, rather than passing through the original request's `Host` header. Incorrect `Host` headers cause verification requests to fail. +Ensure that your Worker sets the `Host` header to your `.mintlify.site` target, as shown in the example script, rather than passing through the original request's `Host` header. Incorrect `Host` headers cause verification requests to fail. ### Configure routing @@ -77,7 +77,7 @@ async function handleRequest(request) { /^\/_mintlify\//.test(urlObject.pathname) ) { // Then Proxy to Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlifysite.com"; + const DOCS_URL = "[SUBDOMAIN].mintlify.site"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); @@ -171,7 +171,7 @@ If you use Webflow to host your main site and want to serve Mintlify docs at `/d /^\/_mintlify\//.test(urlObject.pathname) ) { // Proxy to Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlifysite.com"; + const DOCS_URL = "[SUBDOMAIN].mintlify.site"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); url.hostname = DOCS_URL; @@ -282,7 +282,7 @@ If issues persist, verify your rule configuration: If the firewall exception doesn't resolve the issue: 1. Check Cloudflare's **Security > Events** log for blocked requests. -2. Verify that your Cloudflare Worker (if using a custom subpath) sets the `Host` header to your `.mintlifysite.com` target instead of passing through the original request's `Host` header. +2. Verify that your Cloudflare Worker (if using a custom subpath) sets the `Host` header to your `.mintlify.site` target instead of passing through the original request's `Host` header. 3. Temporarily set Security Level to "Essentially Off" to confirm that Cloudflare is the cause. 4. Review any custom Page Rules that might override the firewall exception. diff --git a/deploy/csp-configuration.mdx b/deploy/csp-configuration.mdx index fb3b5bca15..d45dda99ac 100644 --- a/deploy/csp-configuration.mdx +++ b/deploy/csp-configuration.mdx @@ -26,7 +26,7 @@ The following CSP directives control which resources a page can load: | Domain | Purpose | CSP directive | Required | |:-------|:--------|:--------------|:-------| | `d4tuoctqmanu0.cloudfront.net` | KaTeX CSS, fonts | `style-src`, `font-src` | Required | -| `*.mintlifysite.com` | Documentation content | `connect-src`, `frame-src` | Required | +| `*.mintlify.site` | Documentation content | `connect-src`, `frame-src` | Required | | `*.mintlify.com` | Dashboard, API, analytics proxy | `connect-src` | Required | | `leaves.mintlify.com` | Assistant API | `connect-src` | Required | | `d3gk2c5xim1je2.cloudfront.net` | Icons, images, logos | `img-src` | Required | @@ -66,9 +66,9 @@ browser.sentry-cdn.com js.sentry-cdn.com hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; -connect-src 'self' *.mintlifysite.com *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com +connect-src 'self' *.mintlify.site *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com www.googletagmanager.com cdn.segment.com plausible.io us.posthog.com browser.sentry-cdn.com hcaptcha.com *.hcaptcha.com; -frame-src 'self' *.mintlifysite.com hcaptcha.com *.hcaptcha.com; +frame-src 'self' *.mintlify.site hcaptcha.com *.hcaptcha.com; ``` ## Common configurations by proxy type @@ -86,7 +86,7 @@ Create a Response Header Transform Rule: - **Header name**: `Content-Security-Policy` - **Header value**: ```text wrap - default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlifysite.com *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlifysite.com hcaptcha.com *.hcaptcha.com; + default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.site *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.site hcaptcha.com *.hcaptcha.com; ``` 4. Deploy your rule. @@ -101,7 +101,7 @@ Add a response headers policy in CloudFront: "Config": { "SecurityHeadersConfig": { "ContentSecurityPolicy": { - "ContentSecurityPolicy": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlifysite.com *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlifysite.com hcaptcha.com *.hcaptcha.com;", + "ContentSecurityPolicy": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.site *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.site hcaptcha.com *.hcaptcha.com;", "Override": true } } @@ -122,7 +122,7 @@ Add to your `vercel.json`: "headers": [ { "key": "Content-Security-Policy", - "value": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlifysite.com *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlifysite.com hcaptcha.com *.hcaptcha.com;" + "value": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' cdn.jsdelivr.net hcaptcha.com *.hcaptcha.com; style-src 'self' 'unsafe-inline' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com hcaptcha.com *.hcaptcha.com; font-src 'self' d4tuoctqmanu0.cloudfront.net fonts.googleapis.com; img-src 'self' data: blob: d3gk2c5xim1je2.cloudfront.net mintcdn.com *.mintcdn.com cdn.jsdelivr.net mintlify.s3.us-west-1.amazonaws.com; connect-src 'self' *.mintlify.site *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.site hcaptcha.com *.hcaptcha.com;" } ] } diff --git a/deploy/reverse-proxy.mdx b/deploy/reverse-proxy.mdx index 990732e7c2..845ea2c705 100644 --- a/deploy/reverse-proxy.mdx +++ b/deploy/reverse-proxy.mdx @@ -16,7 +16,7 @@ Set your base path on the [Custom domain setup](https://app.mintlify.com/setting The directory that contains your documentation in your repository does not configure the public base path. For example, storing documentation under a `/docs` directory does not replace setting `/docs` as the base path in your dashboard. -In all configurations, use `mintlifysite.com` as the proxy target. +In all configurations, use `mintlify.site` as the proxy target. ## Host at `/docs` subpath @@ -31,7 +31,7 @@ Before configuring your reverse proxy: 5. Click **Add domain**. - When you host at a subpath, your canonical docs URL becomes `.mintlifysite.com`, like `.mintlifysite.com/docs`. Proxy to `.mintlifysite.com` so cache invalidation and updates take effect. + When you host at a subpath, your canonical docs URL becomes `.mintlify.site`, like `.mintlify.site/docs`. Proxy to `.mintlify.site` so cache invalidation and updates take effect. ### Routing configuration @@ -40,19 +40,19 @@ Proxy these paths to your Mintlify subdomain: | Path | Destination | Caching | | --------------------------------- | ------------------------------------ | -------- | -| `/docs` | `.mintlifysite.com/docs` | No cache | -| `/docs/*` | `.mintlifysite.com/docs/*` | No cache | -| `/docs/_llms/*` | `.mintlifysite.com/docs/_llms/*` | No cache | -| `/.well-known/vercel/*` | `.mintlifysite.com/.well-known/vercel/*` | No cache | -| `/.well-known/skills/*` (optional) | `.mintlifysite.com/docs/.well-known/skills/*` | No cache | -| `/.well-known/agent-skills/*` (optional) | `.mintlifysite.com/docs/.well-known/agent-skills/*` | No cache | -| `/skill.md` (optional) | `.mintlifysite.com/docs/skill.md` | No cache | -| `/llms.txt` (optional) | `.mintlifysite.com/docs/llms.txt` | No cache | -| `/llms-full.txt` (optional) | `.mintlifysite.com/docs/llms-full.txt` | No cache | +| `/docs` | `.mintlify.site/docs` | No cache | +| `/docs/*` | `.mintlify.site/docs/*` | No cache | +| `/docs/_llms/*` | `.mintlify.site/docs/_llms/*` | No cache | +| `/.well-known/vercel/*` | `.mintlify.site/.well-known/vercel/*` | No cache | +| `/.well-known/skills/*` (optional) | `.mintlify.site/docs/.well-known/skills/*` | No cache | +| `/.well-known/agent-skills/*` (optional) | `.mintlify.site/docs/.well-known/agent-skills/*` | No cache | +| `/skill.md` (optional) | `.mintlify.site/docs/skill.md` | No cache | +| `/llms.txt` (optional) | `.mintlify.site/docs/llms.txt` | No cache | +| `/llms-full.txt` (optional) | `.mintlify.site/docs/llms-full.txt` | No cache | Your proxy must forward all HTTP methods on documentation paths. Mintlify sends analytics events as `POST` requests to `/docs/_mintlify/api/v1/e`. A proxy that only allows `GET` and `HEAD` requests silently breaks the analytics in your dashboard. -Mintlify serves these files under your base path, like `.mintlifysite.com/docs/llms.txt`. They are available on your domain under your subpath, like `your-domain.com/docs/llms.txt`, through your main subpath route. +Mintlify serves these files under your base path, like `.mintlify.site/docs/llms.txt`. They are available on your domain under your subpath, like `your-domain.com/docs/llms.txt`, through your main subpath route. The `/docs/*` route also covers generated `llms.txt` indexes under `/docs/_llms/*`. If your proxy uses a more granular path allowlist instead of forwarding all `/docs/*` requests, include `/docs/_llms/*` so agents can follow every index linked from `/docs/llms.txt`. @@ -64,7 +64,7 @@ The `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, `/llms. Configure your reverse proxy with these header requirements: -- **Origin**: Contains the target subdomain `.mintlifysite.com`. +- **Origin**: Contains the target subdomain `.mintlify.site`. - **X-Forwarded-For**: Preserves client IP information. - **X-Forwarded-Proto**: Preserves the original protocol (HTTP/HTTPS). - **X-Real-IP**: Forwards the real client IP address. @@ -83,8 +83,8 @@ server { # Vercel verification paths location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlifysite.com; - proxy_set_header Origin .mintlifysite.com; + proxy_pass https://.mintlify.site; + proxy_set_header Origin .mintlify.site; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -95,8 +95,8 @@ server { # AI skills paths location ^~ /.well-known/skills/ { - proxy_pass https://.mintlifysite.com/docs/.well-known/skills/; - proxy_set_header Origin .mintlifysite.com; + proxy_pass https://.mintlify.site/docs/.well-known/skills/; + proxy_set_header Origin .mintlify.site; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -107,8 +107,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlifysite.com/docs/.well-known/agent-skills/; - proxy_set_header Origin .mintlifysite.com; + proxy_pass https://.mintlify.site/docs/.well-known/agent-skills/; + proxy_set_header Origin .mintlify.site; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -119,8 +119,8 @@ server { # Skill manifest (optional) location = /skill.md { - proxy_pass https://.mintlifysite.com/docs/skill.md; - proxy_set_header Origin .mintlifysite.com; + proxy_pass https://.mintlify.site/docs/skill.md; + proxy_set_header Origin .mintlify.site; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -131,8 +131,8 @@ server { # LLM index files (optional) location = /llms.txt { - proxy_pass https://.mintlifysite.com/docs/llms.txt; - proxy_set_header Origin .mintlifysite.com; + proxy_pass https://.mintlify.site/docs/llms.txt; + proxy_set_header Origin .mintlify.site; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -142,8 +142,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlifysite.com/docs/llms-full.txt; - proxy_set_header Origin .mintlifysite.com; + proxy_pass https://.mintlify.site/docs/llms-full.txt; + proxy_set_header Origin .mintlify.site; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -154,8 +154,8 @@ server { # Documentation root location = /docs { - proxy_pass https://.mintlifysite.com; - proxy_set_header Origin .mintlifysite.com; + proxy_pass https://.mintlify.site; + proxy_set_header Origin .mintlify.site; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -166,8 +166,8 @@ server { # All documentation paths location /docs/ { - proxy_pass https://.mintlifysite.com/docs/; - proxy_set_header Origin .mintlifysite.com; + proxy_pass https://.mintlify.site/docs/; + proxy_set_header Origin .mintlify.site; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; @@ -184,7 +184,7 @@ To use a subpath other than `/docs` (such as `/help` or `/resources`): -Mintlify rebuilds your documentation to serve at your base path, so `.mintlifysite.com` serves your content. +Mintlify rebuilds your documentation to serve at your base path, so `.mintlify.site` serves your content. Configure your reverse proxy using the same [routing configuration](#routing-configuration), [header requirements](#required-header-configuration), and nginx patterns as the `/docs` subpath, replacing `/docs` with your base path. @@ -196,7 +196,7 @@ Configure your reverse proxy using the same [routing configuration](#routing-con **Cause**: Your reverse proxy points to an outdated hostname. -**Solution**: Update your reverse proxy configuration to point to `.mintlifysite.com`. +**Solution**: Update your reverse proxy configuration to point to `.mintlify.site`. ### 404 error @@ -207,7 +207,7 @@ Configure your reverse proxy using the same [routing configuration](#routing-con **Solution**: - Remove `Host` header forwarding. -- Set the `Origin` header to your Mintlify subdomain (`.mintlifysite.com`). +- Set the `Origin` header to your Mintlify subdomain (`.mintlify.site`). ### Generated `/_llms/` links return 404 diff --git a/deploy/route53-cloudfront.mdx b/deploy/route53-cloudfront.mdx index 4dfab2bff2..b73ba3a194 100644 --- a/deploy/route53-cloudfront.mdx +++ b/deploy/route53-cloudfront.mdx @@ -48,10 +48,10 @@ The behaviors for your subpath must allow all HTTP methods. CloudFront only allo ![CloudFront Distributions page with the "Create distribution" button emphasized.](/images/cloudfront/create-distribution.png) -3. For the Origin domain, input `[SUBDOMAIN].mintlifysite.com` where `[SUBDOMAIN]` is your project's unique subdomain. +3. For the Origin domain, input `[SUBDOMAIN].mintlify.site` where `[SUBDOMAIN]` is your project's unique subdomain. - ![CloudFront "Create distribution" page showing "acme.mintlifysite.com" as the origin domain.](/images/cloudfront/origin-name.png) + ![CloudFront "Create distribution" page showing "acme.mintlify.site" as the origin domain.](/images/cloudfront/origin-name.png) 4. For "Web Application Firewall (WAF)," enable security protections. @@ -91,7 +91,7 @@ The behaviors for your subpath must allow all HTTP methods. CloudFront only allo ![CloudFront "Create origin" page with an "Origin domain" input field highlighted.](/images/cloudfront/default-origin.png) -You should now have two Origins: one with `[SUBDOMAIN].mintlifysite.com` and another with your staging URL. +You should now have two Origins: one with `[SUBDOMAIN].mintlify.site` and another with your staging URL. ![CloudFront "Origins" page with two origins: One for `mintlify` and another for `mintlify-landing-page`.](/images/cloudfront/final-origins.png) @@ -101,7 +101,7 @@ You should now have two Origins: one with `[SUBDOMAIN].mintlifysite.com` and ano Behaviors in CloudFront enable control over the subpath logic. At a high level, you create the following logic: -- **If a user lands on your custom subpath**, go to `[SUBDOMAIN].mintlifysite.com`. +- **If a user lands on your custom subpath**, go to `[SUBDOMAIN].mintlify.site`. - **If a user lands on any other page**, go to the current landing page. 1. Navigate to the "Behaviors" tab of your CloudFront distribution. @@ -130,7 +130,7 @@ If `.well-known/*` is too generic, narrow it down to at least 2 behaviors for Ve ### Your subpath -Create a behavior with a **Path pattern** of your chosen subpath, for example `/docs`. Set **Origin and origin groups** to the `.mintlifysite.com` URL (for example, `acme.mintlifysite.com`). +Create a behavior with a **Path pattern** of your chosen subpath, for example `/docs`. Set **Origin and origin groups** to the `.mintlify.site` URL (for example, `acme.mintlify.site`). - Set "Cache policy" to **CachingDisabled**. - Set "Origin request policy" to **AllViewerExceptHostHeader**. @@ -142,12 +142,12 @@ Create a behavior with a **Path pattern** of your chosen subpath, for example `/ - ![CloudFront "Create behavior" page with a "Path pattern" of "/docs/*" and "Origin and origin groups" pointing to the `acme.mintlifysite.com` URL.](/images/cloudfront/behavior-1.png) + ![CloudFront "Create behavior" page with a "Path pattern" of "/docs/*" and "Origin and origin groups" pointing to the `acme.mintlify.site` URL.](/images/cloudfront/behavior-1.png) ### Your subpath with wildcard -Create a behavior with a **Path pattern** of your chosen subpath followed by `/*`, for example `/docs/*`, and **Origin and origin groups** pointing to the same `.mintlifysite.com` URL. +Create a behavior with a **Path pattern** of your chosen subpath followed by `/*`, for example `/docs/*`, and **Origin and origin groups** pointing to the same `.mintlify.site` URL. These settings should exactly match your base subpath behavior, with the exception of the **Path pattern**. @@ -158,7 +158,7 @@ These settings should exactly match your base subpath behavior, with the excepti ### `/mintlify-assets/*` -Create a behavior with a **Path pattern** of `/mintlify-assets/*` and set **Origin and origin groups** to the `.mintlifysite.com` URL. This path serves the CSS, JavaScript, and favicons for your documentation from the root of your domain. +Create a behavior with a **Path pattern** of `/mintlify-assets/*` and set **Origin and origin groups** to the `.mintlify.site` URL. This path serves the CSS, JavaScript, and favicons for your documentation from the root of your domain. - Set "Cache policy" to **CachingOptimized**. - Set "Origin request policy" to **AllViewerExceptHostHeader**. @@ -166,7 +166,7 @@ Create a behavior with a **Path pattern** of `/mintlify-assets/*` and set **Orig ### `/_mintlify/*` -Create a behavior with a **Path pattern** of `/_mintlify/*` and set **Origin and origin groups** to the `.mintlifysite.com` URL. This path handles API playground requests from the root of your domain. +Create a behavior with a **Path pattern** of `/_mintlify/*` and set **Origin and origin groups** to the `.mintlify.site` URL. This path handles API playground requests from the root of your domain. - Set "Cache policy" to **CachingDisabled**. - Set "Origin request policy" to **AllViewerExceptHostHeader**. diff --git a/deploy/vercel.mdx b/deploy/vercel.mdx index 03e19407a8..8d6696205e 100644 --- a/deploy/vercel.mdx +++ b/deploy/vercel.mdx @@ -17,7 +17,7 @@ The `vercel.json` file configures how your project builds and deploys. It sits i Mintlify uses the `rewrites` configuration in your `vercel.json` file to proxy requests from your main domain to your documentation. -Rewrites map incoming requests to different destinations without changing the URL in the browser. When someone visits `yoursite.com/docs`, Vercel internally fetches content from `your-subdomain.mintlifysite.com/docs`, but the user still sees `yoursite.com/docs` in their browser. This is different from redirects, which send users to another URL entirely. +Rewrites map incoming requests to different destinations without changing the URL in the browser. When someone visits `yoursite.com/docs`, Vercel internally fetches content from `your-subdomain.mintlify.site/docs`, but the user still sees `yoursite.com/docs` in their browser. This is different from redirects, which send users to another URL entirely. ## Configuration @@ -35,23 +35,23 @@ Rewrites map incoming requests to different destinations without changing the UR "rewrites": [ { "source": "/_mintlify/:path*", - "destination": "https://[subdomain].mintlifysite.com/_mintlify/:path*" + "destination": "https://[subdomain].mintlify.site/_mintlify/:path*" }, { "source": "/api/request", - "destination": "https://[subdomain].mintlifysite.com/_mintlify/api/request" + "destination": "https://[subdomain].mintlify.site/_mintlify/api/request" }, { "source": "/docs", - "destination": "https://[subdomain].mintlifysite.com/docs" + "destination": "https://[subdomain].mintlify.site/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlifysite.com/docs/:match*" + "destination": "https://[subdomain].mintlify.site/docs/:match*" }, { "source": "/mintlify-assets/:path+", - "destination": "https://[subdomain].mintlifysite.com/mintlify-assets/:path+" + "destination": "https://[subdomain].mintlify.site/mintlify-assets/:path+" } ] } diff --git a/discovery-openapi.json b/discovery-openapi.json index af3d79ad8f..a03a63e7e2 100644 --- a/discovery-openapi.json +++ b/discovery-openapi.json @@ -28,7 +28,7 @@ "schema": { "type": "string" }, - "description": "The domain identifier from your `domain.mintlifysite.com` URL. Can be found at the end of your dashboard URL. For example, `app.mintlify.com/organization/domain` has a domain identifier of `domain`." + "description": "The domain identifier from your `domain.mintlify.site` URL. Can be found at the end of your dashboard URL. For example, `app.mintlify.com/organization/domain` has a domain identifier of `domain`." } ], "requestBody": { @@ -464,7 +464,7 @@ "schema": { "type": "string" }, - "description": "The domain identifier from your `domain.mintlifysite.com` URL. Can be found at the end of your dashboard URL. For example, `app.mintlify.com/organization/domain` has a domain identifier of `domain`." + "description": "The domain identifier from your `domain.mintlify.site` URL. Can be found at the end of your dashboard URL. For example, `app.mintlify.com/organization/domain` has a domain identifier of `domain`." } ], "requestBody": { @@ -752,7 +752,7 @@ "schema": { "type": "string" }, - "description": "The domain identifier from your `domain.mintlifysite.com` URL. Can be found at the end of your dashboard URL. For example, `app.mintlify.com/organization/domain` has a domain identifier of `domain`." + "description": "The domain identifier from your `domain.mintlify.site` URL. Can be found at the end of your dashboard URL. For example, `app.mintlify.com/organization/domain` has a domain identifier of `domain`." } ], "requestBody": { @@ -838,7 +838,7 @@ "schema": { "type": "string" }, - "description": "The domain identifier from your `domain.mintlifysite.com` URL. Can be found at the end of your dashboard URL. For example, `app.mintlify.com/organization/domain` has a domain identifier of `domain`." + "description": "The domain identifier from your `domain.mintlify.site` URL. Can be found at the end of your dashboard URL. For example, `app.mintlify.com/organization/domain` has a domain identifier of `domain`." } ], "requestBody": { diff --git a/editor/review.mdx b/editor/review.mdx index 041ce8eb0c..d2f45f01df 100644 --- a/editor/review.mdx +++ b/editor/review.mdx @@ -21,7 +21,7 @@ To open the [agent](/editor/agent) beside the preview, click **Ask agent** in th ## Preview deployments -When you open a pull request from a feature branch, Mintlify builds a preview deployment: a temporary URL where your changes render exactly as they look when published. The preview rebuilds each time you save new changes to the branch. The URL format is `organization-branch-name.mintlifysite.com`. +When you open a pull request from a feature branch, Mintlify builds a preview deployment: a temporary URL where your changes render exactly as they look when published. The preview rebuilds each time you save new changes to the branch. The URL format is `organization-branch-name.mintlify.site`. Preview URLs are publicly accessible by default. To restrict access to members of your Mintlify organization, enable preview authentication in the **Previews** section of the [Add-ons](https://app.mintlify.com/settings/deployment/addons) page in your dashboard. See [Restrict access to preview deployments](/deploy/preview-deployments#restrict-access-to-preview-deployments) for more information. diff --git a/es/deploy/vercel.mdx b/es/deploy/vercel.mdx index 2cf601d42d..cb05e62e1b 100644 --- a/es/deploy/vercel.mdx +++ b/es/deploy/vercel.mdx @@ -41,23 +41,23 @@ Las reglas de reescritura (rewrites) asignan las solicitudes entrantes a distint "rewrites": [ { "source": "/_mintlify/:path*", - "destination": "https://[subdomain].mintlifysite.com/_mintlify/:path*" + "destination": "https://[subdomain].mintlify.site/_mintlify/:path*" }, { "source": "/api/request", - "destination": "https://[subdomain].mintlifysite.com/_mintlify/api/request" + "destination": "https://[subdomain].mintlify.site/_mintlify/api/request" }, { "source": "/docs", - "destination": "https://[subdomain].mintlifysite.com/docs" + "destination": "https://[subdomain].mintlify.site/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlifysite.com/docs/:match*" + "destination": "https://[subdomain].mintlify.site/docs/:match*" }, { "source": "/mintlify-assets/:path+", - "destination": "https://[subdomain].mintlifysite.com/mintlify-assets/:path+" + "destination": "https://[subdomain].mintlify.site/mintlify-assets/:path+" } ] } diff --git a/fr/deploy/vercel.mdx b/fr/deploy/vercel.mdx index bb4b408056..1e14c5a786 100644 --- a/fr/deploy/vercel.mdx +++ b/fr/deploy/vercel.mdx @@ -42,23 +42,23 @@ Les réécritures (`rewrites`) font correspondre les requêtes entrantes à diff "rewrites": [ { "source": "/_mintlify/:path*", - "destination": "https://[subdomain].mintlifysite.com/_mintlify/:path*" + "destination": "https://[subdomain].mintlify.site/_mintlify/:path*" }, { "source": "/api/request", - "destination": "https://[subdomain].mintlifysite.com/_mintlify/api/request" + "destination": "https://[subdomain].mintlify.site/_mintlify/api/request" }, { "source": "/docs", - "destination": "https://[subdomain].mintlifysite.com/docs" + "destination": "https://[subdomain].mintlify.site/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlifysite.com/docs/:match*" + "destination": "https://[subdomain].mintlify.site/docs/:match*" }, { "source": "/mintlify-assets/:path+", - "destination": "https://[subdomain].mintlifysite.com/mintlify-assets/:path+" + "destination": "https://[subdomain].mintlify.site/mintlify-assets/:path+" } ] } diff --git a/guides/assistant-embed.mdx b/guides/assistant-embed.mdx index 6d62eb7e25..32c546fb4b 100644 --- a/guides/assistant-embed.mdx +++ b/guides/assistant-embed.mdx @@ -72,13 +72,13 @@ Open `src/config.js` and update with your Mintlify project details. ```js src/config.js export const ASSISTANT_CONFIG = { domain: 'your-domain', - docsURL: 'https://yourdocs.mintlifysite.com', + docsURL: 'https://yourdocs.mintlify.site', }; ``` Replace: - `your-domain` with your Mintlify project domain found at the end of your dashboard URL. -- `https://yourdocs.mintlifysite.com` with your actual documentation URL. +- `https://yourdocs.mintlify.site` with your actual documentation URL. diff --git a/guides/codex.mdx b/guides/codex.mdx index 24ac31c17e..9ca1826ea4 100644 --- a/guides/codex.mdx +++ b/guides/codex.mdx @@ -177,7 +177,7 @@ To connect to your own documentation site's MCP server instead, replace the URL ```toml [mcp_servers.my-docs] -url = "https://your-docs.mintlifysite.com/mcp" +url = "https://your-docs.mintlify.site/mcp" ``` Restart your `codex` session for the config change to take effect. To confirm the MCP server connected, ask Codex `Which MCP servers do you have access to?`. It should list the entry you added. diff --git a/guides/help-center.mdx b/guides/help-center.mdx index c1fa6f73c7..24e5fffdf7 100644 --- a/guides/help-center.mdx +++ b/guides/help-center.mdx @@ -22,7 +22,7 @@ The fastest way to create a new help center is with the `mint new --template` co mint new your-help-center-name --template help-center-starter ``` -This creates a new project pre-configured for a help center, including navigation structure, sample pages, and directory listings. See the [live example](https://help-center-starter.mintlifysite.com/) or browse the [template source](https://github.com/mintlify/templates/tree/main/help-center-starter). +This creates a new project pre-configured for a help center, including navigation structure, sample pages, and directory listings. See the [live example](https://help-center-starter.mintlify.site/) or browse the [template source](https://github.com/mintlify/templates/tree/main/help-center-starter). If you prefer to configure a help center in an existing project, continue with the steps below. diff --git a/integrations/privacy/osano.mdx b/integrations/privacy/osano.mdx index 65c9337abc..89c1d158c0 100644 --- a/integrations/privacy/osano.mdx +++ b/integrations/privacy/osano.mdx @@ -48,7 +48,7 @@ After you deploy, open your site in a private or incognito window and confirm th - Add `.mintlifysite.com/` as a managed rule. + Add `.mintlify.site/` as a managed rule. Osano managed rule diff --git a/poc-onboarding.mdx b/poc-onboarding.mdx index 5c5c870b71..18c127eda1 100644 --- a/poc-onboarding.mdx +++ b/poc-onboarding.mdx @@ -98,11 +98,11 @@ Share the goal, baseline, and criteria with your AE or SE. - After the starter content deploys, find your URL on the **Overview** page of the [dashboard](https://app.mintlify.com/). Open the `https://.mintlifysite.com` URL and confirm that it loads. + After the starter content deploys, find your URL on the **Overview** page of the [dashboard](https://app.mintlify.com/). Open the `https://.mintlify.site` URL and confirm that it loads. -Use the `.mintlifysite.com` URL during the POC. [Authentication](/deploy/authentication-setup) works on your `.mintlifysite.com` subdomain or a [custom domain](/customize/custom-domain), but does not work on a custom subpath such as `yourcompany.com/docs`. +Use the `.mintlify.site` URL during the POC. [Authentication](/deploy/authentication-setup) works on your `.mintlify.site` subdomain or a [custom domain](/customize/custom-domain), but does not work on a custom subpath such as `yourcompany.com/docs`. ## Step 2: Invite your team diff --git a/quickstart.mdx b/quickstart.mdx index d6982c1bb7..b5c3230981 100644 --- a/quickstart.mdx +++ b/quickstart.mdx @@ -46,7 +46,7 @@ After you complete this guide, you'll have a live documentation site ready to cu 7. Run `mint dev --no-open` from the directory containing `docs.json` as a background process. Confirm the local URL loads, report it to the user, and stop the process when it is no longer needed. 8. Run `mint validate` and `mint broken-links`. Fix issues caused by your changes before continuing. 9. If a Git repository backs the project and the user asked for deployment, commit and push the changes. A push to the production branch triggers a deployment. Do not overwrite an existing repository with starter content. - 10. Run `mint status` to get the configured subdomain, then verify that `https://.mintlifysite.com` loads before reporting that deployment is complete. + 10. Run `mint status` to get the configured subdomain, then verify that `https://.mintlify.site` loads before reporting that deployment is complete. Have the user complete browser actions only for email verification, OAuth approval, and connecting or authorizing GitHub. Keep ownership of the terminal workflow and resume after each user action. For command flags and troubleshooting, use the [CLI command reference](/cli/commands). @@ -65,7 +65,7 @@ When you connect your documentation repository to your project, you can work on In the final onboarding step, describe the docs that you want to build. You can add links to your existing site, upload files, or select GitHub repositories to use as sources. The Mintlify agent generates a starting point for your docs while you watch a live preview. Answer any questions the agent asks to refine the result. To start with placeholder content instead, select **Skip, start from a blank template**. - After onboarding, your documentation site deploys and is accessible at your `.mintlifysite.com` URL. + After onboarding, your documentation site deploys and is accessible at your `.mintlify.site` URL. If you want to get started quickly without connecting your own repository, you can skip the Git provider connection during onboarding. Mintlify creates a private repository in a private organization and automatically configures the GitHub App for you. @@ -75,12 +75,12 @@ When you connect your documentation repository to your project, you can work on - Use the preceding CLI setup workflow. Initiate the corresponding `mint signup` or `mint login` command. Account verification and GitHub authorization open browser pages; have the user approve them. Continue the setup when they finish. Do not consider setup complete until `mint status` reports a subdomain and the deployed `.mintlifysite.com` URL loads. + Use the preceding CLI setup workflow. Initiate the corresponding `mint signup` or `mint login` command. Account verification and GitHub authorization open browser pages; have the user approve them. Continue the setup when they finish. Do not consider setup complete until `mint status` reports a subdomain and the deployed `.mintlify.site` URL loads. ## View your deployed site -Your documentation site is now deployed at `https://.mintlifysite.com`. +Your documentation site is now deployed at `https://.mintlify.site`. Find your exact URL on the **Overview** page of your [dashboard](https://app.mintlify.com/). diff --git a/reference/concepts.mdx b/reference/concepts.mdx index c6dc2865c4..64c02c6910 100644 --- a/reference/concepts.mdx +++ b/reference/concepts.mdx @@ -21,7 +21,7 @@ An **organization** is the workspace for your team. It contains your members, or A **deployment** is a documentation project in your organization. It connects a repository, content directory, and deployment branch to a published site. An organization can have multiple deployments for separate products or documentation properties. -A **live site** is the published output of a deployment. Mintlify provides a `.mintlifysite.com` URL by default. You can connect a [custom domain](/customize/custom-domain) for your site. Sites include your content, navigation, search, and any features you enable, such as the assistant or API playground. +A **live site** is the published output of a deployment. Mintlify provides a `.mintlify.site` URL by default. You can connect a [custom domain](/customize/custom-domain) for your site. Sites include your content, navigation, search, and any features you enable, such as the assistant or API playground. The documentation sometimes uses **project** as a general name for a deployment and its connected repository, configuration, and site. diff --git a/reference/glossary.mdx b/reference/glossary.mdx index 9da578ae68..720d6e31a0 100644 --- a/reference/glossary.mdx +++ b/reference/glossary.mdx @@ -66,7 +66,7 @@ Units that measure use of Mintlify AI features. Credits are pooled across an org ### Custom domain -A domain, subdomain, or subpath that you connect to a Mintlify site instead of using its default `.mintlifysite.com` address. See [Custom domain](/customize/custom-domain). +A domain, subdomain, or subpath that you connect to a Mintlify site instead of using its default `.mintlify.site` address. See [Custom domain](/customize/custom-domain). ## D diff --git a/snippets/setup-agent-prompt.mdx b/snippets/setup-agent-prompt.mdx index 68f669761f..6f0ab77c77 100644 --- a/snippets/setup-agent-prompt.mdx +++ b/snippets/setup-agent-prompt.mdx @@ -16,7 +16,7 @@ Get my documentation live on a published Mintlify site. You are successfully don 9. Preview with `mint dev`, which generally starts on `http://localhost:3000` unless that port is in use. It blocks until stopped, so run it as a background task. Verify the preview loads, then stop it before continuing. 10. Commit and push your changes. Mintlify deploys automatically on push. 11. Needs me: If I want a custom domain, run `mint add-domain `. It prints the DNS records I need to add with my domain provider. Tell me the DNS records, since only I can configure them at my registrar. Make it clear that this is a step I must complete. -12. Confirm my site is live: fetch `https://.mintlifysite.com` (find the subdomain via `mint status`) and confirm it loads. If I added a custom domain in step 11, also fetch that domain and confirm it loads before calling this step done—DNS propagation can lag, so retry a few times before treating a failed fetch as an error. +12. Confirm my site is live: fetch `https://.mintlify.site` (find the subdomain via `mint status`) and confirm it loads. If I added a custom domain in step 11, also fetch that domain and confirm it loads before calling this step done—DNS propagation can lag, so retry a few times before treating a failed fetch as an error. 13. Set yourself up to keep working here: install the [Mintlify skill](https://mintlify.com/docs/ai/skillmd.md) with `npx skills add https://mintlify.com/docs`, then register the [admin MCP server](https://mintlify.com/docs/ai/model-context-protocol.md) at `https://mcp.mintlify.com` for your specific tool. For example, `claude mcp add --transport http mintlify https://mcp.mintlify.com` for Claude Code or fetch https://mintlify.com/docs/ai/mintlify-mcp.md for instructions for Claude, Cursor, Codex, or ChatGPT. Do this step yourself—don't ask me to run these commands. 14. Needs me: the first admin MCP tool call opens a browser window for OAuth login. Approve it there. Most tools don't load newly added MCP servers mid-session — if the Mintlify tools don't show up, tell me to restart you and we'll pick up from here. 15. If any command fails in a way not covered above, stop and tell me the exact error rather than guessing or retrying blindly. If it looks like something's wrong on Mintlify's end rather than in what you're doing, check https://status.mintlify.com or point me to https://mintlify.com/docs/contact-support. diff --git a/snippets/vercel-json-generator.mdx b/snippets/vercel-json-generator.mdx index 11b589311b..f106c60553 100644 --- a/snippets/vercel-json-generator.mdx +++ b/snippets/vercel-json-generator.mdx @@ -8,23 +8,23 @@ export const VercelJsonGenerator = () => { rewrites: [ { source: "/_mintlify/:path*", - destination: `https://${subdomain}.mintlifysite.com/_mintlify/:path*` + destination: `https://${subdomain}.mintlify.site/_mintlify/:path*` }, { source: "/api/request", - destination: `https://${subdomain}.mintlifysite.com/_mintlify/api/request` + destination: `https://${subdomain}.mintlify.site/_mintlify/api/request` }, { source: `/${cleanSubpath}`, - destination: `https://${subdomain}.mintlifysite.com/${cleanSubpath}` + destination: `https://${subdomain}.mintlify.site/${cleanSubpath}` }, { source: `/${cleanSubpath}/:path*`, - destination: `https://${subdomain}.mintlifysite.com/${cleanSubpath}/:path*` + destination: `https://${subdomain}.mintlify.site/${cleanSubpath}/:path*` }, { source: "/mintlify-assets/:path+", - destination: `https://${subdomain}.mintlifysite.com/mintlify-assets/:path+` + destination: `https://${subdomain}.mintlify.site/mintlify-assets/:path+` } ] } diff --git a/zh/deploy/vercel.mdx b/zh/deploy/vercel.mdx index d9228c5ef3..2a3d3de840 100644 --- a/zh/deploy/vercel.mdx +++ b/zh/deploy/vercel.mdx @@ -42,23 +42,23 @@ Rewrites 会在不更改浏览器中 URL 的情况下，将传入请求映射到 "rewrites": [ { "source": "/_mintlify/:path*", - "destination": "https://[subdomain].mintlifysite.com/_mintlify/:path*" + "destination": "https://[subdomain].mintlify.site/_mintlify/:path*" }, { "source": "/api/request", - "destination": "https://[subdomain].mintlifysite.com/_mintlify/api/request" + "destination": "https://[subdomain].mintlify.site/_mintlify/api/request" }, { "source": "/docs", - "destination": "https://[subdomain].mintlifysite.com/docs" + "destination": "https://[subdomain].mintlify.site/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlifysite.com/docs/:match*" + "destination": "https://[subdomain].mintlify.site/docs/:match*" }, { "source": "/mintlify-assets/:path+", - "destination": "https://[subdomain].mintlifysite.com/mintlify-assets/:path+" + "destination": "https://[subdomain].mintlify.site/mintlify-assets/:path+" } ] }