From 2db27bd6f125787c5d0df86812a8885d0b204e41 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 26 Jun 2026 17:16:54 +0000 Subject: [PATCH 1/2] docs: update hosted docs domain to mintlify.site --- deploy/cloudflare.mdx | 4 +- deploy/csp-configuration.mdx | 12 +-- deploy/reverse-proxy.mdx | 138 ++++++++++++++++--------------- deploy/route53-cloudfront.mdx | 14 ++-- deploy/vercel.mdx | 6 +- es/deploy/cloudflare.mdx | 4 +- es/deploy/csp-configuration.mdx | 12 +-- es/deploy/reverse-proxy.mdx | 138 ++++++++++++++++--------------- es/deploy/route53-cloudfront.mdx | 14 ++-- es/deploy/vercel.mdx | 6 +- es/quickstart.mdx | 4 +- es/what-is-mintlify.mdx | 2 +- fr/deploy/cloudflare.mdx | 4 +- fr/deploy/csp-configuration.mdx | 12 +-- fr/deploy/reverse-proxy.mdx | 138 ++++++++++++++++--------------- fr/deploy/route53-cloudfront.mdx | 14 ++-- fr/deploy/vercel.mdx | 6 +- fr/quickstart.mdx | 4 +- fr/what-is-mintlify.mdx | 2 +- quickstart.mdx | 4 +- what-is-mintlify.mdx | 2 +- zh/deploy/cloudflare.mdx | 4 +- zh/deploy/csp-configuration.mdx | 12 +-- zh/deploy/reverse-proxy.mdx | 138 ++++++++++++++++--------------- zh/deploy/route53-cloudfront.mdx | 14 ++-- zh/deploy/vercel.mdx | 6 +- zh/quickstart.mdx | 4 +- zh/what-is-mintlify.mdx | 2 +- 28 files changed, 364 insertions(+), 356 deletions(-) diff --git a/deploy/cloudflare.mdx b/deploy/cloudflare.mdx index 52ddee619e..45b6f4f857 100644 --- a/deploy/cloudflare.mdx +++ b/deploy/cloudflare.mdx @@ -66,7 +66,7 @@ async function handleRequest(request) { // If the request is to the docs subpath if (/^\/docs/.test(urlObject.pathname)) { // Then Proxy to Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.site"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); @@ -149,7 +149,7 @@ If you use Webflow to host your main site and want to serve Mintlify docs at `/d // If the request is to the docs subpath if (/^\/docs/.test(urlObject.pathname)) { // Proxy to Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.site"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); url.hostname = DOCS_URL; diff --git a/deploy/csp-configuration.mdx b/deploy/csp-configuration.mdx index 069e0ab4a7..36ccc469e0 100644 --- a/deploy/csp-configuration.mdx +++ b/deploy/csp-configuration.mdx @@ -24,7 +24,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 | -| `*.mintlify.dev` | 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 | @@ -62,9 +62,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' *.mintlify.dev *.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' *.mintlify.dev hcaptcha.com *.hcaptcha.com; +frame-src 'self' *.mintlify.site hcaptcha.com *.hcaptcha.com; ``` ## Common configurations by proxy type @@ -82,7 +82,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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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. @@ -97,7 +97,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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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 } } @@ -118,7 +118,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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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 496e803f20..4a8e1249c7 100644 --- a/deploy/reverse-proxy.mdx +++ b/deploy/reverse-proxy.mdx @@ -12,8 +12,10 @@ When you implement a reverse proxy, monitor for potential issues with domain ver Mintlify supports two reverse proxy configurations depending on your subpath requirements. -- **Host at `/docs`**: Use `mintlify.dev` as the proxy target. Enable the **Host at `/docs`** toggle on the [Custom domain setup](https://app.mintlify.com/settings/deployment/custom-domain) page in your dashboard. This is a simpler configuration with fewer routes. -- **Custom subpath**: Use `mintlify.app` as the proxy target. This approach supports any subpath and requires additional routing rules. +- **Host at `/docs`**: Enable the **Host at `/docs`** toggle on the [Custom domain setup](https://app.mintlify.com/settings/deployment/custom-domain) page in your dashboard. This is a simpler configuration with fewer routes. +- **Custom subpath**: Use any subpath you choose. This approach requires additional routing rules. + +In both configurations, use `mintlify.site` as the proxy target. ## Host at `/docs` subpath @@ -26,7 +28,7 @@ Before configuring your reverse proxy: 3. Enter your domain and click **Add domain**. - When you enable **Host at `/docs`**, your canonical docs URL becomes `.mintlify.dev`. Cache invalidation stops on `mintlify.app`, and you must proxy to `mintlify.dev` for updates to appear. + When you enable **Host at `/docs`**, your canonical docs URL becomes `.mintlify.site/docs`. Proxy to `.mintlify.site` so cache invalidation and updates take effect. ### Routing configuration @@ -35,14 +37,14 @@ Proxy these paths to your Mintlify subdomain: | Path | Destination | Caching | | --------------------------------- | ------------------------------------ | -------- | -| `/docs` | `.mintlify.dev/docs` | No cache | -| `/docs/*` | `.mintlify.dev/docs` | No cache | -| `/.well-known/vercel/*` | `.mintlify.dev` | No cache | -| `/.well-known/skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/.well-known/agent-skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/skill.md` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms.txt` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms-full.txt` (optional) | `.mintlify.dev/docs` | No cache | +| `/docs` | `.mintlify.site/docs` | No cache | +| `/docs/*` | `.mintlify.site/docs` | No cache | +| `/.well-known/vercel/*` | `.mintlify.site` | No cache | +| `/.well-known/skills/*` (optional) | `.mintlify.site/docs` | No cache | +| `/.well-known/agent-skills/*` (optional) | `.mintlify.site/docs` | No cache | +| `/skill.md` (optional) | `.mintlify.site/docs` | No cache | +| `/llms.txt` (optional) | `.mintlify.site/docs` | No cache | +| `/llms-full.txt` (optional) | `.mintlify.site/docs` | No cache | The `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, `/llms.txt`, and `/llms-full.txt` routes are optional. Include them only if you want to serve AI files at root paths like `your-domain.com/llms.txt` instead of under your docs subpath like `your-domain.com/docs/llms.txt`. @@ -50,7 +52,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 `.mintlify.dev` +- **Origin**: Contains the target subdomain `.mintlify.site` - **X-Forwarded-For**: Preserves client IP information - **X-Forwarded-Proto**: Preserves original protocol (HTTP/HTTPS) - **X-Real-IP**: Forwards the real client IP address @@ -69,8 +71,8 @@ server { # Vercel verification paths location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.dev; - proxy_set_header Origin .mintlify.dev; + 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; @@ -81,8 +83,8 @@ server { # AI skills paths location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -93,8 +95,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -105,8 +107,8 @@ server { # Skill manifest (optional) location = /skill.md { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -117,8 +119,8 @@ server { # LLM index files (optional) location = /llms.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -128,8 +130,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -140,8 +142,8 @@ server { # Documentation root location = /docs { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -152,8 +154,8 @@ server { # All documentation paths location /docs/ { - proxy_pass https://.mintlify.dev/docs/; - proxy_set_header Origin .mintlify.dev; + 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; @@ -176,16 +178,16 @@ Proxy these paths to your Mintlify subdomain with the specified caching policies | Path | Destination | Caching | | --------------------------------- | ------------------------------- | ------------- | -| `/.well-known/vercel/*` | `.mintlify.app` | No cache | -| `/.well-known/skills/*` | `.mintlify.app` | No cache | -| `/.well-known/agent-skills/*` | `.mintlify.app` | No cache | -| `/skill.md` | `.mintlify.app` | No cache | -| `/llms.txt` | `.mintlify.app` | No cache | -| `/llms-full.txt` | `.mintlify.app` | No cache | -| `/mintlify-assets/_next/static/*` | `.mintlify.app` | Cache enabled | -| `/_mintlify/*` | `.mintlify.app` | No cache | -| `/*` | `.mintlify.app` | No cache | -| `/` | `.mintlify.app` | No cache | +| `/.well-known/vercel/*` | `.mintlify.site` | No cache | +| `/.well-known/skills/*` | `.mintlify.site` | No cache | +| `/.well-known/agent-skills/*` | `.mintlify.site` | No cache | +| `/skill.md` | `.mintlify.site` | No cache | +| `/llms.txt` | `.mintlify.site` | No cache | +| `/llms-full.txt` | `.mintlify.site` | No cache | +| `/mintlify-assets/_next/static/*` | `.mintlify.site` | Cache enabled | +| `/_mintlify/*` | `.mintlify.site` | No cache | +| `/*` | `.mintlify.site` | No cache | +| `/` | `.mintlify.site` | No cache | Mintlify serves `llms.txt`, `llms-full.txt`, and `skill.md` at the root path. If your docs live under a subpath (such as `/help`), you can also serve these files under that subpath (for example, `/help/llms.txt`). To do this, add location blocks that rewrite the subpath to the root path. See the nginx example below for both patterns. @@ -195,7 +197,7 @@ Proxy these paths to your Mintlify subdomain with the specified caching policies Configure your reverse proxy with these header requirements: -- **Origin**: Contains the target subdomain `.mintlify.app` +- **Origin**: Contains the target subdomain `.mintlify.site` - **X-Forwarded-For**: Preserves client IP information - **X-Forwarded-Proto**: Preserves original protocol (HTTP/HTTPS) - **X-Real-IP**: Forwards the real client IP address @@ -214,8 +216,8 @@ server { # Vercel verification paths location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -227,8 +229,8 @@ server { # AI skills paths location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -240,8 +242,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -253,8 +255,8 @@ server { # Skill manifest location = /skill.md { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -266,8 +268,8 @@ server { # LLM index files location = /llms.txt { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -277,8 +279,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -292,8 +294,8 @@ server { # subpath so Mintlify receives the root path it expects. # # location = /help/llms.txt { - # proxy_pass https://.mintlify.app/llms.txt; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -302,8 +304,8 @@ server { # } # # location = /help/llms-full.txt { - # proxy_pass https://.mintlify.app/llms-full.txt; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -312,8 +314,8 @@ server { # } # # location = /help/skill.md { - # proxy_pass https://.mintlify.app/skill.md; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -323,8 +325,8 @@ server { # Static assets with caching location ~ ^/mintlify-assets/_next/static/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -336,8 +338,8 @@ server { # Mintlify-specific paths location ~ ^/_mintlify/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -349,8 +351,8 @@ server { # Root path location = / { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -362,8 +364,8 @@ server { # All other documentation paths location / { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -381,9 +383,9 @@ server { **Symptoms**: You publish documentation updates, but the changes don't appear on your site. -**Cause**: You have **Host at `/docs`** enabled in your dashboard but your reverse proxy points to `mintlify.app` instead of `mintlify.dev`. +**Cause**: Your reverse proxy points to an outdated hostname. -**Solution**: Update your reverse proxy configuration to point to `.mintlify.dev` instead of `.mintlify.app`. +**Solution**: Update your reverse proxy configuration to point to `.mintlify.site`. ### 404 error @@ -394,7 +396,7 @@ server { **Solution**: - Remove `Host` header forwarding -- Set `Origin` header to your Mintlify subdomain (`mintlify.dev` for a `/docs` subpath or `mintlify.app` for a different subpath) +- Set the `Origin` header to your Mintlify subdomain (`.mintlify.site`) ### Performance issues diff --git a/deploy/route53-cloudfront.mdx b/deploy/route53-cloudfront.mdx index da84a9e109..7e6609af9d 100644 --- a/deploy/route53-cloudfront.mdx +++ b/deploy/route53-cloudfront.mdx @@ -36,10 +36,10 @@ All Behaviors must have an **origin request policy** of `AllViewerExceptHostHead ![CloudFront Distributions page with the "Create distribution" button emphasized.](/images/cloudfront/create-distribution.png) -3. For the Origin domain, input `[SUBDOMAIN].mintlify.dev` 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.mintlify.dev" 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. @@ -73,7 +73,7 @@ All Behaviors must have an **origin request policy** of `AllViewerExceptHostHead ![CloudFront "Create origin" page with a "Origin domain" input field highlighted.](/images/cloudfront/default-origin.png) -By this point, you should have two Origins: one with `[SUBDOMAIN].mintlify.app` and another with your staging URL. +By this point, you should 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) @@ -83,7 +83,7 @@ By this point, you should have two Origins: one with `[SUBDOMAIN].mintlify.app` 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].mintlify.dev`. +- **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. @@ -112,19 +112,19 @@ If `.well-known/*` is too generic, it can be narrowed down to 2 behaviors at a m ### Your subpath -Create a behavior with a **Path pattern** of your chosen subpath, for example `/docs`, with **Origin and origin groups** pointing to the `.mintlify.dev` URL (for example, `acme.mintlify.dev`). +Create a behavior with a **Path pattern** of your chosen subpath, for example `/docs`, with **Origin and origin groups** pointing to the `.mintlify.site` URL (for example, `acme.mintlify.site`). - Set "Cache policy" to **CachingOptimized**. - Set "Origin request policy" to **AllViewerExceptHostHeader**. - Set Viewer Protocol Policy to **Redirect HTTP to HTTPS** - ![CloudFront "Create behavior" page with a "Path pattern" of "/docs/*" and "Origin and origin groups" pointing to the `acme.mintlify.dev` 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 `.mintlify.dev` 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**. diff --git a/deploy/vercel.mdx b/deploy/vercel.mdx index e3de3e9124..bf9d856918 100644 --- a/deploy/vercel.mdx +++ b/deploy/vercel.mdx @@ -15,7 +15,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.mintlify.dev/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 @@ -36,11 +36,11 @@ Rewrites map incoming requests to different destinations without changing the UR "rewrites": [ { "source": "/docs", - "destination": "https://[subdomain].mintlify.dev/docs" + "destination": "https://[subdomain].mintlify.site/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlify.dev/docs/:match*" + "destination": "https://[subdomain].mintlify.site/docs/:match*" } ] } diff --git a/es/deploy/cloudflare.mdx b/es/deploy/cloudflare.mdx index 97e35ff340..66ac3a5128 100644 --- a/es/deploy/cloudflare.mdx +++ b/es/deploy/cloudflare.mdx @@ -76,7 +76,7 @@ async function handleRequest(request) { // Si la solicitud es al subpath de docs if (/^\/docs/.test(urlObject.pathname)) { // Entonces hacer proxy a Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.site"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); @@ -169,7 +169,7 @@ Si usas Webflow para alojar tu sitio principal y quieres servir la documentació // Si la solicitud es al subdirectorio de documentación if (/^\/docs/.test(urlObject.pathname)) { // Proxy a Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.site"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); url.hostname = DOCS_URL; diff --git a/es/deploy/csp-configuration.mdx b/es/deploy/csp-configuration.mdx index f6b2373d25..ef94ae42a4 100644 --- a/es/deploy/csp-configuration.mdx +++ b/es/deploy/csp-configuration.mdx @@ -28,7 +28,7 @@ Las siguientes directivas de CSP controlan qué recursos puede cargar una págin | Dominio | Propósito | Directiva CSP | Obligatorio | |:-------|:--------|:--------------|:-------| | `d4tuoctqmanu0.cloudfront.net` | CSS y fuentes de KaTeX | `style-src`, `font-src` | Obligatorio | -| `*.mintlify.dev` | Contenido de la documentación | `connect-src`, `frame-src` | Obligatorio | +| `*.mintlify.site` | Contenido de la documentación | `connect-src`, `frame-src` | Obligatorio | | `*.mintlify.com` | Dashboard, API, proxy de Analytics | `connect-src` | Obligatorio | | `leaves.mintlify.com` | API del assistant | `connect-src` | Obligatorio | | `d3gk2c5xim1je2.cloudfront.net` | Íconos, imágenes, logotipos | `img-src` | Obligatorio | @@ -68,9 +68,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' *.mintlify.dev *.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' *.mintlify.dev hcaptcha.com *.hcaptcha.com; +frame-src 'self' *.mintlify.site hcaptcha.com *.hcaptcha.com; ``` @@ -94,7 +94,7 @@ Crea una regla de transformación de encabezados de respuesta: - **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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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. Publica la regla. @@ -112,7 +112,7 @@ Agrega una política de encabezados de respuesta en 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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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 } } @@ -136,7 +136,7 @@ Agrega en tu `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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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/es/deploy/reverse-proxy.mdx b/es/deploy/reverse-proxy.mdx index e39adab9ee..9c0fe85663 100644 --- a/es/deploy/reverse-proxy.mdx +++ b/es/deploy/reverse-proxy.mdx @@ -14,8 +14,10 @@ Al implementar un proxy inverso, supervisa posibles problemas con la verificaci Mintlify admite dos configuraciones de proxy inverso en función de tus requisitos de subruta. -- **Alojar en `/docs`**: Usa `mintlify.dev` como destino del proxy. Activa la opción **Host at `/docs`** en la página [Custom domain setup](https://dashboard.mintlify.com/settings/deployment/custom-domain) de tu dashboard. Esta es una configuración más sencilla con menos rutas. -- **Subruta personalizada**: Usa `mintlify.app` como destino del proxy. Este enfoque admite cualquier subruta y requiere reglas de enrutamiento adicionales. +- **Alojar en `/docs`**: Activa la opción **Host at `/docs`** en la página [Custom domain setup](https://dashboard.mintlify.com/settings/deployment/custom-domain) de tu dashboard. Esta es una configuración más sencilla con menos rutas. +- **Subruta personalizada**: Usa cualquier subruta que elijas. Este enfoque requiere reglas de enrutamiento adicionales. + +En ambas configuraciones, usa `mintlify.site` como destino del proxy.
## Hospedar en la subruta `/docs` @@ -30,7 +32,7 @@ Antes de configurar tu proxy inverso: 3. Ingresa tu domain y selecciona **Add domain**. - Cuando activas **Host at `/docs`**, la URL canónica de tu documentación se convierte en `.mintlify.dev`. La invalidación de caché se detiene en `mintlify.app` y debes dirigir el proxy a `mintlify.dev` para que aparezcan las actualizaciones. + Cuando activas **Host at `/docs`**, la URL canónica de tu documentación se convierte en `.mintlify.site/docs`. Dirige el proxy a `.mintlify.site` para que la invalidación de caché y las actualizaciones surtan efecto.
@@ -41,14 +43,14 @@ Encamina (proxy) estas rutas a tu subdomain de Mintlify: | Ruta | Destino | Caché | | --------------------------------- | ----------------------------------- | -------- | -| `/docs` | `.mintlify.dev/docs` | Sin caché | -| `/docs/*` | `.mintlify.dev/docs` | Sin caché | -| `/.well-known/vercel/*` | `.mintlify.dev` | Sin caché | -| `/.well-known/skills/*` (opcional) | `.mintlify.dev/docs` | Sin caché | -| `/.well-known/agent-skills/*` (opcional) | `.mintlify.dev/docs` | Sin caché | -| `/skill.md` (opcional) | `.mintlify.dev/docs` | Sin caché | -| `/llms.txt` (opcional) | `.mintlify.dev/docs` | Sin caché | -| `/llms-full.txt` (opcional) | `.mintlify.dev/docs` | Sin caché | +| `/docs` | `.mintlify.site/docs` | Sin caché | +| `/docs/*` | `.mintlify.site/docs` | Sin caché | +| `/.well-known/vercel/*` | `.mintlify.site` | Sin caché | +| `/.well-known/skills/*` (opcional) | `.mintlify.site/docs` | Sin caché | +| `/.well-known/agent-skills/*` (opcional) | `.mintlify.site/docs` | Sin caché | +| `/skill.md` (opcional) | `.mintlify.site/docs` | Sin caché | +| `/llms.txt` (opcional) | `.mintlify.site/docs` | Sin caché | +| `/llms-full.txt` (opcional) | `.mintlify.site/docs` | Sin caché | Las rutas `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, `/llms.txt` y `/llms-full.txt` son opcionales. Inclúyelas solo si quieres servir archivos de IA en rutas raíz como `your-domain.com/llms.txt` en lugar de en tu subruta de documentación, como `your-domain.com/docs/llms.txt`. @@ -56,7 +58,7 @@ Las rutas `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, ` Configura tu proxy inverso con estos requisitos de encabezados: -* **Origin**: Contiene el subdomain de destino `.mintlify.dev` +* **Origin**: Contiene el subdomain de destino `.mintlify.site` * **X-Forwarded-For**: Conserva la información de la IP del cliente * **X-Forwarded-Proto**: Conserva el protocolo original (HTTP/HTTPS) * **X-Real-IP**: Reenvía la dirección IP real del cliente @@ -77,8 +79,8 @@ server { # Rutas de verificación de Vercel location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.dev; - proxy_set_header Origin .mintlify.dev; + 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; @@ -89,8 +91,8 @@ server { # Rutas de habilidades de IA location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -101,8 +103,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -113,8 +115,8 @@ server { # Manifiesto de habilidad (opcional) location = /skill.md { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -125,8 +127,8 @@ server { # Archivos de índice LLM (opcional) location = /llms.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -136,8 +138,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -148,8 +150,8 @@ server { # Raíz de la documentación location = /docs { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -160,8 +162,8 @@ server { # Todas las rutas de la documentación location /docs/ { - proxy_pass https://.mintlify.dev/docs/; - proxy_set_header Origin .mintlify.dev; + 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; @@ -187,16 +189,16 @@ Encamina estas rutas a tu subdomain de Mintlify con las políticas de caché esp | Ruta | Destino | Caché | | --------------------------------- | ------------------------------- | ---------------- | -| `/.well-known/vercel/*` | `.mintlify.app` | Sin caché | -| `/.well-known/skills/*` | `.mintlify.app` | Sin caché | -| `/.well-known/agent-skills/*` | `.mintlify.app` | Sin caché | -| `/skill.md` | `.mintlify.app` | Sin caché | -| `/llms.txt` | `.mintlify.app` | Sin caché | -| `/llms-full.txt` | `.mintlify.app` | Sin caché | -| `/mintlify-assets/_next/static/*` | `.mintlify.app` | Caché habilitada | -| `/_mintlify/*` | `.mintlify.app` | Sin caché | -| `/*` | `.mintlify.app` | Sin caché | -| `/` | `.mintlify.app` | Sin caché | +| `/.well-known/vercel/*` | `.mintlify.site` | Sin caché | +| `/.well-known/skills/*` | `.mintlify.site` | Sin caché | +| `/.well-known/agent-skills/*` | `.mintlify.site` | Sin caché | +| `/skill.md` | `.mintlify.site` | Sin caché | +| `/llms.txt` | `.mintlify.site` | Sin caché | +| `/llms-full.txt` | `.mintlify.site` | Sin caché | +| `/mintlify-assets/_next/static/*` | `.mintlify.site` | Caché habilitada | +| `/_mintlify/*` | `.mintlify.site` | Sin caché | +| `/*` | `.mintlify.site` | Sin caché | +| `/` | `.mintlify.site` | Sin caché | Mintlify sirve `llms.txt`, `llms-full.txt` y `skill.md` en la ruta raíz. Si tu documentación se encuentra en una subruta (como `/help`), también puedes servir estos archivos desde esa subruta (por ejemplo, `/help/llms.txt`). Para ello, agrega bloques location que reescriban la subruta a la ruta raíz. Consulta el ejemplo de nginx a continuación para ambos patrones. @@ -208,7 +210,7 @@ Encamina estas rutas a tu subdomain de Mintlify con las políticas de caché esp Configura tu proxy inverso con estos requisitos de encabezados: -- **Origin**: Contiene el subdomain de destino `.mintlify.app` +- **Origin**: Contiene el subdomain de destino `.mintlify.site` - **X-Forwarded-For**: Conserva la información de la IP del cliente - **X-Forwarded-Proto**: Conserva el protocolo original (HTTP/HTTPS) - **X-Real-IP**: Reenvía la dirección IP real del cliente @@ -229,8 +231,8 @@ server { # Vercel verification paths location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -242,8 +244,8 @@ server { # AI skills paths location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -255,8 +257,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -268,8 +270,8 @@ server { # Skill manifest location = /skill.md { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -281,8 +283,8 @@ server { # Archivos de índice LLM location = /llms.txt { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -292,8 +294,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -307,8 +309,8 @@ server { # subruta para que Mintlify reciba la ruta raíz que espera. # # location = /help/llms.txt { - # proxy_pass https://.mintlify.app/llms.txt; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -317,8 +319,8 @@ server { # } # # location = /help/llms-full.txt { - # proxy_pass https://.mintlify.app/llms-full.txt; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -327,8 +329,8 @@ server { # } # # location = /help/skill.md { - # proxy_pass https://.mintlify.app/skill.md; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -338,8 +340,8 @@ server { # Static assets with caching location ~ ^/mintlify-assets/_next/static/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -351,8 +353,8 @@ server { # Mintlify-specific paths location ~ ^/_mintlify/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -364,8 +366,8 @@ server { # Root path location = / { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -377,8 +379,8 @@ server { # All other documentation paths location / { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -401,9 +403,9 @@ server { **Síntomas**: Publicas actualizaciones de la documentación, pero los cambios no aparecen en tu sitio. -**Causa**: Tienes **Host at `/docs`** activado en tu dashboard, pero tu proxy inverso apunta a `mintlify.app` en lugar de `mintlify.dev`. +**Causa**: Tu proxy inverso apunta a un nombre de host obsoleto. -**Solución**: Actualiza la configuración de tu proxy inverso para que apunte a `.mintlify.dev` en lugar de `.mintlify.app`. +**Solución**: Actualiza la configuración de tu proxy inverso para que apunte a `.mintlify.site`.
### Error 404 @@ -416,7 +418,7 @@ server { **Solución**: - Elimina el reenvío del encabezado `Host` -- Configura el encabezado `Origin` en tu subdominio de Mintlify (`mintlify.dev` para una subruta `/docs` o `mintlify.app` para una subruta diferente) +- Configura el encabezado `Origin` en tu subdominio de Mintlify (`.mintlify.site`)
### Problemas de rendimiento diff --git a/es/deploy/route53-cloudfront.mdx b/es/deploy/route53-cloudfront.mdx index d65460e0fd..a9429fb369 100644 --- a/es/deploy/route53-cloudfront.mdx +++ b/es/deploy/route53-cloudfront.mdx @@ -41,10 +41,10 @@ Todos los comportamientos (Behaviors) deben tener una **origin request policy** ![Página de CloudFront Distributions con el botón «Create distribution» resaltado.](/images/cloudfront/create-distribution.png) -3. En Origin domain, ingresa `[SUBDOMAIN].mintlify.dev`, donde `[SUBDOMAIN]` es el subdomain único de tu proyecto. +3. En Origin domain, ingresa `[SUBDOMAIN].mintlify.site`, donde `[SUBDOMAIN]` es el subdomain único de tu proyecto. - ![Página «Create distribution» de CloudFront mostrando «acme.mintlify.dev» como Origin domain.](/images/cloudfront/origin-name.png) + ![Página «Create distribution» de CloudFront mostrando «acme.mintlify.site» como Origin domain.](/images/cloudfront/origin-name.png) 4. En «Web Application Firewall (WAF)», habilita las protecciones de seguridad. @@ -80,7 +80,7 @@ Todos los comportamientos (Behaviors) deben tener una **origin request policy** ![Página de CloudFront "Create origin" con el campo de entrada "Origin domain" resaltado.](/images/cloudfront/default-origin.png) -A este punto, deberías tener dos Origins: uno con `[SUBDOMAIN].mintlify.app` y otro con tu URL de staging. +A este punto, deberías tener dos Origins: uno con `[SUBDOMAIN].mintlify.site` y otro con tu URL de staging. ![Página de CloudFront "Origins" con dos orígenes: uno para mintlify y otro para mintlify-landing-page.](/images/cloudfront/final-origins.png) @@ -92,7 +92,7 @@ A este punto, deberías tener dos Origins: uno con `[SUBDOMAIN].mintlify.app` y Los comportamientos en CloudFront permiten controlar la lógica de subrutas. A grandes rasgos, queremos implementar la siguiente lógica: -- **Si un usuario llega a tu subruta personalizada**, redirigir a `[SUBDOMAIN].mintlify.dev`. +- **Si un usuario llega a tu subruta personalizada**, redirigir a `[SUBDOMAIN].mintlify.site`. - **Si un usuario llega a cualquier otra página**, redirigir a la página de inicio actual. 1. Ve a la pestaña "Behaviors" de tu distribución de CloudFront. @@ -125,21 +125,21 @@ Si `.well-known/*` es demasiado genérico, puede acotarse a un mínimo de 2 comp ### Tu subruta
-Crea un comportamiento con un **Path pattern** de la subruta que elijas, por ejemplo `/docs`, con **Origin and origin groups** apuntando a la URL `.mintlify.dev` (en nuestro caso `acme.mintlify.dev`). +Crea un comportamiento con un **Path pattern** de la subruta que elijas, por ejemplo `/docs`, con **Origin and origin groups** apuntando a la URL `.mintlify.site` (en nuestro caso `acme.mintlify.site`). - Establece "Cache policy" en **CachingOptimized**. - Establece "Origin request policy" en **AllViewerExceptHostHeader**. - Establece "Viewer protocol policy" en **Redirect HTTP to HTTPS**. - ![Página "Create behavior" de CloudFront con un "Path pattern" de "/docs/*" y "Origin and origin groups" apuntando a la URL `acme.mintlify.dev`.](/images/cloudfront/behavior-1.png) + ![Página "Create behavior" de CloudFront con un "Path pattern" de "/docs/*" y "Origin and origin groups" apuntando a la URL `acme.mintlify.site`.](/images/cloudfront/behavior-1.png)
### Tu subruta con comodín
-Crea un comportamiento con un **Path pattern** que sea la subruta que elijas seguida de `/*`, por ejemplo `/docs/*`, y con **Origin and origin groups** apuntando a la misma URL `.mintlify.dev`. +Crea un comportamiento con un **Path pattern** que sea la subruta que elijas seguida de `/*`, por ejemplo `/docs/*`, y con **Origin and origin groups** apuntando a la misma URL `.mintlify.site`. Esta configuración debe coincidir exactamente con el comportamiento de tu subruta base, con la excepción de **Path pattern**. diff --git a/es/deploy/vercel.mdx b/es/deploy/vercel.mdx index 81d21d3359..61c4705370 100644 --- a/es/deploy/vercel.mdx +++ b/es/deploy/vercel.mdx @@ -18,7 +18,7 @@ El archivo `vercel.json` configura cómo se compila e implementa tu proyecto. Se Usamos la configuración de `rewrites` en tu archivo `vercel.json` para enrutar las solicitudes desde tu dominio principal hacia tu documentación mediante un proxy. -Las reglas de reescritura (rewrites) asignan las solicitudes entrantes a distintos destinos sin cambiar la URL en el navegador. Cuando alguien visita `yoursite.com/docs`, Vercel obtiene internamente el contenido desde `your-subdomain.mintlify.dev/docs`, pero el usuario sigue viendo `yoursite.com/docs` en su navegador. Esto es diferente de las redirecciones, que envían a los usuarios a otra URL por completo. +Las reglas de reescritura (rewrites) asignan las solicitudes entrantes a distintos destinos sin cambiar la URL en el navegador. Cuando alguien visita `yoursite.com/docs`, Vercel obtiene internamente el contenido desde `your-subdomain.mintlify.site/docs`, pero el usuario sigue viendo `yoursite.com/docs` en su navegador. Esto es diferente de las redirecciones, que envían a los usuarios a otra URL por completo.
## Configuración @@ -43,11 +43,11 @@ Las reglas de reescritura (rewrites) asignan las solicitudes entrantes a distint "rewrites": [ { "source": "/docs", - "destination": "https://[subdomain].mintlify.dev/docs" + "destination": "https://[subdomain].mintlify.site/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlify.dev/docs/:match*" + "destination": "https://[subdomain].mintlify.site/docs/:match*" } ] } diff --git a/es/quickstart.mdx b/es/quickstart.mdx index 23065d9808..98a8e406b7 100644 --- a/es/quickstart.mdx +++ b/es/quickstart.mdx @@ -42,7 +42,7 @@ Luego agrega el servidor de Model Context Protocol (MCP) de Mintlify para accede Ve a [mintlify.com/start](https://mintlify.com/start) y completa el proceso de configuración inicial. Durante la configuración, conectarás tu cuenta de GitHub, crearás o seleccionarás un repositorio para tu documentación e instalarás la Aplicación de GitHub para habilitar las implementaciones automáticas. -Después de la configuración inicial, tu sitio de documentación se implementa y queda accesible en tu URL `.mintlify.app`. +Después de la configuración inicial, tu sitio de documentación se implementa y queda accesible en tu URL `.mintlify.site`. @@ -56,7 +56,7 @@ Después de la configuración inicial, tu sitio de documentación se implementa ## Consulta tu sitio desplegado
-Tu sitio de documentación ya se ha desplegado en `https://.mintlify.app`. +Tu sitio de documentación ya se ha desplegado en `https://.mintlify.site`. Encuentra tu URL exacta en la página **Overview** de tu [Dashboard de Mintlify](https://dashboard.mintlify.com/). diff --git a/es/what-is-mintlify.mdx b/es/what-is-mintlify.mdx index 7688e2961b..ad8db04cc0 100644 --- a/es/what-is-mintlify.mdx +++ b/es/what-is-mintlify.mdx @@ -14,7 +14,7 @@ Mintlify aloja tu contenido como un sitio web. Tu contenido se almacena en un re **El Dashboard de Mintlify** se conecta a tu repositorio y te permite gestionar tu sitio. Úsalo para supervisar las implementaciones, configurar los ajustes, gestionar a tu equipo y editar contenido directamente en el navegador. -**Tu sitio**, impulsado por Mintlify. Mintlify construye tu sitio a partir de tu repositorio y lo implementa en una URL `.mintlify.app` de forma predeterminada. Cuando estés listo, puedes asignar un dominio personalizado a tu sitio. +**Tu sitio**, impulsado por Mintlify. Mintlify construye tu sitio a partir de tu repositorio y lo implementa en una URL `.mintlify.site` de forma predeterminada. Cuando estés listo, puedes asignar un dominio personalizado a tu sitio. ```mermaid flowchart LR diff --git a/fr/deploy/cloudflare.mdx b/fr/deploy/cloudflare.mdx index 4952d68072..f797cc84d1 100644 --- a/fr/deploy/cloudflare.mdx +++ b/fr/deploy/cloudflare.mdx @@ -76,7 +76,7 @@ async function handleRequest(request) { // Si la requête concerne le sous-chemin docs if (/^\/docs/.test(urlObject.pathname)) { // Alors rediriger via proxy vers Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.site"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); @@ -169,7 +169,7 @@ Si vous utilisez Webflow pour héberger votre site principal et que vous souhait // Si la requête concerne le sous-chemin docs if (/^\/docs/.test(urlObject.pathname)) { // Proxy vers Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.site"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); url.hostname = DOCS_URL; diff --git a/fr/deploy/csp-configuration.mdx b/fr/deploy/csp-configuration.mdx index 7171d45b68..9d9ffbfc5b 100644 --- a/fr/deploy/csp-configuration.mdx +++ b/fr/deploy/csp-configuration.mdx @@ -28,7 +28,7 @@ Les directives CSP suivantes contrôlent quelles ressources une page peut charge | Domaine | Finalité | Directive CSP | Obligatoire | |:-------|:--------|:--------------|:-------| | `d4tuoctqmanu0.cloudfront.net` | CSS et polices KaTeX | `style-src`, `font-src` | Obligatoire | -| `*.mintlify.dev` | Contenu de la documentation | `connect-src`, `frame-src` | Obligatoire | +| `*.mintlify.site` | Contenu de la documentation | `connect-src`, `frame-src` | Obligatoire | | `*.mintlify.com` | Dashboard, API, proxy d’Analytics | `connect-src` | Obligatoire | | `leaves.mintlify.com` | API Assistant | `connect-src` | Obligatoire | | `d3gk2c5xim1je2.cloudfront.net` | Icônes, images, logos | `img-src` | Obligatoire | @@ -68,9 +68,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' *.mintlify.dev *.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' *.mintlify.dev hcaptcha.com *.hcaptcha.com; +frame-src 'self' *.mintlify.site hcaptcha.com *.hcaptcha.com; ``` @@ -94,7 +94,7 @@ Créez une règle de transformation des en-têtes de réponse : - **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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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. Déployez la règle. @@ -112,7 +112,7 @@ Ajoutez une stratégie d’en-têtes de réponse dans 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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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 } } @@ -136,7 +136,7 @@ Ajoutez ceci à votre `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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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/fr/deploy/reverse-proxy.mdx b/fr/deploy/reverse-proxy.mdx index 7f7785fba6..d3d1967bd1 100644 --- a/fr/deploy/reverse-proxy.mdx +++ b/fr/deploy/reverse-proxy.mdx @@ -14,8 +14,10 @@ Lorsque vous mettez en place un proxy inverse, surveillez les problèmes potenti Mintlify prend en charge deux configurations de proxy inverse en fonction de vos exigences en matière de sous-chemin. -- **Héberger sur `/docs`** : utilisez `mintlify.dev` comme cible du proxy. Activez le bouton **Héberger sur `/docs`** sur la page [Configuration du domaine personnalisé](https://dashboard.mintlify.com/settings/deployment/custom-domain) de votre Dashboard. Il s’agit d’une configuration plus simple avec moins de routes. -- **Sous-chemin personnalisé** : utilisez `mintlify.app` comme cible du proxy. Cette approche prend en charge n’importe quel sous-chemin et nécessite des règles de routage supplémentaires. +- **Héberger sur `/docs`** : Activez le bouton **Héberger sur `/docs`** sur la page [Configuration du domaine personnalisé](https://dashboard.mintlify.com/settings/deployment/custom-domain) de votre Dashboard. Il s’agit d’une configuration plus simple avec moins de routes. +- **Sous-chemin personnalisé** : utilisez n’importe quel sous-chemin de votre choix. Cette approche nécessite des règles de routage supplémentaires. + +Dans les deux configurations, utilisez `mintlify.site` comme cible du proxy.
## Héberger sur le sous-chemin `/docs` @@ -30,7 +32,7 @@ Avant de configurer votre reverse proxy : 3. Saisissez votre domaine et sélectionnez **Add domain**. - Lorsque vous activez **Host at `/docs`**, l’URL canonique de votre documentation devient `.mintlify.dev`. L’invalidation du cache s’arrête sur `mintlify.app`, et vous devez configurer le proxy vers `mintlify.dev` pour que les mises à jour apparaissent. + Lorsque vous activez **Host at `/docs`**, l’URL canonique de votre documentation devient `.mintlify.site/docs`. Configurez le proxy vers `.mintlify.site` pour que l’invalidation du cache et les mises à jour prennent effet.
@@ -41,14 +43,14 @@ Redirigez ces chemins via un proxy vers votre sous-domaine Mintlify : | Path | Destination | Caching | | --------------------------------- | ------------------------------------ | -------- | -| `/docs` | `.mintlify.dev/docs` | No cache | -| `/docs/*` | `.mintlify.dev/docs` | No cache | -| `/.well-known/vercel/*` | `.mintlify.dev` | No cache | -| `/.well-known/skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/.well-known/agent-skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/skill.md` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms.txt` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms-full.txt` (optional) | `.mintlify.dev/docs` | No cache | +| `/docs` | `.mintlify.site/docs` | No cache | +| `/docs/*` | `.mintlify.site/docs` | No cache | +| `/.well-known/vercel/*` | `.mintlify.site` | No cache | +| `/.well-known/skills/*` (optional) | `.mintlify.site/docs` | No cache | +| `/.well-known/agent-skills/*` (optional) | `.mintlify.site/docs` | No cache | +| `/skill.md` (optional) | `.mintlify.site/docs` | No cache | +| `/llms.txt` (optional) | `.mintlify.site/docs` | No cache | +| `/llms-full.txt` (optional) | `.mintlify.site/docs` | No cache | Les routes `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, `/llms.txt` et `/llms-full.txt` sont facultatives. Ne les incluez que si vous souhaitez servir des fichiers d'IA sur des chemins à la racine comme `your-domain.com/llms.txt` plutôt que sous votre sous-chemin de documentation, par exemple `your-domain.com/docs/llms.txt`. @@ -58,7 +60,7 @@ Les routes `/.well-known/skills/*`, `/.well-known/agent-skills/*`, `/skill.md`, Configurez votre reverse proxy avec les en-têtes suivants : -* **Origin** : contient le sous-domaine cible `.mintlify.dev` +* **Origin** : contient le sous-domaine cible `.mintlify.site` * **X-Forwarded-For** : conserve les informations d’adresse IP du client * **X-Forwarded-Proto** : conserve le protocole d’origine (HTTP/HTTPS) * **X-Real-IP** : transmet la véritable adresse IP du client @@ -79,8 +81,8 @@ server { # Vercel verification paths location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.dev; - proxy_set_header Origin .mintlify.dev; + 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; @@ -91,8 +93,8 @@ server { # AI skills paths location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -103,8 +105,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -115,8 +117,8 @@ server { # Manifeste de compétence (facultatif) location = /skill.md { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -127,8 +129,8 @@ server { # Fichiers d'index LLM (facultatif) location = /llms.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -138,8 +140,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -150,8 +152,8 @@ server { # Documentation root location = /docs { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -162,8 +164,8 @@ server { # All documentation paths location /docs/ { - proxy_pass https://.mintlify.dev/docs/; - proxy_set_header Origin .mintlify.dev; + 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; @@ -189,16 +191,16 @@ Redirigez ces chemins vers votre sous-domaine Mintlify avec les politiques de mi | Chemin | Destination | Mise en cache | | --------------------------------- | ------------------------------- | ------------- | -| `/.well-known/vercel/*` | `.mintlify.app` | Pas de cache | -| `/.well-known/skills/*` | `.mintlify.app` | Pas de cache | -| `/.well-known/agent-skills/*` | `.mintlify.app` | Pas de cache | -| `/skill.md` | `.mintlify.app` | Pas de cache | -| `/llms.txt` | `.mintlify.app` | Pas de cache | -| `/llms-full.txt` | `.mintlify.app` | Pas de cache | -| `/mintlify-assets/_next/static/*` | `.mintlify.app` | Cache activé | -| `/_mintlify/*` | `.mintlify.app` | Pas de cache | -| `/*` | `.mintlify.app` | Pas de cache | -| `/` | `.mintlify.app` | Pas de cache | +| `/.well-known/vercel/*` | `.mintlify.site` | Pas de cache | +| `/.well-known/skills/*` | `.mintlify.site` | Pas de cache | +| `/.well-known/agent-skills/*` | `.mintlify.site` | Pas de cache | +| `/skill.md` | `.mintlify.site` | Pas de cache | +| `/llms.txt` | `.mintlify.site` | Pas de cache | +| `/llms-full.txt` | `.mintlify.site` | Pas de cache | +| `/mintlify-assets/_next/static/*` | `.mintlify.site` | Cache activé | +| `/_mintlify/*` | `.mintlify.site` | Pas de cache | +| `/*` | `.mintlify.site` | Pas de cache | +| `/` | `.mintlify.site` | Pas de cache | Mintlify sert `llms.txt`, `llms-full.txt` et `skill.md` à la racine. Si votre documentation se trouve sous un sous-chemin (comme `/help`), vous pouvez également servir ces fichiers depuis ce sous-chemin (par exemple, `/help/llms.txt`). Pour cela, ajoutez des blocs location qui réécrivent le sous-chemin vers le chemin racine. Consultez l'exemple nginx ci-dessous pour les deux approches. @@ -210,7 +212,7 @@ Redirigez ces chemins vers votre sous-domaine Mintlify avec les politiques de mi Configurez votre reverse proxy avec les en-têtes suivants : -- **Origin** : contient le sous-domaine cible `.mintlify.app` +- **Origin** : contient le sous-domaine cible `.mintlify.site` - **X-Forwarded-For** : conserve les informations d’adresse IP du client - **X-Forwarded-Proto** : conserve le protocole d’origine (HTTP/HTTPS) - **X-Real-IP** : transmet la véritable adresse IP du client @@ -231,8 +233,8 @@ server { # Vercel verification paths location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -244,8 +246,8 @@ server { # AI skills paths location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -257,8 +259,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -270,8 +272,8 @@ server { # Skill manifest location = /skill.md { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -283,8 +285,8 @@ server { # Fichiers d'index LLM location = /llms.txt { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -294,8 +296,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -309,8 +311,8 @@ server { # sous-chemin afin que Mintlify reçoive le chemin racine attendu. # # location = /help/llms.txt { - # proxy_pass https://.mintlify.app/llms.txt; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -319,8 +321,8 @@ server { # } # # location = /help/llms-full.txt { - # proxy_pass https://.mintlify.app/llms-full.txt; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -329,8 +331,8 @@ server { # } # # location = /help/skill.md { - # proxy_pass https://.mintlify.app/skill.md; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -340,8 +342,8 @@ server { # Static assets with caching location ~ ^/mintlify-assets/_next/static/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -353,8 +355,8 @@ server { # Mintlify-specific paths location ~ ^/_mintlify/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -366,8 +368,8 @@ server { # Root path location = / { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -379,8 +381,8 @@ server { # All other documentation paths location / { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -403,9 +405,9 @@ server { **Symptômes** : Vous publiez des mises à jour de la documentation, mais les modifications n'apparaissent pas sur votre site. -**Cause** : Vous avez activé **Host at `/docs`** dans votre Dashboard, mais votre proxy inverse pointe vers `mintlify.app` au lieu de `mintlify.dev`. +**Cause** : Votre proxy inverse pointe vers un nom d’hôte obsolète. -**Solution** : Mettez à jour la configuration de votre proxy inverse pour qu'il pointe vers `.mintlify.dev` au lieu de `.mintlify.app`. +**Solution** : Mettez à jour la configuration de votre proxy inverse pour qu'il pointe vers `.mintlify.site`.
### Erreur 404 @@ -418,7 +420,7 @@ server { **Solution** : - Supprimer le transfert de l’en-tête `Host` -- Définir l’en-tête `Origin` sur votre sous-domaine Mintlify (`mintlify.dev` pour un sous-chemin `/docs` ou `mintlify.app` pour un autre sous-chemin) +- Définir l’en-tête `Origin` sur votre sous-domaine Mintlify (`.mintlify.site`)
### Problèmes de performances diff --git a/fr/deploy/route53-cloudfront.mdx b/fr/deploy/route53-cloudfront.mdx index 0fe8c37dfb..43871c8e92 100644 --- a/fr/deploy/route53-cloudfront.mdx +++ b/fr/deploy/route53-cloudfront.mdx @@ -40,10 +40,10 @@ Tous les Behaviors doivent avoir une **origin request policy** de `AllViewerExce ![Page des distributions CloudFront avec le bouton « Create distribution » mis en évidence.](/images/cloudfront/create-distribution.png) -3. Pour le domaine d’origine, saisissez `[SUBDOMAIN].mintlify.dev`, où `[SUBDOMAIN]` est le sous-domaine propre à votre projet. +3. Pour le domaine d’origine, saisissez `[SUBDOMAIN].mintlify.site`, où `[SUBDOMAIN]` est le sous-domaine propre à votre projet. - ![Page « Create distribution » de CloudFront affichant « acme.mintlify.dev » comme domaine d’origine.](/images/cloudfront/origin-name.png) + ![Page « Create distribution » de CloudFront affichant « acme.mintlify.site » comme domaine d’origine.](/images/cloudfront/origin-name.png) 4. Pour « Web Application Firewall (WAF) », activez les protections de sécurité. @@ -79,7 +79,7 @@ Tous les Behaviors doivent avoir une **origin request policy** de `AllViewerExce ![Page CloudFront « Create origin » avec le champ de saisie « Origin domain » mis en évidence.](/images/cloudfront/default-origin.png) -À ce stade, vous devriez avoir deux Origins : une avec `[SUBDOMAIN].mintlify.app` et une autre avec votre URL de staging. +À ce stade, vous devriez avoir deux Origins : une avec `[SUBDOMAIN].mintlify.site` et une autre avec votre URL de staging. ![Page CloudFront « Origins » avec deux origins : une pour mintlify et une autre pour mintlify-landing-page.](/images/cloudfront/final-origins.png) @@ -91,7 +91,7 @@ Tous les Behaviors doivent avoir une **origin request policy** de `AllViewerExce Les comportements dans CloudFront permettent de contrôler la logique des sous-chemins. Globalement, nous voulons mettre en place la logique suivante : -- **Si un utilisateur arrive sur votre sous-chemin personnalisé**, le rediriger vers `[SUBDOMAIN].mintlify.dev`. +- **Si un utilisateur arrive sur votre sous-chemin personnalisé**, le rediriger vers `[SUBDOMAIN].mintlify.site`. - **Si un utilisateur arrive sur une autre page**, le diriger vers la page d’accueil actuelle. 1. Accédez à l’onglet « Behaviors » de votre distribution CloudFront. @@ -124,21 +124,21 @@ Si `/.well-known/*` est trop générique, vous pouvez le restreindre à au moins ### Votre sous-chemin
-Créez un comportement avec un **Path pattern** défini sur le sous-chemin de votre choix, par exemple `/docs`, avec **Origin and origin groups** pointant vers l’URL `.mintlify.dev` (dans notre cas `acme.mintlify.dev`). +Créez un comportement avec un **Path pattern** défini sur le sous-chemin de votre choix, par exemple `/docs`, avec **Origin and origin groups** pointant vers l’URL `.mintlify.site` (dans notre cas `acme.mintlify.site`). - Définissez « Cache policy » sur **CachingOptimized**. - Définissez « Origin request policy » sur **AllViewerExceptHostHeader**. - Définissez « Viewer Protocol Policy » sur **Redirect HTTP to HTTPS**. - ![Page CloudFront « Create behavior » avec un « Path pattern » de « /docs/* » et « Origin and origin groups » pointant vers l’URL `acme.mintlify.dev`.](/images/cloudfront/behavior-1.png) + ![Page CloudFront « Create behavior » avec un « Path pattern » de « /docs/* » et « Origin and origin groups » pointant vers l’URL `acme.mintlify.site`.](/images/cloudfront/behavior-1.png)
### Votre sous-chemin avec caractère générique
-Créez un comportement avec un **Path pattern** correspondant au sous-chemin de votre choix suivi de `/*`, par exemple `/docs/*`, et des **Origin and origin groups** pointant vers la même URL en `.mintlify.dev`. +Créez un comportement avec un **Path pattern** correspondant au sous-chemin de votre choix suivi de `/*`, par exemple `/docs/*`, et des **Origin and origin groups** pointant vers la même URL en `.mintlify.site`. Ces paramètres doivent correspondre exactement au comportement de votre sous-chemin de base, à l’exception du **Path pattern**. diff --git a/fr/deploy/vercel.mdx b/fr/deploy/vercel.mdx index 1cb1188804..693624978d 100644 --- a/fr/deploy/vercel.mdx +++ b/fr/deploy/vercel.mdx @@ -18,7 +18,7 @@ Le fichier `vercel.json` définit la façon dont votre projet est construit et d Nous utilisons la configuration `rewrites` dans votre fichier `vercel.json` pour faire transiter les requêtes de votre domaine principal vers votre documentation via un proxy. -Les réécritures (`rewrites`) font correspondre les requêtes entrantes à différentes destinations sans modifier l'URL dans le navigateur. Quand quelqu’un visite `yoursite.com/docs`, Vercel récupère en interne le contenu depuis `your-subdomain.mintlify.dev/docs`, mais l’utilisateur voit toujours `yoursite.com/docs` dans son navigateur. Cela diffère des redirections, qui envoient les utilisateurs vers une URL complètement différente. +Les réécritures (`rewrites`) font correspondre les requêtes entrantes à différentes destinations sans modifier l'URL dans le navigateur. Quand quelqu’un visite `yoursite.com/docs`, Vercel récupère en interne le contenu depuis `your-subdomain.mintlify.site/docs`, mais l’utilisateur voit toujours `yoursite.com/docs` dans son navigateur. Cela diffère des redirections, qui envoient les utilisateurs vers une URL complètement différente.
## Configuration @@ -43,11 +43,11 @@ Les réécritures (`rewrites`) font correspondre les requêtes entrantes à diff "rewrites": [ { "source": "/docs", - "destination": "https://[subdomain].mintlify.dev/docs" + "destination": "https://[subdomain].mintlify.site/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlify.dev/docs/:match*" + "destination": "https://[subdomain].mintlify.site/docs/:match*" } ] } diff --git a/fr/quickstart.mdx b/fr/quickstart.mdx index 3988255acf..f38d417ca2 100644 --- a/fr/quickstart.mdx +++ b/fr/quickstart.mdx @@ -42,7 +42,7 @@ Ajoutez ensuite le serveur MCP Mintlify pour accéder à la recherche dans la do Accédez à [mintlify.com/start](https://mintlify.com/start) et suivez le processus d'onboarding. Pendant l'onboarding, vous connectez votre compte GitHub, créez ou sélectionnez un référentiel pour votre documentation et installez la GitHub App afin d'activer les déploiements automatiques. -Après l'onboarding, votre site de documentation est déployé et accessible via l'URL `.mintlify.app` de votre site. +Après l'onboarding, votre site de documentation est déployé et accessible via l'URL `.mintlify.site` de votre site. @@ -56,7 +56,7 @@ Après l'onboarding, votre site de documentation est déployé et accessible via ## Voir votre site déployé
-Votre site de documentation est maintenant déployé à l’adresse `https://.mintlify.app`. +Votre site de documentation est maintenant déployé à l’adresse `https://.mintlify.site`. Trouvez l’URL exacte de votre site sur la page **Overview** de votre [Tableau de bord Mintlify](https://dashboard.mintlify.com/). diff --git a/fr/what-is-mintlify.mdx b/fr/what-is-mintlify.mdx index 1528f3ce32..d7c4917bf0 100644 --- a/fr/what-is-mintlify.mdx +++ b/fr/what-is-mintlify.mdx @@ -14,7 +14,7 @@ Mintlify héberge votre contenu sous la forme d’un site web. Votre contenu se **Le Tableau de bord Mintlify** se connecte à votre référentiel et vous permet de gérer votre site. Utilisez-le pour surveiller les déploiements, configurer les paramètres, gérer votre équipe et modifier le contenu directement dans le navigateur. -**Votre site**, propulsé par Mintlify. Mintlify génère votre site à partir de votre référentiel et le déploie par défaut sous une URL en `.mintlify.app`. Lorsque vous êtes prêt, vous pouvez associer un domaine personnalisé à votre site. +**Votre site**, propulsé par Mintlify. Mintlify génère votre site à partir de votre référentiel et le déploie par défaut sous une URL en `.mintlify.site`. Lorsque vous êtes prêt, vous pouvez associer un domaine personnalisé à votre site. ```mermaid flowchart LR diff --git a/quickstart.mdx b/quickstart.mdx index 1065c1e02e..4fc7601ca7 100644 --- a/quickstart.mdx +++ b/quickstart.mdx @@ -27,7 +27,7 @@ When you connect your documentation repository to your project, you can work on Go to [mintlify.com/start](https://mintlify.com/start) and complete the onboarding process. During onboarding, you'll connect your GitHub account, create or select a repository for your documentation, and install the GitHub App to enable automatic deployments. -After onboarding, your documentation site deploys and is accessible at your `.mintlify.app` URL. +After onboarding, your documentation site deploys and is accessible at your `.mintlify.site` URL. @@ -39,7 +39,7 @@ After onboarding, your documentation site deploys and is accessible at your `.mi ## View your deployed site -Your documentation site is now deployed at `https://.mintlify.app`. +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/what-is-mintlify.mdx b/what-is-mintlify.mdx index 3d8f34725a..399364e461 100644 --- a/what-is-mintlify.mdx +++ b/what-is-mintlify.mdx @@ -12,7 +12,7 @@ Mintlify hosts your content as a website. Your content lives in a Git repository **The Mintlify dashboard** connects to your repository and lets you manage your site. Use it to monitor deployments, configure settings, manage your team, and edit content directly in the browser. -**Your site**, powered by Mintlify. Mintlify builds your site from your repository and deploys it at a `.mintlify.app` URL by default. When you're ready, you can point a custom domain to your site. +**Your site**, powered by Mintlify. Mintlify builds your site from your repository and deploys it at a `.mintlify.site` URL by default. When you're ready, you can point a custom domain to your site. ```mermaid flowchart LR diff --git a/zh/deploy/cloudflare.mdx b/zh/deploy/cloudflare.mdx index 667cce21d4..ce4de4198b 100644 --- a/zh/deploy/cloudflare.mdx +++ b/zh/deploy/cloudflare.mdx @@ -76,7 +76,7 @@ async function handleRequest(request) { // 如果请求是 docs 子路径 if (/^\/docs/.test(urlObject.pathname)) { // 然后代理到 Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.site"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); @@ -169,7 +169,7 @@ async function handleRequest(request) { // 如果请求是文档子路径 if (/^\/docs/.test(urlObject.pathname)) { // 代理到 Mintlify - const DOCS_URL = "[SUBDOMAIN].mintlify.dev"; + const DOCS_URL = "[SUBDOMAIN].mintlify.site"; const CUSTOM_URL = "[YOUR_DOMAIN]"; let url = new URL(request.url); url.hostname = DOCS_URL; diff --git a/zh/deploy/csp-configuration.mdx b/zh/deploy/csp-configuration.mdx index 0971b3e6e6..3b5a006646 100644 --- a/zh/deploy/csp-configuration.mdx +++ b/zh/deploy/csp-configuration.mdx @@ -28,7 +28,7 @@ keywords: ["内容安全策略", "CSP", "指令", "安全标头", "防火墙", " | 域名 | 用途 | CSP 指令 | 是否必需 | |:-------|:--------|:--------------|:-------| | `d4tuoctqmanu0.cloudfront.net` | KaTeX CSS、字体 | `style-src`, `font-src` | 必需 | -| `*.mintlify.dev` | 文档内容 | `connect-src`, `frame-src` | 必需 | +| `*.mintlify.site` | 文档内容 | `connect-src`, `frame-src` | 必需 | | `*.mintlify.com` | 控制台、API、分析代理 | `connect-src` | 必需 | | `leaves.mintlify.com` | AI 助手 API | `connect-src` | 必需 | | `d3gk2c5xim1je2.cloudfront.net` | 图标、图像、徽标 | `img-src` | 必需 | @@ -68,9 +68,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' *.mintlify.dev *.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' *.mintlify.dev hcaptcha.com *.hcaptcha.com; +frame-src 'self' *.mintlify.site hcaptcha.com *.hcaptcha.com; ``` @@ -94,7 +94,7 @@ frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; - **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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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. 部署该规则。 @@ -112,7 +112,7 @@ frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; "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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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 } } @@ -136,7 +136,7 @@ frame-src 'self' *.mintlify.dev hcaptcha.com *.hcaptcha.com; "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' *.mintlify.dev *.mintlify.com d1ctpt7j8wusba.cloudfront.net mintcdn.com *.mintcdn.com hcaptcha.com *.hcaptcha.com; frame-src 'self' *.mintlify.dev 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/zh/deploy/reverse-proxy.mdx b/zh/deploy/reverse-proxy.mdx index 657199ced6..c5c555b6f1 100644 --- a/zh/deploy/reverse-proxy.mdx +++ b/zh/deploy/reverse-proxy.mdx @@ -18,8 +18,10 @@ keywords: ["反向代理配置", "nginx", "代理路由", "请求头转发"] Mintlify 根据你的子路径需求支持两种反向代理配置。 -- **在 `/docs` 下托管**：使用 `mintlify.dev` 作为代理目标。在控制台的 [Custom domain setup](https://dashboard.mintlify.com/settings/deployment/custom-domain) 页面中开启 **Host at `/docs`** 开关。这种方式路由更少，配置更简单。 -- **自定义子路径**：使用 `mintlify.app` 作为代理目标。这种方式支持任意子路径，但需要额外的路由规则。 +- **在 `/docs` 下托管**：在控制台的 [Custom domain setup](https://dashboard.mintlify.com/settings/deployment/custom-domain) 页面中开启 **Host at `/docs`** 开关。这种方式路由更少，配置更简单。 +- **自定义子路径**：使用你选择的任意子路径。这种方式需要额外的路由规则。 + +两种配置都使用 `mintlify.site` 作为代理目标。
## 在 `/docs` 子路径下托管 @@ -34,7 +36,7 @@ Mintlify 根据你的子路径需求支持两种反向代理配置。 3. 输入你的 domain 并选择 **Add domain**。 - 当你启用 **Host at `/docs`** 时，你的文档规范 URL 将变为 `.mintlify.dev`。在 `mintlify.app` 上的缓存失效将停止，你必须将代理指向 `mintlify.dev`，更新才会生效。 + 当你启用 **Host at `/docs`** 时，你的文档规范 URL 将变为 `.mintlify.site/docs`。将代理指向 `.mintlify.site`，缓存失效和更新才会生效。
@@ -45,14 +47,14 @@ Mintlify 根据你的子路径需求支持两种反向代理配置。 | 路径 | 目标地址 | 缓存 | | --------------------------------- | ------------------------------------ | -------- | -| `/docs` | `.mintlify.dev/docs` | No cache | -| `/docs/*` | `.mintlify.dev/docs` | No cache | -| `/.well-known/vercel/*` | `.mintlify.dev` | No cache | -| `/.well-known/skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/.well-known/agent-skills/*` (optional) | `.mintlify.dev/docs` | No cache | -| `/skill.md` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms.txt` (optional) | `.mintlify.dev/docs` | No cache | -| `/llms-full.txt` (optional) | `.mintlify.dev/docs` | No cache | +| `/docs` | `.mintlify.site/docs` | No cache | +| `/docs/*` | `.mintlify.site/docs` | No cache | +| `/.well-known/vercel/*` | `.mintlify.site` | No cache | +| `/.well-known/skills/*` (optional) | `.mintlify.site/docs` | No cache | +| `/.well-known/agent-skills/*` (optional) | `.mintlify.site/docs` | No cache | +| `/skill.md` (optional) | `.mintlify.site/docs` | No cache | +| `/llms.txt` (optional) | `.mintlify.site/docs` | No cache | +| `/llms-full.txt` (optional) | `.mintlify.site/docs` | No cache | `/.well-known/skills/*`、`/.well-known/agent-skills/*`、`/skill.md`、`/llms.txt` 和 `/llms-full.txt` 这些路由是可选的。只有当你希望在站点根路径（例如 `your-domain.com/llms.txt`）而不是在文档子路径下（例如 `your-domain.com/docs/llms.txt`）提供 AI 文件时，才需要包含它们。 @@ -62,7 +64,7 @@ Mintlify 根据你的子路径需求支持两种反向代理配置。 按以下请求头要求配置你的反向代理： -* **Origin**：包含目标子域 `.mintlify.dev` +* **Origin**：包含目标子域 `.mintlify.site` * **X-Forwarded-For**：保留客户端 IP 信息 * **X-Forwarded-Proto**：保留原始协议 (HTTP/HTTPS) * **X-Real-IP**：转发真实的客户端 IP 地址 @@ -83,8 +85,8 @@ server { # Vercel 验证路径 location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.dev; - proxy_set_header Origin .mintlify.dev; + 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 +97,8 @@ server { # AI 技能路径 location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -107,8 +109,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -119,8 +121,8 @@ server { # 技能清单(可选) location = /skill.md { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -131,8 +133,8 @@ server { # LLM 索引文件(可选) location = /llms.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -142,8 +144,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -154,8 +156,8 @@ server { # 文档根路径 location = /docs { - proxy_pass https://.mintlify.dev/docs; - proxy_set_header Origin .mintlify.dev; + 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; @@ -166,8 +168,8 @@ server { # 所有文档路径 location /docs/ { - proxy_pass https://.mintlify.dev/docs/; - proxy_set_header Origin .mintlify.dev; + 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; @@ -189,16 +191,16 @@ server { | Path | Destination | Caching | | --------------------------------- | ------------------------------- | ------------- | -| `/.well-known/vercel/*` | `.mintlify.app` | 不缓存 | -| `/.well-known/skills/*` | `.mintlify.app` | 不缓存 | -| `/.well-known/agent-skills/*` | `.mintlify.app` | 不缓存 | -| `/skill.md` | `.mintlify.app` | 不缓存 | -| `/llms.txt` | `.mintlify.app` | 不缓存 | -| `/llms-full.txt` | `.mintlify.app` | 不缓存 | -| `/mintlify-assets/_next/static/*` | `.mintlify.app` | 启用缓存 | -| `/_mintlify/*` | `.mintlify.app` | 不缓存 | -| `/*` | `.mintlify.app` | 不缓存 | -| `/` | `.mintlify.app` | 不缓存 | +| `/.well-known/vercel/*` | `.mintlify.site` | 不缓存 | +| `/.well-known/skills/*` | `.mintlify.site` | 不缓存 | +| `/.well-known/agent-skills/*` | `.mintlify.site` | 不缓存 | +| `/skill.md` | `.mintlify.site` | 不缓存 | +| `/llms.txt` | `.mintlify.site` | 不缓存 | +| `/llms-full.txt` | `.mintlify.site` | 不缓存 | +| `/mintlify-assets/_next/static/*` | `.mintlify.site` | 启用缓存 | +| `/_mintlify/*` | `.mintlify.site` | 不缓存 | +| `/*` | `.mintlify.site` | 不缓存 | +| `/` | `.mintlify.site` | 不缓存 | Mintlify 在根路径提供 `llms.txt`、`llms-full.txt` 和 `skill.md`。如果你的文档位于子路径下（例如 `/help`），你也可以在该子路径下提供这些文件（例如 `/help/llms.txt`）。为此，请添加 location 块将子路径重写到根路径。请参阅下方的 nginx 示例了解这两种模式。 @@ -210,7 +212,7 @@ server { 按以下请求头要求配置你的反向代理： -- **Origin**：包含目标子域 `.mintlify.app` +- **Origin**：包含目标子域 `.mintlify.site` - **X-Forwarded-For**：保留客户端 IP 信息 - **X-Forwarded-Proto**：保留原始协议（HTTP/HTTPS） - **X-Real-IP**：转发真实的客户端 IP 地址 @@ -229,8 +231,8 @@ server { # Vercel verification paths location ~ ^/\.well-known/vercel/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -242,8 +244,8 @@ server { # AI skills paths location ^~ /.well-known/skills/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -255,8 +257,8 @@ server { # Agent-skills discovery paths location ^~ /.well-known/agent-skills/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -268,8 +270,8 @@ server { # Skill manifest location = /skill.md { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -281,8 +283,8 @@ server { # LLM 索引文件 location = /llms.txt { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -292,8 +294,8 @@ server { } location = /llms-full.txt { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -307,8 +309,8 @@ server { # 使 Mintlify 接收到它期望的根路径。 # # location = /help/llms.txt { - # proxy_pass https://.mintlify.app/llms.txt; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -317,8 +319,8 @@ server { # } # # location = /help/llms-full.txt { - # proxy_pass https://.mintlify.app/llms-full.txt; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -327,8 +329,8 @@ server { # } # # location = /help/skill.md { - # proxy_pass https://.mintlify.app/skill.md; - # proxy_set_header Origin .mintlify.app; + # proxy_pass https://.mintlify.site/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; @@ -338,8 +340,8 @@ server { # Static assets with caching location ~ ^/mintlify-assets/_next/static/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -351,8 +353,8 @@ server { # Mintlify-specific paths location ~ ^/_mintlify/ { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -364,8 +366,8 @@ server { # Root path location = / { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -377,8 +379,8 @@ server { # All other documentation paths location / { - proxy_pass https://.mintlify.app; - proxy_set_header Origin .mintlify.app; + 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; @@ -401,9 +403,9 @@ server { **症状**：你发布了文档更新，但这些更改并没有在你的网站上显示出来。 -**原因**：你在控制台中启用了 **Host at `/docs`**，但你的反向代理指向的是 `mintlify.app` 而不是 `mintlify.dev`。 +**原因**：你的反向代理指向了过时的主机名。 -**解决方案**：将反向代理配置更新为指向 `.mintlify.dev`，而不是 `.mintlify.app`。 +**解决方案**：将反向代理配置更新为指向 `.mintlify.site`。
### 404 错误 @@ -416,7 +418,7 @@ server { **解决方案**： - 停止转发 `Host` 头 -- 将 `Origin` 头设置为你的 Mintlify 子域（对于 `/docs` 子路径使用 `mintlify.dev`，其他子路径使用 `mintlify.app`） +- 将 `Origin` 头设置为你的 Mintlify 子域（`.mintlify.site`）
### 性能问题 diff --git a/zh/deploy/route53-cloudfront.mdx b/zh/deploy/route53-cloudfront.mdx index b868fe6a89..652a2fcb34 100644 --- a/zh/deploy/route53-cloudfront.mdx +++ b/zh/deploy/route53-cloudfront.mdx @@ -40,10 +40,10 @@ import Propagating from "/snippets/zh/custom-subpath-propagating.mdx"; ![CloudFront Distributions 页面，高亮显示 “Create distribution” 按钮。](/images/cloudfront/create-distribution.png) -3. 在 Origin domain 中输入 `[SUBDOMAIN].mintlify.dev`，其中 `[SUBDOMAIN]` 是你项目的唯一子域。 +3. 在 Origin domain 中输入 `[SUBDOMAIN].mintlify.site`，其中 `[SUBDOMAIN]` 是你项目的唯一子域。 - ![CloudFront “Create distribution” 页面显示 “acme.mintlify.dev” 作为 Origin domain。](/images/cloudfront/origin-name.png) + ![CloudFront “Create distribution” 页面显示 “acme.mintlify.site” 作为 Origin domain。](/images/cloudfront/origin-name.png) 4. 在 “Web Application Firewall (WAF)” 中，启用安全防护。 @@ -79,7 +79,7 @@ import Propagating from "/snippets/zh/custom-subpath-propagating.mdx"; ![CloudFront 的 “Create origin” 页面，高亮显示 “Origin domain” 输入框。](/images/cloudfront/default-origin.png) -此时，你应当有两个 Origins：一个为 `[SUBDOMAIN].mintlify.app`，另一个为你的预发布 URL。 +此时，你应当有两个 Origins：一个为 `[SUBDOMAIN].mintlify.site`，另一个为你的预发布 URL。 ![CloudFront 的 “Origins” 页面，包含两个 origins：一个用于 mintlify，另一个用于 mintlify-landing-page。](/images/cloudfront/final-origins.png) @@ -91,7 +91,7 @@ import Propagating from "/snippets/zh/custom-subpath-propagating.mdx"; CloudFront 中的行为用于控制子路径逻辑。总体而言，我们希望实现以下逻辑： -- **如果用户访问你的自定义子路径**，跳转到 `[SUBDOMAIN].mintlify.dev`。 +- **如果用户访问你的自定义子路径**，跳转到 `[SUBDOMAIN].mintlify.site`。 - **如果用户访问其他任意页面**，跳转到当前登录页。 1. 打开 CloudFront 分配的 “Behaviors” 标签页。 @@ -124,21 +124,21 @@ CloudFront 中的行为用于控制子路径逻辑。总体而言，我们希望 ### 你的子路径
-创建一个行为，将 **Path pattern** 设置为你选择的子路径，例如 `/docs`，并将 **Origin and origin groups** 指向 `.mintlify.dev` 的 URL（在我们的示例中为 `acme.mintlify.dev`）。 +创建一个行为，将 **Path pattern** 设置为你选择的子路径，例如 `/docs`，并将 **Origin and origin groups** 指向 `.mintlify.site` 的 URL（在我们的示例中为 `acme.mintlify.site`）。 - 将 "Cache policy" 设置为 **CachingOptimized**。 - 将 "Origin request policy" 设置为 **AllViewerExceptHostHeader**。 - 将 "Viewer Protocol Policy" 设置为 **Redirect HTTP to HTTPS**。 - ![CloudFront 的 "Create behavior" 页面，其中 "Path pattern" 设置为 "/docs/*"，并且 "Origin and origin groups" 指向 `acme.mintlify.dev` 的 URL。](/images/cloudfront/behavior-1.png) + ![CloudFront 的 "Create behavior" 页面，其中 "Path pattern" 设置为 "/docs/*"，并且 "Origin and origin groups" 指向 `acme.mintlify.site` 的 URL。](/images/cloudfront/behavior-1.png)
### 带通配符的子路径
-创建一个行为，在 **Path pattern** 中填写你选择的子路径并在后面添加 `/*`，例如 `/docs/*`，并将 **Origin and origin groups** 指向相同的 `.mintlify.dev` URL。 +创建一个行为，在 **Path pattern** 中填写你选择的子路径并在后面添加 `/*`，例如 `/docs/*`，并将 **Origin and origin groups** 指向相同的 `.mintlify.site` URL。 除 **Path pattern** 外，其余设置应与基础子路径行为完全一致。 diff --git a/zh/deploy/vercel.mdx b/zh/deploy/vercel.mdx index 99d93c22ea..31ac93e5c7 100644 --- a/zh/deploy/vercel.mdx +++ b/zh/deploy/vercel.mdx @@ -18,7 +18,7 @@ import { VercelJsonGenerator } from "/snippets/zh/vercel-json-generator.mdx"; 我们会在你的 `vercel.json` 文件中使用 `rewrites` 配置，将来自主域名的请求代理到你的文档站点。 -Rewrites 会在不更改浏览器中 URL 的情况下，将传入请求映射到不同的目标。当有人访问 `yoursite.com/docs` 时，Vercel 会在内部从 `your-subdomain.mintlify.dev/docs` 获取内容，但用户在浏览器中仍然看到的是 `yoursite.com/docs`。这与重定向不同，后者会将用户直接带到另一个完全不同的 URL。 +Rewrites 会在不更改浏览器中 URL 的情况下，将传入请求映射到不同的目标。当有人访问 `yoursite.com/docs` 时，Vercel 会在内部从 `your-subdomain.mintlify.site/docs` 获取内容，但用户在浏览器中仍然看到的是 `yoursite.com/docs`。这与重定向不同，后者会将用户直接带到另一个完全不同的 URL。
## 配置 @@ -43,11 +43,11 @@ Rewrites 会在不更改浏览器中 URL 的情况下，将传入请求映射到 "rewrites": [ { "source": "/docs", - "destination": "https://[subdomain].mintlify.dev/docs" + "destination": "https://[subdomain].mintlify.site/docs" }, { "source": "/docs/:match*", - "destination": "https://[subdomain].mintlify.dev/docs/:match*" + "destination": "https://[subdomain].mintlify.site/docs/:match*" } ] } diff --git a/zh/quickstart.mdx b/zh/quickstart.mdx index c5b9258e24..d9480ec382 100644 --- a/zh/quickstart.mdx +++ b/zh/quickstart.mdx @@ -40,7 +40,7 @@ npx skills add https://mintlify.com/docs 前往 [mintlify.com/start](https://mintlify.com/start) 并完成初始设置流程。在初始设置过程中，你会连接你的 GitHub 账户，为文档创建或选择一个存储库，并安装 GitHub 应用以启用自动部署。 -完成初始设置后，你的文档站点会部署完成，并可通过你的 `.mintlify.app` URL 访问。 +完成初始设置后，你的文档站点会部署完成，并可通过你的 `.mintlify.site` URL 访问。 @@ -54,7 +54,7 @@ npx skills add https://mintlify.com/docs ## 查看你已部署的网站
-你的文档站点现在已部署在 `https://.mintlify.app`。 +你的文档站点现在已部署在 `https://.mintlify.site`。 在 [控制台](https://dashboard.mintlify.com/) 的 **Overview** 页面中可以找到准确的 URL。 diff --git a/zh/what-is-mintlify.mdx b/zh/what-is-mintlify.mdx index 6f337e2413..5a9aad1171 100644 --- a/zh/what-is-mintlify.mdx +++ b/zh/what-is-mintlify.mdx @@ -14,7 +14,7 @@ Mintlify 会将你的内容托管成一个网站。你的内容以 MDX 文件的 **Mintlify 控制台** 会连接到你的存储库，让你管理你的站点。你可以用它来监控部署、配置设置、管理团队，并在浏览器中直接编辑内容。 -**你的网站**，由 Mintlify 驱动。Mintlify 会从你的存储库构建站点，并默认将其部署到一个 `.mintlify.app` 的 URL。当你准备就绪时，可以将自定义域名指向你的网站。 +**你的网站**，由 Mintlify 驱动。Mintlify 会从你的存储库构建站点，并默认将其部署到一个 `.mintlify.site` 的 URL。当你准备就绪时，可以将自定义域名指向你的网站。 ```mermaid flowchart LR From e5c948854efff0bf9573506f6d3783b25874f269 Mon Sep 17 00:00:00 2001 From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> Date: Fri, 26 Jun 2026 10:43:47 -0700 Subject: [PATCH 2/2] 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 --- ai/skillmd.mdx | 2 +- assistant/use.mdx | 4 ++-- customize/themes.mdx | 18 +++++++++--------- deploy/authentication-setup.mdx | 2 +- discovery-openapi.json | 8 ++++---- editor/branching-and-publishing.mdx | 2 +- es/ai/skillmd.mdx | 2 +- es/assistant/use.mdx | 4 ++-- es/customize/themes.mdx | 18 +++++++++--------- es/deploy/authentication-setup.mdx | 2 +- es/discovery-openapi.json | 8 ++++---- es/editor/branching-and-publishing.mdx | 2 +- es/guides/assistant-embed.mdx | 4 ++-- es/guides/codex.mdx | 2 +- es/guides/help-center.mdx | 2 +- es/integrations/privacy/osano.mdx | 2 +- fr/ai/skillmd.mdx | 2 +- fr/assistant/use.mdx | 4 ++-- fr/customize/themes.mdx | 18 +++++++++--------- fr/deploy/authentication-setup.mdx | 2 +- fr/discovery-openapi.json | 8 ++++---- fr/editor/branching-and-publishing.mdx | 2 +- fr/guides/assistant-embed.mdx | 4 ++-- fr/guides/codex.mdx | 2 +- fr/guides/help-center.mdx | 2 +- fr/integrations/privacy/osano.mdx | 2 +- guides/assistant-embed.mdx | 4 ++-- guides/codex.mdx | 2 +- guides/help-center.mdx | 2 +- integrations/privacy/osano.mdx | 2 +- snippets/es/vercel-json-generator.mdx | 20 ++++++++++---------- snippets/fr/vercel-json-generator.mdx | 20 ++++++++++---------- snippets/vercel-json-generator.mdx | 20 ++++++++++---------- snippets/zh/vercel-json-generator.mdx | 20 ++++++++++---------- zh/ai/skillmd.mdx | 2 +- zh/assistant/use.mdx | 4 ++-- zh/customize/themes.mdx | 18 +++++++++--------- zh/deploy/authentication-setup.mdx | 2 +- zh/discovery-openapi.json | 8 ++++---- zh/editor/branching-and-publishing.mdx | 2 +- zh/editor/collaborate.mdx | 2 +- zh/guides/assistant-embed.mdx | 4 ++-- zh/guides/codex.mdx | 2 +- zh/guides/help-center.mdx | 2 +- zh/integrations/privacy/osano.mdx | 2 +- 45 files changed, 133 insertions(+), 133 deletions(-) diff --git a/ai/skillmd.mdx b/ai/skillmd.mdx index cb3340cf46..ff4d19c764 100644 --- a/ai/skillmd.mdx +++ b/ai/skillmd.mdx @@ -211,7 +211,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 `*.mintlify.app` 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 fabdac8b7b..b40a787f04 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.mintlify.app/quickstart?assistant -https://yourdocs.mintlify.app/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/customize/themes.mdx b/customize/themes.mdx index fc189edea2..36700fe30b 100644 --- a/customize/themes.mdx +++ b/customize/themes.mdx @@ -40,23 +40,23 @@ export const ThemeCard = ({ title, value, description, href }) => {
- + - + - + - + - + - + - + - + - +
diff --git a/deploy/authentication-setup.mdx b/deploy/authentication-setup.mdx index 5d841ede69..a811636a18 100644 --- a/deploy/authentication-setup.mdx +++ b/deploy/authentication-setup.mdx @@ -14,7 +14,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 are protected. -Authentication is only available for sites hosted on a custom domain or Mintlify subdomain. For example, `docs.example.com` or `example.mintlify.app`. 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`. ## Configure authentication diff --git a/discovery-openapi.json b/discovery-openapi.json index 89c64242e9..54bed9baa2 100644 --- a/discovery-openapi.json +++ b/discovery-openapi.json @@ -28,7 +28,7 @@ "schema": { "type": "string" }, - "description": "The domain identifier from your `domain.mintlify.app` 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.mintlify.app` 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.mintlify.app` 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": { @@ -831,7 +831,7 @@ "schema": { "type": "string" }, - "description": "The domain identifier from your `domain.mintlify.app` 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/branching-and-publishing.mdx b/editor/branching-and-publishing.mdx index 4c68e025b9..c00c289bde 100644 --- a/editor/branching-and-publishing.mdx +++ b/editor/branching-and-publishing.mdx @@ -84,7 +84,7 @@ Every time you save changes to a feature branch, Mintlify builds a preview deplo ### Access and share a preview 1. Click **Publish** in the editor toolbar. -1. In the publish menu, click the preview URL. The URL format is `organization-branch-name.mintlify.app`. +1. In the publish menu, click the preview URL. The URL format is `organization-branch-name.mintlify.site`. Preview URL emphasized in the publish menu. Preview URL emphasized in the publish menu. diff --git a/es/ai/skillmd.mdx b/es/ai/skillmd.mdx index a26087cb0f..0278a70ece 100644 --- a/es/ai/skillmd.mdx +++ b/es/ai/skillmd.mdx @@ -235,7 +235,7 @@ Los agentes compatibles con A2A obtienen `/.well-known/agent-card.json` para des | `capabilities` | Indicadores de funcionalidades. Actualmente `{ streaming: false, pushNotifications: false }`. | | `skills` | Las skills expuestas en `/.well-known/agent-skills/`. | -Las URL de la tarjeta (`url`, `documentationUrl`, `provider.url` y cada URL de skill) se construyen a partir del dominio personalizado configurado cuando está disponible, de modo que la tarjeta publicada siempre anuncia el dominio canónico en lugar del subdominio `*.mintlify.app`. +Las URL de la tarjeta (`url`, `documentationUrl`, `provider.url` y cada URL de skill) se construyen a partir del dominio personalizado configurado cuando está disponible, de modo que la tarjeta publicada siempre anuncia el dominio canónico en lugar del subdominio `*.mintlify.site`. Si usas un [reverse proxy](/es/deploy/reverse-proxy), configúralo para reenviar `/.well-known/agent-card.json` a tu subdominio de Mintlify. diff --git a/es/assistant/use.mdx b/es/assistant/use.mdx index 1bd71dc6b7..75c55f4944 100644 --- a/es/assistant/use.mdx +++ b/es/assistant/use.mdx @@ -83,8 +83,8 @@ Abre el assistant desde cualquier página de tu sitio de documentación añadien - `?assistant=`: Abre el panel de chat del assistant y envía `` como el primer mensaje del usuario. Codifica el valor en URL para que los espacios y caracteres especiales se conserven en la solicitud. ```text Ejemplos -https://yourdocs.mintlify.app/quickstart?assistant -https://yourdocs.mintlify.app/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 ```
diff --git a/es/customize/themes.mdx b/es/customize/themes.mdx index 77bce2b7dc..3cb5ee9638 100644 --- a/es/customize/themes.mdx +++ b/es/customize/themes.mdx @@ -39,22 +39,22 @@ export const ThemeCard = ({ title, value, description, href }) => {
- + - + - + - + - + - + - + - + - +
diff --git a/es/deploy/authentication-setup.mdx b/es/deploy/authentication-setup.mdx index 9ab2d730e4..6f6c6f2147 100644 --- a/es/deploy/authentication-setup.mdx +++ b/es/deploy/authentication-setup.mdx @@ -14,7 +14,7 @@ La autenticación exige que los usuarios inicien sesión antes de acceder a tu c Puedes configurar autenticación completa para todas las páginas o autenticación parcial en la que algunas páginas son públicas y otras están protegidas. -La autenticación solo está disponible para sitios alojados en un dominio personalizado o subdominio de Mintlify. Por ejemplo, `docs.ejemplo.com` o `ejemplo.mintlify.app`. La autenticación **no es compatible** para sitios con una [subruta personalizada](/es/deploy/docs-subpath). Por ejemplo, `ejemplo.com/docs`. +La autenticación solo está disponible para sitios alojados en un dominio personalizado o subdominio de Mintlify. Por ejemplo, `docs.ejemplo.com` o `ejemplo.mintlify.site`. La autenticación **no es compatible** para sitios con una [subruta personalizada](/es/deploy/docs-subpath). Por ejemplo, `ejemplo.com/docs`.
## Configurar la autenticación diff --git a/es/discovery-openapi.json b/es/discovery-openapi.json index a44967c919..bef9c7155c 100644 --- a/es/discovery-openapi.json +++ b/es/discovery-openapi.json @@ -28,7 +28,7 @@ "schema": { "type": "string" }, - "description": "El identificador de domain de tu URL `domain.mintlify.app`. Se puede encontrar al final de la URL de tu dashboard. Por ejemplo, en `dashboard.mintlify.com/organization/domain`, el identificador de domain es `domain`." + "description": "El identificador de domain de tu URL `domain.mintlify.site`. Se puede encontrar al final de la URL de tu dashboard. Por ejemplo, en `dashboard.mintlify.com/organization/domain`, el identificador de domain es `domain`." } ], "requestBody": { @@ -464,7 +464,7 @@ "schema": { "type": "string" }, - "description": "El identificador de domain de tu URL, por ejemplo `domain.mintlify.app`. Puedes encontrarlo al final de la URL de tu dashboard. Por ejemplo, en `dashboard.mintlify.com/organization/domain`, el identificador de domain es `domain`." + "description": "El identificador de domain de tu URL, por ejemplo `domain.mintlify.site`. Puedes encontrarlo al final de la URL de tu dashboard. Por ejemplo, en `dashboard.mintlify.com/organization/domain`, el identificador de domain es `domain`." } ], "requestBody": { @@ -752,7 +752,7 @@ "schema": { "type": "string" }, - "description": "El identificador domain de tu URL `domain.mintlify.app`. Se encuentra al final de la URL de tu dashboard. Por ejemplo, `dashboard.mintlify.com/organization/domain` tiene un identificador domain de `domain`." + "description": "El identificador domain de tu URL `domain.mintlify.site`. Se encuentra al final de la URL de tu dashboard. Por ejemplo, `dashboard.mintlify.com/organization/domain` tiene un identificador domain de `domain`." } ], "requestBody": { @@ -831,7 +831,7 @@ "schema": { "type": "string" }, - "description": "El identificador domain de tu URL `domain.mintlify.app`. Lo puedes encontrar al final de la URL de tu dashboard. Por ejemplo, `dashboard.mintlify.com/organization/domain` tiene un identificador domain de `domain`." + "description": "El identificador domain de tu URL `domain.mintlify.site`. Lo puedes encontrar al final de la URL de tu dashboard. Por ejemplo, `dashboard.mintlify.com/organization/domain` tiene un identificador domain de `domain`." } ], "requestBody": { diff --git a/es/editor/branching-and-publishing.mdx b/es/editor/branching-and-publishing.mdx index f0e19c298f..6080817056 100644 --- a/es/editor/branching-and-publishing.mdx +++ b/es/editor/branching-and-publishing.mdx @@ -116,7 +116,7 @@ Cada vez que guarda cambios en una feature branch, Mintlify compila un despliegu
1. Haga clic en **Publish** en la barra de herramientas del editor. -1. En el menú de publicación, haga clic en la URL de vista previa. El formato de la URL es `organization-branch-name.mintlify.app`. +1. En el menú de publicación, haga clic en la URL de vista previa. El formato de la URL es `organization-branch-name.mintlify.site`. URL de vista previa destacada en el menú de publicación. URL de vista previa destacada en el menú de publicación. diff --git a/es/guides/assistant-embed.mdx b/es/guides/assistant-embed.mdx index 6af3bb7887..9a76500e05 100644 --- a/es/guides/assistant-embed.mdx +++ b/es/guides/assistant-embed.mdx @@ -80,13 +80,13 @@ Abre `src/config.js` y actualiza los detalles de tu proyecto de Mintlify. ```js src/config.js export const ASSISTANT_CONFIG = { domain: 'your-domain', - docsURL: 'https://yourdocs.mintlify.app', + docsURL: 'https://yourdocs.mintlify.site', }; ``` Reemplaza: - `your-domain` por el domain de tu proyecto de Mintlify que encontrarás al final de la URL de tu dashboard. -- `https://yourdocs.mintlify.app` por la URL real de tu documentación. +- `https://yourdocs.mintlify.site` por la URL real de tu documentación. diff --git a/es/guides/codex.mdx b/es/guides/codex.mdx index d45d5b2ffe..0271a2db86 100644 --- a/es/guides/codex.mdx +++ b/es/guides/codex.mdx @@ -181,7 +181,7 @@ Para conectarte en su lugar al servidor MCP de tu propio sitio de documentación ```toml [mcp_servers.my-docs] -url = "https://your-docs.mintlify.app/mcp" +url = "https://your-docs.mintlify.site/mcp" ``` Consulta [Model Context Protocol](/es/ai/model-context-protocol) para obtener más información sobre los servidores MCP y cómo encontrar el endpoint MCP de tu sitio. diff --git a/es/guides/help-center.mdx b/es/guides/help-center.mdx index 2a28c871b7..5f1e287f62 100644 --- a/es/guides/help-center.mdx +++ b/es/guides/help-center.mdx @@ -24,7 +24,7 @@ La forma más rápida de crear un nuevo centro de ayuda es con el comando `mint mint new your-help-center-name --template help-center-starter ``` -Esto crea un nuevo proyecto preconfigurado para un centro de ayuda, que incluye la estructura de navegación, páginas de ejemplo y listados de directorios. Consulta el [ejemplo en vivo](https://help-center-starter.mintlify.app/) o revisa el [código fuente de la plantilla](https://github.com/mintlify/templates/tree/main/help-center-starter). +Esto crea un nuevo proyecto preconfigurado para un centro de ayuda, que incluye la estructura de navegación, páginas de ejemplo y listados de directorios. Consulta el [ejemplo en vivo](https://help-center-starter.mintlify.site/) o revisa el [código fuente de la plantilla](https://github.com/mintlify/templates/tree/main/help-center-starter). Si prefieres configurar un centro de ayuda en un proyecto existente, continúa con los pasos a continuación. diff --git a/es/integrations/privacy/osano.mdx b/es/integrations/privacy/osano.mdx index badc90900c..8444f65fe0 100644 --- a/es/integrations/privacy/osano.mdx +++ b/es/integrations/privacy/osano.mdx @@ -42,7 +42,7 @@ Reemplaza `OSANO_SCRIPT_URL` con la URL de tu script de Osano. La URL de tu scri - Agrega `.mintlify.app/` como una regla gestionada. + Agrega `.mintlify.site/` como una regla gestionada. Regla gestionada de Osano diff --git a/fr/ai/skillmd.mdx b/fr/ai/skillmd.mdx index 31c022f97c..8daeda7016 100644 --- a/fr/ai/skillmd.mdx +++ b/fr/ai/skillmd.mdx @@ -235,7 +235,7 @@ Les agents compatibles A2A récupèrent `/.well-known/agent-card.json` pour déc | `capabilities` | Indicateurs de fonctionnalités. Actuellement `{ streaming: false, pushNotifications: false }`. | | `skills` | Les skills exposées par `/.well-known/agent-skills/`. | -Les URL de la carte (`url`, `documentationUrl`, `provider.url` et chaque URL de skill) sont construites à partir du domaine personnalisé configuré lorsqu'il est défini, afin que la carte publiée annonce toujours le domaine canonique au lieu du sous-domaine `*.mintlify.app`. +Les URL de la carte (`url`, `documentationUrl`, `provider.url` et chaque URL de skill) sont construites à partir du domaine personnalisé configuré lorsqu'il est défini, afin que la carte publiée annonce toujours le domaine canonique au lieu du sous-domaine `*.mintlify.site`. Si vous utilisez un [reverse proxy](/fr/deploy/reverse-proxy), configurez-le pour transférer `/.well-known/agent-card.json` vers votre sous-domaine Mintlify. diff --git a/fr/assistant/use.mdx b/fr/assistant/use.mdx index 7be5e04f91..a4b37ba633 100644 --- a/fr/assistant/use.mdx +++ b/fr/assistant/use.mdx @@ -83,8 +83,8 @@ Ouvrez l'assistant depuis n'importe quelle page de votre site de documentation e - `?assistant=` : Ouvre le panneau de chat de l'assistant et envoie `` comme premier message de l'utilisateur. Encodez la valeur en URL pour que les espaces et les caractères spéciaux soient préservés dans la requête. ```text Exemples -https://yourdocs.mintlify.app/quickstart?assistant -https://yourdocs.mintlify.app/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 ```
diff --git a/fr/customize/themes.mdx b/fr/customize/themes.mdx index 723288002c..438cdf0690 100644 --- a/fr/customize/themes.mdx +++ b/fr/customize/themes.mdx @@ -39,22 +39,22 @@ export const ThemeCard = ({ title, value, description, href }) => {
- + - + - + - + - + - + - + - + - +
diff --git a/fr/deploy/authentication-setup.mdx b/fr/deploy/authentication-setup.mdx index ec62f0841f..5c0c910d84 100644 --- a/fr/deploy/authentication-setup.mdx +++ b/fr/deploy/authentication-setup.mdx @@ -14,7 +14,7 @@ L’authentification exige que les utilisateurs se connectent avant d’accéder Vous pouvez configurer une authentification complète pour toutes les pages ou une authentification partielle où certaines pages sont publiques et d'autres sont protégées. -L'authentification n'est disponible que pour les sites hébergés sur un domaine personnalisé ou un sous-domaine Mintlify. Par exemple, `docs.exemple.com` ou `exemple.mintlify.app`. L'authentification **n'est pas prise en charge** pour les sites avec un [sous-chemin personnalisé](/fr/deploy/docs-subpath). Par exemple, `exemple.com/docs`. +L'authentification n'est disponible que pour les sites hébergés sur un domaine personnalisé ou un sous-domaine Mintlify. Par exemple, `docs.exemple.com` ou `exemple.mintlify.site`. L'authentification **n'est pas prise en charge** pour les sites avec un [sous-chemin personnalisé](/fr/deploy/docs-subpath). Par exemple, `exemple.com/docs`.
## Configurer l’authentification diff --git a/fr/discovery-openapi.json b/fr/discovery-openapi.json index ea1493bc14..69428229f6 100644 --- a/fr/discovery-openapi.json +++ b/fr/discovery-openapi.json @@ -28,7 +28,7 @@ "schema": { "type": "string" }, - "description": "L’identifiant de domain à partir de votre URL `domain.mintlify.app`. Il se trouve à la fin de l’URL de votre Dashboard. Par exemple, `dashboard.mintlify.com/organization/domain` a un identifiant de domain de `domain`." + "description": "L’identifiant de domain à partir de votre URL `domain.mintlify.site`. Il se trouve à la fin de l’URL de votre Dashboard. Par exemple, `dashboard.mintlify.com/organization/domain` a un identifiant de domain de `domain`." } ], "requestBody": { @@ -464,7 +464,7 @@ "schema": { "type": "string" }, - "description": "L’identifiant de domaine provenant de votre URL `domain.mintlify.app`. Il se trouve à la fin de l’URL de votre Dashboard. Par exemple, `dashboard.mintlify.com/organization/domain` a un identifiant de domaine égal à `domain`." + "description": "L’identifiant de domaine provenant de votre URL `domain.mintlify.site`. Il se trouve à la fin de l’URL de votre Dashboard. Par exemple, `dashboard.mintlify.com/organization/domain` a un identifiant de domaine égal à `domain`." } ], "requestBody": { @@ -752,7 +752,7 @@ "schema": { "type": "string" }, - "description": "L'identifiant domain de votre URL `domain.mintlify.app`. Il se trouve à la fin de l'URL de votre Dashboard. Par exemple, `dashboard.mintlify.com/organization/domain` a un identifiant domain de `domain`." + "description": "L'identifiant domain de votre URL `domain.mintlify.site`. Il se trouve à la fin de l'URL de votre Dashboard. Par exemple, `dashboard.mintlify.com/organization/domain` a un identifiant domain de `domain`." } ], "requestBody": { @@ -831,7 +831,7 @@ "schema": { "type": "string" }, - "description": "L’identifiant de domaine extrait de votre URL `domain.mintlify.app`. Il se trouve à la fin de l’URL de votre Dashboard. Par exemple, dans `dashboard.mintlify.com/organization/domain`, l’identifiant de domaine est `domain`." + "description": "L’identifiant de domaine extrait de votre URL `domain.mintlify.site`. Il se trouve à la fin de l’URL de votre Dashboard. Par exemple, dans `dashboard.mintlify.com/organization/domain`, l’identifiant de domaine est `domain`." } ], "requestBody": { diff --git a/fr/editor/branching-and-publishing.mdx b/fr/editor/branching-and-publishing.mdx index 78ff28d2e1..2daf889c01 100644 --- a/fr/editor/branching-and-publishing.mdx +++ b/fr/editor/branching-and-publishing.mdx @@ -116,7 +116,7 @@ Chaque fois que vous enregistrez des modifications sur une branche de fonctionna
1. Cliquez sur **Publish** dans la barre d'outils de l'éditeur. -1. Dans le menu de publication, cliquez sur l'URL d'aperçu. Le format de l'URL est `organization-branch-name.mintlify.app`. +1. Dans le menu de publication, cliquez sur l'URL d'aperçu. Le format de l'URL est `organization-branch-name.mintlify.site`. URL d'aperçu mise en évidence dans le menu de publication. URL d'aperçu mise en évidence dans le menu de publication. diff --git a/fr/guides/assistant-embed.mdx b/fr/guides/assistant-embed.mdx index 8e87184882..054ffe5a2f 100644 --- a/fr/guides/assistant-embed.mdx +++ b/fr/guides/assistant-embed.mdx @@ -80,13 +80,13 @@ Ouvrez `src/config.js` et mettez-le à jour avec les détails de votre projet Mi ```js src/config.js export const ASSISTANT_CONFIG = { domain: 'your-domain', - docsURL: 'https://yourdocs.mintlify.app', + docsURL: 'https://yourdocs.mintlify.site', }; ``` Remplacez: - `your-domain` par le domain de votre projet Mintlify, visible à la fin de l’URL de votre dashboard. -- `https://yourdocs.mintlify.app` par l’URL réelle de votre documentation. +- `https://yourdocs.mintlify.site` par l’URL réelle de votre documentation. diff --git a/fr/guides/codex.mdx b/fr/guides/codex.mdx index 40c075f2ed..f016336027 100644 --- a/fr/guides/codex.mdx +++ b/fr/guides/codex.mdx @@ -181,7 +181,7 @@ Pour vous connecter au serveur MCP de votre propre site de documentation, rempla ```toml [mcp_servers.my-docs] -url = "https://your-docs.mintlify.app/mcp" +url = "https://your-docs.mintlify.site/mcp" ``` Consultez [Model Context Protocol](/fr/ai/model-context-protocol) pour plus d'informations sur les serveurs MCP et savoir comment trouver le point de terminaison MCP de votre site. diff --git a/fr/guides/help-center.mdx b/fr/guides/help-center.mdx index 8d6ae2741c..5fb6df7e5f 100644 --- a/fr/guides/help-center.mdx +++ b/fr/guides/help-center.mdx @@ -24,7 +24,7 @@ Le moyen le plus rapide de créer un nouveau centre d’assistance est d’utili mint new your-help-center-name --template help-center-starter ``` -Cela crée un nouveau projet préconfiguré pour un centre d’assistance, comprenant la structure de navigation, des pages d’exemple et des listes de répertoires. Consultez l’[exemple en ligne](https://help-center-starter.mintlify.app/) ou parcourez le [code source du modèle](https://github.com/mintlify/templates/tree/main/help-center-starter). +Cela crée un nouveau projet préconfiguré pour un centre d’assistance, comprenant la structure de navigation, des pages d’exemple et des listes de répertoires. Consultez l’[exemple en ligne](https://help-center-starter.mintlify.site/) ou parcourez le [code source du modèle](https://github.com/mintlify/templates/tree/main/help-center-starter). Si vous préférez configurer un centre d’assistance dans un projet existant, poursuivez avec les étapes ci-dessous. diff --git a/fr/integrations/privacy/osano.mdx b/fr/integrations/privacy/osano.mdx index 9845d095b5..f77891e92b 100644 --- a/fr/integrations/privacy/osano.mdx +++ b/fr/integrations/privacy/osano.mdx @@ -42,7 +42,7 @@ Remplacez `OSANO_SCRIPT_URL` par l’URL de votre script Osano. Cette URL de scr - Ajoutez `.mintlify.app/` en tant que règle gérée. + Ajoutez `.mintlify.site/` en tant que règle gérée. Règle gérée Osano diff --git a/guides/assistant-embed.mdx b/guides/assistant-embed.mdx index cc13506e99..843b773bc1 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.mintlify.app', + docsURL: 'https://yourdocs.mintlify.site', }; ``` Replace: - `your-domain` with your Mintlify project domain found at the end of your dashboard URL. -- `https://yourdocs.mintlify.app` 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 09a20dc926..7440bdf955 100644 --- a/guides/codex.mdx +++ b/guides/codex.mdx @@ -165,7 +165,7 @@ To connect to your own documentation site's MCP server instead, replace the URL ```toml [mcp_servers.my-docs] -url = "https://your-docs.mintlify.app/mcp" +url = "https://your-docs.mintlify.site/mcp" ``` See [Model Context Protocol](/ai/model-context-protocol) for more information about MCP servers and how to find your site's MCP endpoint. diff --git a/guides/help-center.mdx b/guides/help-center.mdx index 4a826c3de7..c07cbe8971 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.mintlify.app/) 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 db21ddd505..9d8b1add86 100644 --- a/integrations/privacy/osano.mdx +++ b/integrations/privacy/osano.mdx @@ -42,7 +42,7 @@ Replace `OSANO_SCRIPT_URL` with your Osano script URL. Your script URL is the `s - Add `.mintlify.app/` as a managed rule. + Add `.mintlify.site/` as a managed rule. Osano managed rule diff --git a/snippets/es/vercel-json-generator.mdx b/snippets/es/vercel-json-generator.mdx index 2982a8d099..b874a6386b 100644 --- a/snippets/es/vercel-json-generator.mdx +++ b/snippets/es/vercel-json-generator.mdx @@ -6,43 +6,43 @@ export const VercelJsonGenerator = () => { rewrites: [ { source: "/_mintlify/:path*", - destination: `https://${subdomain}.mintlify.app/_mintlify/:path*` + destination: `https://${subdomain}.mintlify.site/_mintlify/:path*` }, { source: "/api/request", - destination: `https://${subdomain}.mintlify.app/_mintlify/api/request` + destination: `https://${subdomain}.mintlify.site/_mintlify/api/request` }, { source: `/${subpath}`, - destination: `https://${subdomain}.mintlify.app/${subpath}` + destination: `https://${subdomain}.mintlify.site/${subpath}` }, { source: `/${subpath}/llms.txt`, - destination: `https://${subdomain}.mintlify.app/llms.txt` + destination: `https://${subdomain}.mintlify.site/llms.txt` }, { source: `/${subpath}/llms-full.txt`, - destination: `https://${subdomain}.mintlify.app/llms-full.txt` + destination: `https://${subdomain}.mintlify.site/llms-full.txt` }, { source: `/${subpath}/sitemap.xml`, - destination: `https://${subdomain}.mintlify.app/sitemap.xml` + destination: `https://${subdomain}.mintlify.site/sitemap.xml` }, { source: `/${subpath}/robots.txt`, - destination: `https://${subdomain}.mintlify.app/robots.txt` + destination: `https://${subdomain}.mintlify.site/robots.txt` }, { source: `/${subpath}/mcp`, - destination: `https://${subdomain}.mintlify.app/mcp` + destination: `https://${subdomain}.mintlify.site/mcp` }, { source: `/${subpath}/:path*`, - destination: `https://${subdomain}.mintlify.app/${subpath}/:path*` + destination: `https://${subdomain}.mintlify.site/${subpath}/:path*` }, { source: "/mintlify-assets/:path+", - destination: `https://${subdomain}.mintlify.app/mintlify-assets/:path+` + destination: `https://${subdomain}.mintlify.site/mintlify-assets/:path+` } ] } diff --git a/snippets/fr/vercel-json-generator.mdx b/snippets/fr/vercel-json-generator.mdx index 2982a8d099..b874a6386b 100644 --- a/snippets/fr/vercel-json-generator.mdx +++ b/snippets/fr/vercel-json-generator.mdx @@ -6,43 +6,43 @@ export const VercelJsonGenerator = () => { rewrites: [ { source: "/_mintlify/:path*", - destination: `https://${subdomain}.mintlify.app/_mintlify/:path*` + destination: `https://${subdomain}.mintlify.site/_mintlify/:path*` }, { source: "/api/request", - destination: `https://${subdomain}.mintlify.app/_mintlify/api/request` + destination: `https://${subdomain}.mintlify.site/_mintlify/api/request` }, { source: `/${subpath}`, - destination: `https://${subdomain}.mintlify.app/${subpath}` + destination: `https://${subdomain}.mintlify.site/${subpath}` }, { source: `/${subpath}/llms.txt`, - destination: `https://${subdomain}.mintlify.app/llms.txt` + destination: `https://${subdomain}.mintlify.site/llms.txt` }, { source: `/${subpath}/llms-full.txt`, - destination: `https://${subdomain}.mintlify.app/llms-full.txt` + destination: `https://${subdomain}.mintlify.site/llms-full.txt` }, { source: `/${subpath}/sitemap.xml`, - destination: `https://${subdomain}.mintlify.app/sitemap.xml` + destination: `https://${subdomain}.mintlify.site/sitemap.xml` }, { source: `/${subpath}/robots.txt`, - destination: `https://${subdomain}.mintlify.app/robots.txt` + destination: `https://${subdomain}.mintlify.site/robots.txt` }, { source: `/${subpath}/mcp`, - destination: `https://${subdomain}.mintlify.app/mcp` + destination: `https://${subdomain}.mintlify.site/mcp` }, { source: `/${subpath}/:path*`, - destination: `https://${subdomain}.mintlify.app/${subpath}/:path*` + destination: `https://${subdomain}.mintlify.site/${subpath}/:path*` }, { source: "/mintlify-assets/:path+", - destination: `https://${subdomain}.mintlify.app/mintlify-assets/:path+` + destination: `https://${subdomain}.mintlify.site/mintlify-assets/:path+` } ] } diff --git a/snippets/vercel-json-generator.mdx b/snippets/vercel-json-generator.mdx index f87d3ccc76..55481174ca 100644 --- a/snippets/vercel-json-generator.mdx +++ b/snippets/vercel-json-generator.mdx @@ -6,43 +6,43 @@ export const VercelJsonGenerator = () => { rewrites: [ { source: "/_mintlify/:path*", - destination: `https://${subdomain}.mintlify.app/_mintlify/:path*` + destination: `https://${subdomain}.mintlify.site/_mintlify/:path*` }, { source: "/api/request", - destination: `https://${subdomain}.mintlify.app/_mintlify/api/request` + destination: `https://${subdomain}.mintlify.site/_mintlify/api/request` }, { source: `/${subpath}`, - destination: `https://${subdomain}.mintlify.app/${subpath}` + destination: `https://${subdomain}.mintlify.site/${subpath}` }, { source: `/${subpath}/llms.txt`, - destination: `https://${subdomain}.mintlify.app/llms.txt` + destination: `https://${subdomain}.mintlify.site/llms.txt` }, { source: `/${subpath}/llms-full.txt`, - destination: `https://${subdomain}.mintlify.app/llms-full.txt` + destination: `https://${subdomain}.mintlify.site/llms-full.txt` }, { source: `/${subpath}/sitemap.xml`, - destination: `https://${subdomain}.mintlify.app/sitemap.xml` + destination: `https://${subdomain}.mintlify.site/sitemap.xml` }, { source: `/${subpath}/robots.txt`, - destination: `https://${subdomain}.mintlify.app/robots.txt` + destination: `https://${subdomain}.mintlify.site/robots.txt` }, { source: `/${subpath}/mcp`, - destination: `https://${subdomain}.mintlify.app/mcp` + destination: `https://${subdomain}.mintlify.site/mcp` }, { source: `/${subpath}/:path*`, - destination: `https://${subdomain}.mintlify.app/${subpath}/:path*` + destination: `https://${subdomain}.mintlify.site/${subpath}/:path*` }, { source: "/mintlify-assets/:path+", - destination: `https://${subdomain}.mintlify.app/mintlify-assets/:path+` + destination: `https://${subdomain}.mintlify.site/mintlify-assets/:path+` } ] } diff --git a/snippets/zh/vercel-json-generator.mdx b/snippets/zh/vercel-json-generator.mdx index 2982a8d099..b874a6386b 100644 --- a/snippets/zh/vercel-json-generator.mdx +++ b/snippets/zh/vercel-json-generator.mdx @@ -6,43 +6,43 @@ export const VercelJsonGenerator = () => { rewrites: [ { source: "/_mintlify/:path*", - destination: `https://${subdomain}.mintlify.app/_mintlify/:path*` + destination: `https://${subdomain}.mintlify.site/_mintlify/:path*` }, { source: "/api/request", - destination: `https://${subdomain}.mintlify.app/_mintlify/api/request` + destination: `https://${subdomain}.mintlify.site/_mintlify/api/request` }, { source: `/${subpath}`, - destination: `https://${subdomain}.mintlify.app/${subpath}` + destination: `https://${subdomain}.mintlify.site/${subpath}` }, { source: `/${subpath}/llms.txt`, - destination: `https://${subdomain}.mintlify.app/llms.txt` + destination: `https://${subdomain}.mintlify.site/llms.txt` }, { source: `/${subpath}/llms-full.txt`, - destination: `https://${subdomain}.mintlify.app/llms-full.txt` + destination: `https://${subdomain}.mintlify.site/llms-full.txt` }, { source: `/${subpath}/sitemap.xml`, - destination: `https://${subdomain}.mintlify.app/sitemap.xml` + destination: `https://${subdomain}.mintlify.site/sitemap.xml` }, { source: `/${subpath}/robots.txt`, - destination: `https://${subdomain}.mintlify.app/robots.txt` + destination: `https://${subdomain}.mintlify.site/robots.txt` }, { source: `/${subpath}/mcp`, - destination: `https://${subdomain}.mintlify.app/mcp` + destination: `https://${subdomain}.mintlify.site/mcp` }, { source: `/${subpath}/:path*`, - destination: `https://${subdomain}.mintlify.app/${subpath}/:path*` + destination: `https://${subdomain}.mintlify.site/${subpath}/:path*` }, { source: "/mintlify-assets/:path+", - destination: `https://${subdomain}.mintlify.app/mintlify-assets/:path+` + destination: `https://${subdomain}.mintlify.site/mintlify-assets/:path+` } ] } diff --git a/zh/ai/skillmd.mdx b/zh/ai/skillmd.mdx index 430e824c8b..4beb8849a5 100644 --- a/zh/ai/skillmd.mdx +++ b/zh/ai/skillmd.mdx @@ -235,7 +235,7 @@ Mintlify 在 `/.well-known/agent-card.json` 托管一个 [Agent-to-Agent (A2A)]( | `capabilities` | 功能标志。目前为 `{ streaming: false, pushNotifications: false }`。 | | `skills` | 在 `/.well-known/agent-skills/` 暴露的 skills。 | -card 中的 URL（`url`、`documentationUrl`、`provider.url` 以及每个 skill URL）使用你配置的自定义域名，因此发布的 card 始终公布规范域名而不是 `*.mintlify.app` 子域名。 +card 中的 URL（`url`、`documentationUrl`、`provider.url` 以及每个 skill URL）使用你配置的自定义域名，因此发布的 card 始终公布规范域名而不是 `*.mintlify.site` 子域名。 如果你使用[反向代理](/zh/deploy/reverse-proxy)，请将其配置为将 `/.well-known/agent-card.json` 转发到你的 Mintlify 子域名。 diff --git a/zh/assistant/use.mdx b/zh/assistant/use.mdx index 1dfae9fa97..4d6a797279 100644 --- a/zh/assistant/use.mdx +++ b/zh/assistant/use.mdx @@ -83,8 +83,8 @@ AI 助手出现在两个位置：搜索栏旁边的按钮和页面底部的横 - `?assistant=<消息>`：打开 AI 助手聊天面板，并将 `<消息>` 作为用户的第一条消息发送。请对参数值进行 URL 编码，以确保空格和特殊字符在请求中被正确保留。 ```text 示例 -https://yourdocs.mintlify.app/quickstart?assistant -https://yourdocs.mintlify.app/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 ```
diff --git a/zh/customize/themes.mdx b/zh/customize/themes.mdx index 4bb8c614f2..a0184dae65 100644 --- a/zh/customize/themes.mdx +++ b/zh/customize/themes.mdx @@ -39,22 +39,22 @@ export const ThemeCard = ({ title, value, description, href }) => {
- + - + - + - + - + - + - + - + - +
diff --git a/zh/deploy/authentication-setup.mdx b/zh/deploy/authentication-setup.mdx index 3485ac7725..20fb958ebc 100644 --- a/zh/deploy/authentication-setup.mdx +++ b/zh/deploy/authentication-setup.mdx @@ -14,7 +14,7 @@ keywords: ['authentication', 'auth', 'OAuth', 'JWT', 'password'] 启用认证后，用户必须先登录才能访问任何内容。你可以将特定页面或分组配置为公开，而将其他页面设为受保护状态。 -认证仅适用于托管在自定义域名或 Mintlify 子域名上的站点。例如，`docs.example.com` 或 `example.mintlify.app`。使用[自定义子路径](/zh/deploy/docs-subpath)的站点**不支持**认证。例如，`example.com/docs`。 +认证仅适用于托管在自定义域名或 Mintlify 子域名上的站点。例如，`docs.example.com` 或 `example.mintlify.site`。使用[自定义子路径](/zh/deploy/docs-subpath)的站点**不支持**认证。例如，`example.com/docs`。
## 配置认证 diff --git a/zh/discovery-openapi.json b/zh/discovery-openapi.json index 712811dfce..c3180c5b70 100644 --- a/zh/discovery-openapi.json +++ b/zh/discovery-openapi.json @@ -28,7 +28,7 @@ "schema": { "type": "string" }, - "description": "在你的 `domain.mintlify.app` URL 中使用的 domain 标识符。你可以在控制台 URL 的末尾找到它。例如，在 `dashboard.mintlify.com/organization/domain` 中，domain 标识符为 `domain`。" + "description": "在你的 `domain.mintlify.site` URL 中使用的 domain 标识符。你可以在控制台 URL 的末尾找到它。例如，在 `dashboard.mintlify.com/organization/domain` 中，domain 标识符为 `domain`。" } ], "requestBody": { @@ -464,7 +464,7 @@ "schema": { "type": "string" }, - "description": "来自你的 `domain.mintlify.app` URL 中的 domain 标识符。你可以在控制台 URL 的末尾找到它。例如，在 `dashboard.mintlify.com/organization/domain` 中，domain 标识符是 `domain`。" + "description": "来自你的 `domain.mintlify.site` URL 中的 domain 标识符。你可以在控制台 URL 的末尾找到它。例如，在 `dashboard.mintlify.com/organization/domain` 中，domain 标识符是 `domain`。" } ], "requestBody": { @@ -752,7 +752,7 @@ "schema": { "type": "string" }, - "description": "来自你的 `domain.mintlify.app` URL 的域名标识符。可以在你的控制台 URL 末尾找到。例如，`dashboard.mintlify.com/organization/domain` 的域名标识符为 `domain`。" + "description": "来自你的 `domain.mintlify.site` URL 的域名标识符。可以在你的控制台 URL 末尾找到。例如，`dashboard.mintlify.com/organization/domain` 的域名标识符为 `domain`。" } ], "requestBody": { @@ -831,7 +831,7 @@ "schema": { "type": "string" }, - "description": "来自你的 `domain.mintlify.app` URL 的域名标识符。可以在控制台 URL 的末尾找到。例如，`dashboard.mintlify.com/organization/domain` 的域名标识符就是 `domain`。" + "description": "来自你的 `domain.mintlify.site` URL 的域名标识符。可以在控制台 URL 的末尾找到。例如，`dashboard.mintlify.com/organization/domain` 的域名标识符就是 `domain`。" } ], "requestBody": { diff --git a/zh/editor/branching-and-publishing.mdx b/zh/editor/branching-and-publishing.mdx index ef9db1fdf0..2aec7a32f2 100644 --- a/zh/editor/branching-and-publishing.mdx +++ b/zh/editor/branching-and-publishing.mdx @@ -100,7 +100,7 @@ Web 编辑器会在你输入时自动保存所有内容，但你的更改只有
1. 点击编辑器工具栏中的 **Publish**。 -1. 在发布菜单中，点击预览 URL。URL 格式为 `organization-branch-name.mintlify.app`。 +1. 在发布菜单中，点击预览 URL。URL 格式为 `organization-branch-name.mintlify.site`。 发布菜单中突出显示的预览 URL。 发布菜单中突出显示的预览 URL。 diff --git a/zh/editor/collaborate.mdx b/zh/editor/collaborate.mdx index b7b6024694..b262e215ed 100644 --- a/zh/editor/collaborate.mdx +++ b/zh/editor/collaborate.mdx @@ -96,7 +96,7 @@ agent 完成编辑后不久，其光标会自动消失。
1. 在编辑器工具栏中点击 **Publish**。 -2. 点击预览 URL，在新标签页中打开预览部署。URL 的格式为 `organization-branch-name.mintlify.app`。 +2. 点击预览 URL，在新标签页中打开预览部署。URL 的格式为 `organization-branch-name.mintlify.site`。
### 分享预览 diff --git a/zh/guides/assistant-embed.mdx b/zh/guides/assistant-embed.mdx index 9ab7d4fe6d..008996d8b5 100644 --- a/zh/guides/assistant-embed.mdx +++ b/zh/guides/assistant-embed.mdx @@ -79,14 +79,14 @@ keywords: ["assistant embed", "in-app chat", "widget", "chatbot"] ```js src/config.js export const ASSISTANT_CONFIG = { domain: 'your-domain', - docsURL: 'https://yourdocs.mintlify.app', + docsURL: 'https://yourdocs.mintlify.site', }; ``` 将以下内容替换为你的实际信息： * 将 `your-domain` 替换为你在控制台 URL 末尾看到的 Mintlify 项目 domain。 - * 将 `https://yourdocs.mintlify.app` 替换为你的文档实际 URL。 + * 将 `https://yourdocs.mintlify.site` 替换为你的文档实际 URL。 diff --git a/zh/guides/codex.mdx b/zh/guides/codex.mdx index a2fb8fe79e..66887260ff 100644 --- a/zh/guides/codex.mdx +++ b/zh/guides/codex.mdx @@ -181,7 +181,7 @@ url = "https://mintlify.com/docs/mcp" ```toml [mcp_servers.my-docs] -url = "https://your-docs.mintlify.app/mcp" +url = "https://your-docs.mintlify.site/mcp" ``` 有关 MCP 服务器以及如何查找你站点 MCP 端点的更多信息，请参阅 [Model Context Protocol](/zh/ai/model-context-protocol)。 diff --git a/zh/guides/help-center.mdx b/zh/guides/help-center.mdx index f27a3d6ddc..3aad55c660 100644 --- a/zh/guides/help-center.mdx +++ b/zh/guides/help-center.mdx @@ -24,7 +24,7 @@ Mintlify 提供可随客户规模扩展的支持中心基础设施。 mint new your-help-center-name --template help-center-starter ``` -这会创建一个为支持中心预先配置好的新项目，包含导航结构、示例页面和目录列表。查看[在线示例](https://help-center-starter.mintlify.app/)或浏览[模板源代码](https://github.com/mintlify/templates/tree/main/help-center-starter)。 +这会创建一个为支持中心预先配置好的新项目，包含导航结构、示例页面和目录列表。查看[在线示例](https://help-center-starter.mintlify.site/)或浏览[模板源代码](https://github.com/mintlify/templates/tree/main/help-center-starter)。 如果你希望在现有项目中配置支持中心，请继续按照下面的步骤操作。 diff --git a/zh/integrations/privacy/osano.mdx b/zh/integrations/privacy/osano.mdx index 56c22ca1db..db1ea702e9 100644 --- a/zh/integrations/privacy/osano.mdx +++ b/zh/integrations/privacy/osano.mdx @@ -42,7 +42,7 @@ boost: 3 - 将 `.mintlify.app/` 添加为一条 managed rule。 + 将 `.mintlify.site/` 添加为一条 managed rule。 Osano managed rule