diff --git a/docs.json b/docs.json
index a70122a..45f55c4 100644
--- a/docs.json
+++ b/docs.json
@@ -197,6 +197,100 @@
]
}
]
+ },
+ {
+ "language": "cn",
+ "tabs": [
+ {
+ "tab": "指南",
+ "groups": [
+ {
+ "group": "入门",
+ "pages": [
+ "docs/cn/index",
+ "docs/cn/quickstart",
+ "docs/cn/development"
+ ]
+ },
+ {
+ "group": "自定义",
+ "pages": [
+ "docs/cn/essentials/settings",
+ "docs/cn/essentials/navigation"
+ ]
+ },
+ {
+ "group": "撰写内容",
+ "pages": [
+ "docs/cn/essentials/markdown",
+ "docs/cn/essentials/code",
+ "docs/cn/essentials/images",
+ "docs/cn/essentials/reusable-snippets"
+ ]
+ },
+ {
+ "group": "AI 工具",
+ "pages": [
+ "docs/cn/ai-tools/cursor",
+ "docs/cn/ai-tools/claude-code",
+ "docs/cn/ai-tools/windsurf"
+ ]
+ },
+ {
+ "group": "实施练习",
+ "pages": [
+ "docs/cn/implementation-exercises/signed-webhooks",
+ "docs/cn/implementation-exercises/async-export-jobs",
+ "docs/cn/implementation-exercises/team-feature-flags"
+ ]
+ }
+ ]
+ },
+ {
+ "tab": "API 参考",
+ "groups": [
+ {
+ "group": "API 文档",
+ "pages": [
+ "docs/cn/api-reference/introduction"
+ ]
+ },
+ {
+ "group": "OpenAPI 参考测试",
+ "pages": [
+ "docs/cn/api-reference/openapi-test/index",
+ "docs/cn/api-reference/openapi-test/relative",
+ "docs/cn/api-reference/openapi-test/absolute",
+ "docs/cn/api-reference/openapi-test/same-dir",
+ "docs/cn/api-reference/openapi-test/explode-false-query",
+ "docs/cn/api-reference/openapi-test/explode-true-query",
+ "docs/cn/api-reference/openapi-test/remote"
+ ]
+ },
+ {
+ "group": "端点示例",
+ "pages": [
+ "docs/cn/api-reference/endpoint/get",
+ "docs/cn/api-reference/endpoint/create",
+ "docs/cn/api-reference/endpoint/delete",
+ "docs/cn/api-reference/endpoint/webhook",
+ "docs/cn/api-reference/endpoint/search",
+ "docs/cn/api-reference/endpoint/academic-standards-search",
+ "docs/cn/api-reference/endpoint/change-location",
+ "docs/cn/api-reference/endpoint/hierarchy",
+ "docs/cn/api-reference/endpoint/get-asset-proof",
+ "docs/cn/api-reference/endpoint/get-pots"
+ ]
+ },
+ {
+ "group": "AsyncAPI 文档",
+ "asyncapi": {
+ "source": "docs/api-reference/asyncapi.json"
+ }
+ }
+ ]
+ }
+ ]
}
],
"global": {
diff --git a/docs/cn/ai-tools/claude-code.mdx b/docs/cn/ai-tools/claude-code.mdx
new file mode 100644
index 0000000..8f3bd50
--- /dev/null
+++ b/docs/cn/ai-tools/claude-code.mdx
@@ -0,0 +1,76 @@
+---
+title: "Claude Code 设置"
+description: "为你的文档工作流配置 Claude Code"
+icon: "asterisk"
+---
+
+Claude Code 是 Anthropic 官方的 CLI 工具。本指南将帮助你设置 Claude Code，以协助你编写和维护文档。
+
+## 前置条件
+
+- 有效的 Claude 订阅（Pro、Max 或 API 访问权限）
+
+## 设置
+
+1. 全局安装 Claude Code：
+
+ ```bash
+ npm install -g @anthropic-ai/claude-code
+```
+
+2. 导航到你的文档目录。
+3. （可选）将下方的 `CLAUDE.md` 文件添加到你的项目中。
+4. 运行 `claude` 启动。
+
+## 创建 `CLAUDE.md`
+
+在文档仓库根目录创建一个 `CLAUDE.md` 文件，使 Claude Code 了解你特定的文档规范：
+
+````markdown
+# Mintlify documentation
+
+## Working relationship
+- You can push back on ideas-this can lead to better documentation. Cite sources and explain your reasoning when you do so
+- ALWAYS ask for clarification rather than making assumptions
+- NEVER lie, guess, or make up information
+
+## Project context
+- Format: MDX files with YAML frontmatter
+- Config: docs.json for navigation, theme, settings
+- Components: Mintlify components
+
+## Content strategy
+- Document just enough for user success - not too much, not too little
+- Prioritize accuracy and usability of information
+- Make content evergreen when possible
+- Search for existing information before adding new content. Avoid duplication unless it is done for a strategic reason
+- Check existing patterns for consistency
+- Start by making the smallest reasonable changes
+
+## Frontmatter requirements for pages
+- title: Clear, descriptive page title
+- description: Concise summary for SEO/navigation
+
+## Writing standards
+- Second-person voice ("you")
+- Prerequisites at start of procedural content
+- Test all code examples before publishing
+- Match style and formatting of existing pages
+- Include both basic and advanced use cases
+- Language tags on all code blocks
+- Alt text on all images
+- Relative paths for internal links
+
+## Git workflow
+- NEVER use --no-verify when committing
+- Ask how to handle uncommitted changes before starting
+- Create a new branch when no clear branch exists for changes
+- Commit frequently throughout development
+- NEVER skip or disable pre-commit hooks
+
+## Do not
+- Skip frontmatter on any MDX file
+- Use absolute URLs for internal links
+- Include untested code examples
+- Make assumptions - always ask for clarification
+````
diff --git a/docs/cn/ai-tools/cursor.mdx b/docs/cn/ai-tools/cursor.mdx
new file mode 100644
index 0000000..17c5602
--- /dev/null
+++ b/docs/cn/ai-tools/cursor.mdx
@@ -0,0 +1,420 @@
+---
+title: "Cursor 设置"
+description: "为你的文档工作流配置 Cursor"
+icon: "arrow-pointer"
+---
+
+使用 Cursor 协助你编写和维护文档。本指南介绍如何配置 Cursor，以便在技术写作任务和使用 Mintlify 组件时获得更好的效果。
+
+## 前置条件
+
+- 已安装 Cursor 编辑器
+- 拥有文档仓库的访问权限
+
+## 项目规则
+
+创建可供所有团队成员使用的项目规则。在你的文档仓库根目录中：
+
+```bash
+mkdir -p .cursor
+```
+
+创建 `.cursor/rules.md`：
+
+````markdown
+# Mintlify technical writing rule
+
+You are an AI writing assistant specialized in creating exceptional technical documentation using Mintlify components and following industry-leading technical writing practices.
+
+## Core writing principles
+
+### Language and style requirements
+
+- Use clear, direct language appropriate for technical audiences
+- Write in second person ("you") for instructions and procedures
+- Use active voice over passive voice
+- Employ present tense for current states, future tense for outcomes
+- Avoid jargon unless necessary and define terms when first used
+- Maintain consistent terminology throughout all documentation
+- Keep sentences concise while providing necessary context
+- Use parallel structure in lists, headings, and procedures
+
+### Content organization standards
+
+- Lead with the most important information (inverted pyramid structure)
+- Use progressive disclosure: basic concepts before advanced ones
+- Break complex procedures into numbered steps
+- Include prerequisites and context before instructions
+- Provide expected outcomes for each major step
+- Use descriptive, keyword-rich headings for navigation and SEO
+- Group related information logically with clear section breaks
+
+### User-centered approach
+
+- Focus on user goals and outcomes rather than system features
+- Anticipate common questions and address them proactively
+- Include troubleshooting for likely failure points
+- Write for scannability with clear headings, lists, and white space
+- Include verification steps to confirm success
+
+## Mintlify component reference
+
+### Callout components
+
+#### Note - Additional helpful information
+
+
+Supplementary information that supports the main content without interrupting flow
+
+
+#### Tip - Best practices and pro tips
+
+
+Expert advice, shortcuts, or best practices that enhance user success
+
+
+#### Warning - Important cautions
+
+
+Critical information about potential issues, breaking changes, or destructive actions
+
+
+#### Info - Neutral contextual information
+
+
+Background information, context, or neutral announcements
+
+
+#### Check - Success confirmations
+
+
+Positive confirmations, successful completions, or achievement indicators
+
+
+### Code components
+
+#### Single code block
+
+Example of a single code block:
+
+```javascript config.js
+const apiConfig = {
+ baseURL: 'https://api.example.com',
+ timeout: 5000,
+ headers: {
+ 'Authorization': `Bearer ${process.env.API_TOKEN}`
+ }
+};
+```
+
+#### Code group with multiple languages
+
+Example of a code group:
+
+
+```javascript Node.js
+const response = await fetch('/api/endpoint', {
+ headers: { Authorization: `Bearer ${apiKey}` }
+});
+```
+
+```python Python
+import requests
+response = requests.get('/api/endpoint',
+ headers={'Authorization': f'Bearer {api_key}'})
+```
+
+```curl cURL
+curl -X GET '/api/endpoint' \
+ -H 'Authorization: Bearer YOUR_API_KEY'
+```
+
+
+#### Request/response examples
+
+Example of request/response documentation:
+
+
+```bash cURL
+curl -X POST 'https://api.example.com/users' \
+ -H 'Content-Type: application/json' \
+ -d '{"name": "John Doe", "email": "john@example.com"}'
+```
+
+
+
+```json Success
+{
+ "id": "user_123",
+ "name": "John Doe",
+ "email": "john@example.com",
+ "created_at": "2024-01-15T10:30:00Z"
+}
+```
+
+
+### Structural components
+
+#### Steps for procedures
+
+Example of step-by-step instructions:
+
+
+
+ Run `npm install` to install required packages.
+
+
+ Verify installation by running `npm list`.
+
+
+
+
+ Create a `.env` file with your API credentials.
+
+ ```bash
+ API_KEY=your_api_key_here
+ ```
+
+
+ Never commit API keys to version control.
+
+
+
+
+#### Tabs for alternative content
+
+Example of tabbed content:
+
+
+
+ ```bash
+ brew install node
+ npm install -g package-name
+ ```
+
+
+
+ ```powershell
+ choco install nodejs
+ npm install -g package-name
+ ```
+
+
+
+ ```bash
+ sudo apt install nodejs npm
+ npm install -g package-name
+ ```
+
+
+
+#### Accordions for collapsible content
+
+Example of accordion groups:
+
+
+
+ - **Firewall blocking**: Ensure ports 80 and 443 are open
+ - **Proxy configuration**: Set HTTP_PROXY environment variable
+ - **DNS resolution**: Try using 8.8.8.8 as DNS server
+
+
+
+ ```javascript
+ const config = {
+ performance: { cache: true, timeout: 30000 },
+ security: { encryption: 'AES-256' }
+ };
+ ```
+
+
+
+### Cards and columns for emphasizing information
+
+Example of cards and card groups:
+
+
+Complete walkthrough from installation to your first API call in under 10 minutes.
+
+
+
+
+ Learn how to authenticate requests using API keys or JWT tokens.
+
+
+
+ Understand rate limits and best practices for high-volume usage.
+
+
+
+### API documentation components
+
+#### Parameter fields
+
+Example of parameter documentation:
+
+
+Unique identifier for the user. Must be a valid UUID v4 format.
+
+
+
+User's email address. Must be valid and unique within the system.
+
+
+
+Maximum number of results to return. Range: 1-100.
+
+
+
+Bearer token for API authentication. Format: `Bearer YOUR_API_KEY`
+
+
+#### Response fields
+
+Example of response field documentation:
+
+
+Unique identifier assigned to the newly created user.
+
+
+
+ISO 8601 formatted timestamp of when the user was created.
+
+
+
+List of permission strings assigned to this user.
+
+
+#### Expandable nested fields
+
+Example of nested field documentation:
+
+
+Complete user object with all associated data.
+
+
+
+ User profile information including personal details.
+
+
+
+ User's first name as entered during registration.
+
+
+
+ URL to user's profile picture. Returns null if no avatar is set.
+
+
+
+
+
+
+### Media and advanced components
+
+#### Frames for images
+
+Wrap all images in frames:
+
+
+
+
+
+
+
+
+
+#### Videos
+
+Use the HTML video element for self-hosted video content:
+
+
+
+Embed YouTube videos using iframe elements:
+
+
+
+#### Tooltips
+
+Example of tooltip usage:
+
+
+API
+
+
+#### Updates
+
+Use updates for changelogs:
+
+
+## New features
+- Added bulk user import functionality
+- Improved error messages with actionable suggestions
+
+## Bug fixes
+- Fixed pagination issue with large datasets
+- Resolved authentication timeout problems
+
+
+## Required page structure
+
+Every documentation page must begin with YAML frontmatter:
+
+```yaml
+---
+title: "Clear, specific, keyword-rich title"
+description: "Concise description explaining page purpose and value"
+---
+```
+
+## Content quality standards
+
+### Code examples requirements
+
+- Always include complete, runnable examples that users can copy and execute
+- Show proper error handling and edge case management
+- Use realistic data instead of placeholder values
+- Include expected outputs and results for verification
+- Test all code examples thoroughly before publishing
+- Specify language and include filename when relevant
+- Add explanatory comments for complex logic
+- Never include real API keys or secrets in code examples
+
+### API documentation requirements
+
+- Document all parameters including optional ones with clear descriptions
+- Show both success and error response examples with realistic data
+- Include rate limiting information with specific limits
+- Provide authentication examples showing proper format
+- Explain all HTTP status codes and error handling
+- Cover complete request/response cycles
+
+### Accessibility requirements
+
+- Include descriptive alt text for all images and diagrams
+- Use specific, actionable link text instead of "click here"
+- Ensure proper heading hierarchy starting with H2
+- Provide keyboard navigation considerations
+- Use sufficient color contrast in examples and visuals
+- Structure content for easy scanning with headers and lists
+
+## Component selection logic
+
+- Use **Steps** for procedures and sequential instructions
+- Use **Tabs** for platform-specific content or alternative approaches
+- Use **CodeGroup** when showing the same concept in multiple programming languages
+- Use **Accordions** for progressive disclosure of information
+- Use **RequestExample/ResponseExample** specifically for API endpoint documentation
+- Use **ParamField** for API parameters, **ResponseField** for API responses
+- Use **Expandable** for nested object properties or hierarchical information
+````
diff --git a/docs/cn/ai-tools/windsurf.mdx b/docs/cn/ai-tools/windsurf.mdx
new file mode 100644
index 0000000..4b4f424
--- /dev/null
+++ b/docs/cn/ai-tools/windsurf.mdx
@@ -0,0 +1,96 @@
+---
+title: "Windsurf 设置"
+description: "为你的文档工作流配置 Windsurf"
+icon: "water"
+---
+
+配置 Windsurf 的 Cascade AI 助手以帮助你编写和维护文档。本指南介绍如何专门为你的 Mintlify 文档工作流设置 Windsurf。
+
+## 前置条件
+
+- 已安装 Windsurf 编辑器
+- 拥有文档仓库的访问权限
+
+## 工作区规则
+
+创建工作区规则，为 Windsurf 提供有关你的文档项目和规范的上下文。
+
+在项目根目录创建 `.windsurf/rules.md`：
+
+````markdown
+# Mintlify technical writing rule
+
+## Project context
+
+- This is a documentation project on the Mintlify platform
+- We use MDX files with YAML frontmatter
+- Navigation is configured in `docs.json`
+- We follow technical writing best practices
+
+## Writing standards
+
+- Use second person ("you") for instructions
+- Write in active voice and present tense
+- Start procedures with prerequisites
+- Include expected outcomes for major steps
+- Use descriptive, keyword-rich headings
+- Keep sentences concise but informative
+
+## Required page structure
+
+Every page must start with frontmatter:
+
+```yaml
+---
+title: "Clear, specific title"
+description: "Concise description for SEO and navigation"
+---
+```
+
+## Mintlify components
+
+### Callouts
+
+- `` for helpful supplementary information
+- `` for important cautions and breaking changes
+- `` for best practices and expert advice
+- `` for neutral contextual information
+- `` for success confirmations
+
+### Code examples
+
+- When appropriate, include complete, runnable examples
+- Use `` for multiple language examples
+- Specify language tags on all code blocks
+- Include realistic data, not placeholders
+- Use `` and `` for API docs
+
+### Procedures
+
+- Use `` component for sequential instructions
+- Include verification steps with `` components when relevant
+- Break complex procedures into smaller steps
+
+### Content organization
+
+- Use `` for platform-specific content
+- Use `` for progressive disclosure
+- Use `` and `` for highlighting content
+- Wrap images in `` components with descriptive alt text
+
+## API documentation requirements
+
+- Document all parameters with ``
+- Show response structure with ``
+- Include both success and error examples
+- Use `` for nested object properties
+- Always include authentication examples
+
+## Quality standards
+
+- Test all code examples before publishing
+- Use relative paths for internal links
+- Include alt text for all images
+- Ensure proper heading hierarchy (start with h2)
+- Check existing patterns for consistency
+````
diff --git a/docs/cn/api-reference/async-api/lighting-measured.mdx b/docs/cn/api-reference/async-api/lighting-measured.mdx
new file mode 100644
index 0000000..f69590f
--- /dev/null
+++ b/docs/cn/api-reference/async-api/lighting-measured.mdx
@@ -0,0 +1,4 @@
+---
+title: '照明测量'
+asyncapi: 'api-reference/asyncapi.json lightingMeasured'
+---
diff --git a/docs/cn/api-reference/endpoint/academic-standards-search.mdx b/docs/cn/api-reference/endpoint/academic-standards-search.mdx
new file mode 100644
index 0000000..345cce9
--- /dev/null
+++ b/docs/cn/api-reference/endpoint/academic-standards-search.mdx
@@ -0,0 +1,4 @@
+---
+title: '搜索学术标准'
+openapi: 'GET /academic-standards/search'
+---
diff --git a/docs/cn/api-reference/endpoint/change-location.mdx b/docs/cn/api-reference/endpoint/change-location.mdx
new file mode 100644
index 0000000..8e53301
--- /dev/null
+++ b/docs/cn/api-reference/endpoint/change-location.mdx
@@ -0,0 +1,4 @@
+---
+title: '更改位置'
+openapi: 'PUT /plants/{id}/location'
+---
\ No newline at end of file
diff --git a/docs/cn/api-reference/endpoint/create-bulk.mdx b/docs/cn/api-reference/endpoint/create-bulk.mdx
new file mode 100644
index 0000000..1d59ca2
--- /dev/null
+++ b/docs/cn/api-reference/endpoint/create-bulk.mdx
@@ -0,0 +1,6 @@
+---
+title: '批量创建植物'
+openapi: 'POST /plants/bulk'
+---
+
+这是批量创建端点的一些自定义 markdown 内容。
\ No newline at end of file
diff --git a/docs/cn/api-reference/endpoint/create.mdx b/docs/cn/api-reference/endpoint/create.mdx
new file mode 100644
index 0000000..7d509eb
--- /dev/null
+++ b/docs/cn/api-reference/endpoint/create.mdx
@@ -0,0 +1,8 @@
+---
+title: '创建植物'
+openapi: 'openapi/openapi.json POST /plants'
+de_link: "https://developers.example.de/docs/api-reference/endpoint/create"
+fr_link: "https://developers.example.fr/docs/api-reference/endpoint/create"
+---
+
+这是创建端点的一些自定义 markdown 内容。
\ No newline at end of file
diff --git a/docs/cn/api-reference/endpoint/delete.mdx b/docs/cn/api-reference/endpoint/delete.mdx
new file mode 100644
index 0000000..eeb7947
--- /dev/null
+++ b/docs/cn/api-reference/endpoint/delete.mdx
@@ -0,0 +1,4 @@
+---
+title: '删除植物'
+openapi: 'DELETE /plants/{id}'
+---
diff --git a/docs/cn/api-reference/endpoint/get-asset-proof.mdx b/docs/cn/api-reference/endpoint/get-asset-proof.mdx
new file mode 100644
index 0000000..c7e9078
--- /dev/null
+++ b/docs/cn/api-reference/endpoint/get-asset-proof.mdx
@@ -0,0 +1,5 @@
+---
+title: "获取资产证明"
+openapi: "POST /getAssetProof"
+description: "检索压缩 Solana NFT 或代币的加密 merkle 证明。"
+---
\ No newline at end of file
diff --git a/docs/cn/api-reference/endpoint/get-pots.mdx b/docs/cn/api-reference/endpoint/get-pots.mdx
new file mode 100644
index 0000000..0920e59
--- /dev/null
+++ b/docs/cn/api-reference/endpoint/get-pots.mdx
@@ -0,0 +1,4 @@
+---
+title: 获取花盆
+openapi: "GET /pots"
+---
\ No newline at end of file
diff --git a/docs/cn/api-reference/endpoint/get.mdx b/docs/cn/api-reference/endpoint/get.mdx
new file mode 100644
index 0000000..16a5a6a
--- /dev/null
+++ b/docs/cn/api-reference/endpoint/get.mdx
@@ -0,0 +1,7 @@
+---
+title: '获取植物'
+openapi: 'GET /plants'
+de_link: "https://developers.example.de/docs/api-reference/endpoint/get"
+fr_link: "https://developers.example.fr/docs/api-reference/endpoint/get"
+es_link: "https://developers.example.es/docs/api-reference/endpoint/get"
+---
diff --git a/docs/cn/api-reference/endpoint/hierarchy.mdx b/docs/cn/api-reference/endpoint/hierarchy.mdx
new file mode 100644
index 0000000..f19d86a
--- /dev/null
+++ b/docs/cn/api-reference/endpoint/hierarchy.mdx
@@ -0,0 +1,5 @@
+---
+title: "获取植物层级"
+openapi: "GET /plants/{id}/hierarchy"
+description: "获取展示父子关系的植物层级结构"
+---
\ No newline at end of file
diff --git a/docs/cn/api-reference/endpoint/search.mdx b/docs/cn/api-reference/endpoint/search.mdx
new file mode 100644
index 0000000..83939fb
--- /dev/null
+++ b/docs/cn/api-reference/endpoint/search.mdx
@@ -0,0 +1,4 @@
+---
+title: '搜索植物'
+openapi: 'POST /plants/search'
+---
diff --git a/docs/cn/api-reference/endpoint/webhook.mdx b/docs/cn/api-reference/endpoint/webhook.mdx
new file mode 100644
index 0000000..d0488dc
--- /dev/null
+++ b/docs/cn/api-reference/endpoint/webhook.mdx
@@ -0,0 +1,6 @@
+---
+title: '新植物'
+openapi: 'WEBHOOK /plant/webhook'
+---
+
+这是 webhook 端点的一些自定义 markdown 内容。
diff --git a/docs/cn/api-reference/introduction.mdx b/docs/cn/api-reference/introduction.mdx
new file mode 100644
index 0000000..fa4123c
--- /dev/null
+++ b/docs/cn/api-reference/introduction.mdx
@@ -0,0 +1,35 @@
+---
+title: '简介 (Reed Docs)'
+description: '用于展示 API 端点的示例章节'
+de_link: "https://developers.example.de/docs/api-reference/introduction"
+fr_link: "https://developers.example.fr/docs/api-reference/introduction"
+es_link: "https://developers.example.es/docs/api-reference/introduction"
+---
+
+
+ 如果你不打算构建 API 参考文档,可以删除 api-reference 文件夹以移除本章节。
+
+
+## 欢迎
+
+构建 API 文档有两种方式:[OpenAPI](https://mintlify.com/docs/api-playground/openapi/setup) 和 [MDX 组件](https://mintlify.com/docs/api-playground/mdx/configuration)。在此入门套件中,我们使用了以下 OpenAPI 规范。
+
+
+ 查看 OpenAPI 规范文件
+
+
+## 身份验证
+
+所有 API 端点都使用 Bearer 令牌进行身份验证,并从规范文件中获取。
+
+```json
+"security": [
+ {
+ "bearerAuth": []
+ }
+]
+```
diff --git a/docs/cn/api-reference/openapi-test/absolute.mdx b/docs/cn/api-reference/openapi-test/absolute.mdx
new file mode 100644
index 0000000..6cbbb42
--- /dev/null
+++ b/docs/cn/api-reference/openapi-test/absolute.mdx
@@ -0,0 +1,7 @@
+---
+title: '绝对路径引用'
+description: '使用从仓库根目录开始的绝对路径引用规范'
+openapi: '/openapi/openapi-example.json GET /users'
+---
+
+引用 `/openapi/openapi-example.json` — 从仓库根目录开始的绝对路径（以斜杠开头）。
diff --git a/docs/cn/api-reference/openapi-test/explode-false-query.mdx b/docs/cn/api-reference/openapi-test/explode-false-query.mdx
new file mode 100644
index 0000000..f4eb224
--- /dev/null
+++ b/docs/cn/api-reference/openapi-test/explode-false-query.mdx
@@ -0,0 +1,15 @@
+---
+title: 'Explode False 查询参数'
+description: '测试以逗号分隔的 OpenAPI 数组查询参数'
+openapi: 'local-spec.json GET /tweets'
+---
+
+本页面测试使用 `style: form` 和 `explode: false` 的数组查询参数。
+
+Playground 请求应将多个 `tweet.fields` 值序列化为：
+
+```text
+tweet.fields=author_id,attachments,id,text
+```
+
+而不应将相同的选择序列化为多个重复的 `tweet.fields` 查询参数。
diff --git a/docs/cn/api-reference/openapi-test/explode-true-query.mdx b/docs/cn/api-reference/openapi-test/explode-true-query.mdx
new file mode 100644
index 0000000..fc61b52
--- /dev/null
+++ b/docs/cn/api-reference/openapi-test/explode-true-query.mdx
@@ -0,0 +1,15 @@
+---
+title: 'Explode True 查询参数'
+description: '测试重复出现的 OpenAPI 数组查询参数'
+openapi: 'local-spec.json GET /tweets-exploded'
+---
+
+本页面测试使用 `style: form` 和 `explode: true` 的数组查询参数。
+
+Playground 请求应将多个 `tweet.fields` 值序列化为重复的查询参数：
+
+```text
+tweet.fields=author_id&tweet.fields=attachments&tweet.fields=id&tweet.fields=text
+```
+
+可使用本页面与 `explode: false` 版本进行对比，后者应将相同的选择序列化为单个以逗号分隔的 `tweet.fields` 查询参数。
diff --git a/docs/cn/api-reference/openapi-test/index.mdx b/docs/cn/api-reference/openapi-test/index.mdx
new file mode 100644
index 0000000..bcebb58
--- /dev/null
+++ b/docs/cn/api-reference/openapi-test/index.mdx
@@ -0,0 +1,13 @@
+---
+title: 'OpenAPI 引用测试'
+description: '针对不同 OpenAPI 规范引用方式的测试集'
+---
+
+本节用于测试 OpenAPI 规范引用：
+
+- **相对路径** – `openapi/openapi-example.json`（相对于项目根目录的路径）
+- **绝对路径** – `/openapi/openapi-example.json`（从仓库根目录开始的绝对路径）
+- **同目录** – `docs/api-reference/openapi-test/local-spec.json`（规范与 MDX 位于同一目录）
+- **Explode false 查询** – `tweet.fields` 数组查询参数序列化为以逗号分隔的值
+- **Explode true 查询** – `tweet.fields` 数组查询参数序列化为重复的参数
+- **远程** – `https://petstore3.swagger.io/api/v3/openapi.json`（托管 URL）
diff --git a/docs/cn/api-reference/openapi-test/local-spec.json b/docs/cn/api-reference/openapi-test/local-spec.json
new file mode 100644
index 0000000..3e11c48
--- /dev/null
+++ b/docs/cn/api-reference/openapi-test/local-spec.json
@@ -0,0 +1,103 @@
+{
+ "openapi": "3.1.0",
+ "info": {
+ "title": "Local Same-Dir API",
+ "description": "Spec colocated with MDX page",
+ "version": "1.0.0"
+ },
+ "servers": [{ "url": "https://api.example.com" }],
+ "paths": {
+ "/items": {
+ "get": {
+ "summary": "List items",
+ "responses": {
+ "200": {
+ "description": "OK",
+ "content": {
+ "application/json": {
+ "schema": {
+ "type": "array",
+ "items": { "type": "object", "properties": { "id": { "type": "string" } } }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "/tweets": {
+ "get": {
+ "summary": "Search tweets",
+ "description": "Tests comma-delimited query serialization for multi-value fields parameters.",
+ "parameters": [
+ {
+ "name": "tweet.fields",
+ "in": "query",
+ "description": "Select tweet fields. With form style and explode disabled, multiple selected values should serialize as `tweet.fields=author_id,attachments,id,text`.",
+ "required": false,
+ "style": "form",
+ "explode": false,
+ "schema": {
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": ["author_id", "attachments", "id", "text"]
+ }
+ },
+ "example": ["author_id", "attachments", "id", "text"]
+ }
+ ],
+ "responses": {
+ "200": {
+ "description": "OK",
+ "content": {
+ "application/json": {
+ "schema": {
+ "type": "array",
+ "items": { "type": "object", "properties": { "id": { "type": "string" } } }
+ }
+ }
+ }
+ }
+ }
+ }
+ },
+ "/tweets-exploded": {
+ "get": {
+ "summary": "Search tweets with exploded fields",
+ "description": "Tests repeated query parameter serialization for multi-value fields parameters.",
+ "parameters": [
+ {
+ "name": "tweet.fields",
+ "in": "query",
+ "description": "Select tweet fields. With form style and explode enabled, multiple selected values should serialize as repeated `tweet.fields` query parameters.",
+ "required": false,
+ "style": "form",
+ "explode": true,
+ "schema": {
+ "type": "array",
+ "items": {
+ "type": "string",
+ "enum": ["author_id", "attachments", "id", "text"]
+ }
+ },
+ "example": ["author_id", "attachments", "id", "text"]
+ }
+ ],
+ "responses": {
+ "200": {
+ "description": "OK",
+ "content": {
+ "application/json": {
+ "schema": {
+ "type": "array",
+ "items": { "type": "object", "properties": { "id": { "type": "string" } } }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+ }
+}
diff --git a/docs/cn/api-reference/openapi-test/relative.mdx b/docs/cn/api-reference/openapi-test/relative.mdx
new file mode 100644
index 0000000..f655580
--- /dev/null
+++ b/docs/cn/api-reference/openapi-test/relative.mdx
@@ -0,0 +1,7 @@
+---
+title: '相对路径引用'
+description: '使用相对于项目根目录的路径引用规范'
+openapi: 'openapi/openapi-example.json GET /users'
+---
+
+引用 `openapi/openapi-example.json` — 相对于项目根目录的路径（不以斜杠开头）。
diff --git a/docs/cn/api-reference/openapi-test/remote.mdx b/docs/cn/api-reference/openapi-test/remote.mdx
new file mode 100644
index 0000000..8c6dbaf
--- /dev/null
+++ b/docs/cn/api-reference/openapi-test/remote.mdx
@@ -0,0 +1,7 @@
+---
+title: '远程引用'
+description: '通过远程 URL 引用 OpenAPI 规范'
+openapi: 'https://petstore3.swagger.io/api/v3/openapi.json GET /pets'
+---
+
+通过 URL 引用 Swagger Petstore 规范：`https://petstore3.swagger.io/api/v3/openapi.json`。
diff --git a/docs/cn/api-reference/openapi-test/same-dir.mdx b/docs/cn/api-reference/openapi-test/same-dir.mdx
new file mode 100644
index 0000000..969c4d8
--- /dev/null
+++ b/docs/cn/api-reference/openapi-test/same-dir.mdx
@@ -0,0 +1,7 @@
+---
+title: '同目录引用'
+description: '引用与此 MDX 位于同一目录中的规范'
+openapi: 'local-spec.json GET /items'
+---
+
+引用与本页面位于同一目录的 `local-spec.json`。从项目根目录起的路径为：`docs/api-reference/openapi-test/local-spec.json`。
diff --git a/docs/cn/development.mdx b/docs/cn/development.mdx
new file mode 100644
index 0000000..71bfc53
--- /dev/null
+++ b/docs/cn/development.mdx
@@ -0,0 +1,93 @@
+---
+title: "开发"
+description: "在本地预览更改以更新你的文档"
+---
+
+
+ **前置条件**：
+
+ - Node.js 19 或更高版本
+ - 一个包含 `docs.json` 文件的文档仓库
+
+
+请按照以下步骤在你选择的操作系统上安装和运行 Mintlify。我们同时支持 Windows 和 macOS。
+
+
+
+ ```bash
+ npm i -g mint
+ ```
+
+
+ 导航到包含 `docs.json` 文件的文档目录，并运行以下命令：
+
+ ```bash
+ mint dev
+ ```
+
+ 你的文档本地预览将在 `http://localhost:3000` 上可用。
+
+
+
+## 自定义端口
+
+默认情况下，Mintlify 使用 3000 端口。你可以通过 `--port` 标志自定义 Mintlify 运行的端口。例如，要在 3333 端口上运行 Mintlify，请使用以下命令：
+
+```bash
+mint dev --port 3333
+```
+
+如果你尝试在一个已被占用的端口上运行 Mintlify，它将使用下一个可用端口：
+
+```md
+Port 3000 is already in use. Trying 3001 instead.
+```
+
+## Mintlify 版本
+
+请注意，每次 CLI 发布都对应特定版本的 Mintlify。如果你的本地预览与生产版本不一致，请更新 CLI：
+
+```bash
+npm mint update
+```
+
+## 验证链接
+
+CLI 可以帮助验证文档中的链接。要识别任何失效链接，请使用以下命令：
+
+```bash
+mint broken-links
+```
+
+## 部署
+
+如果部署成功，你应该会看到以下内容：
+
+
+ 
+
+
+## 代码格式化
+
+我们建议在你的 IDE 上使用扩展来识别和格式化 MDX。如果你是 VSCode 用户，可以考虑使用 [MDX VSCode 扩展](https://marketplace.visualstudio.com/items?itemName=unifiedjs.vscode-mdx) 进行语法高亮，并使用 [Prettier](https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode) 进行代码格式化。
+
+## 故障排查
+
+
+
+ 这可能是由于 node 版本过旧导致的。请尝试以下方法：
+
+ 1. 移除当前已安装的 CLI 版本：`npm remove -g mint`
+ 2. 升级到 Node v19 或更高版本。
+ 3. 重新安装 CLI：`npm i -g mint`
+
+
+ 解决方案：进入设备根目录并删除 `~/.mintlify` 文件夹。然后再次运行 `mint dev`。
+
+
+
+想了解最新 CLI 版本中有哪些变化？请查看 [CLI 更新日志](https://www.npmjs.com/package/mintlify?activeTab=versions)。
diff --git a/docs/cn/essentials/code.mdx b/docs/cn/essentials/code.mdx
new file mode 100644
index 0000000..233ff6a
--- /dev/null
+++ b/docs/cn/essentials/code.mdx
@@ -0,0 +1,35 @@
+---
+title: '代码块'
+description: '展示行内代码和代码块'
+icon: 'code'
+---
+
+## 行内代码
+
+要将某个`单词`或`短语`标记为代码，请用反引号 (`) 将其包围。
+
+```
+To denote a `word` or `phrase` as code, enclose it in backticks (`).
+```
+
+## 代码块
+
+使用[围栏代码块](https://www.markdownguide.org/extended-syntax/#fenced-code-blocks)：用三个反引号将代码包围，并在起始反引号后写明代码片段所使用的编程语言，即可获得语法高亮。可选地，你还可以在编程语言之后写上代码的名称。
+
+```java HelloWorld.java
+class HelloWorld {
+ public static void main(String[] args) {
+ System.out.println("Hello, World!");
+ }
+}
+```
+
+````md
+```java HelloWorld.java
+class HelloWorld {
+ public static void main(String[] args) {
+ System.out.println("Hello, World!");
+ }
+}
+```
+````
diff --git a/docs/cn/essentials/images.mdx b/docs/cn/essentials/images.mdx
new file mode 100644
index 0000000..0a5290f
--- /dev/null
+++ b/docs/cn/essentials/images.mdx
@@ -0,0 +1,71 @@
+---
+title: '图片和嵌入'
+description: '添加图片、视频以及其他 HTML 元素'
+icon: 'image'
+---
+
+
+
+## 图标图片源
+
+在行内使用本地图片源：，并将其与现有的内置图标路径进行比较：。
+
+在行内使用远程图片源：。
+
+```md
+
+
+
+```
+
+## 图片
+
+### 使用 Markdown
+
+[markdown 语法](https://www.markdownguide.org/basic-syntax/#images)允许你使用以下代码添加图片：
+
+```md
+
+```
+
+请注意，图片文件大小必须小于 5MB。否则，我们建议将其托管在 [Cloudinary](https://cloudinary.com/) 或 [S3](https://aws.amazon.com/s3/) 这样的服务上。然后你可以使用该 URL 并进行嵌入。
+
+### 使用嵌入
+
+要获得更高的图片自定义能力，你也可以使用[嵌入](/writing-content/embed)来添加图片：
+
+```html
+
+```
+
+## 嵌入和 HTML 元素
+
+
+
+
+
+
+
+Mintlify 支持 [Markdown 中的 HTML 标签](https://www.markdownguide.org/basic-syntax/#html)。如果你更喜欢使用 HTML 标签而非 Markdown 语法，这会很有帮助，并让你能够灵活无限地创建文档。
+
+
+
+### iFrames
+
+在文档中加载另一个 HTML 页面。最常用于嵌入视频。
+
+```html
+
+```
diff --git a/docs/cn/essentials/markdown.mdx b/docs/cn/essentials/markdown.mdx
new file mode 100644
index 0000000..87b5a57
--- /dev/null
+++ b/docs/cn/essentials/markdown.mdx
@@ -0,0 +1,116 @@
+---
+title: 'Markdown 语法'
+description: '使用标准 markdown 编写文本、标题和样式'
+icon: 'text-size'
+---
+
+## 标题
+
+最适合用作章节标题。
+
+```md
+## Titles
+```
+
+### 子标题
+
+最适合用作子章节标题。
+
+```md
+### Subtitles
+```
+
+
+
+每一个**标题**和**子标题**都会生成一个锚点，并且会出现在右侧的目录中。
+
+
+
+## 文本格式
+
+我们支持大多数 markdown 格式。只需在文本周围添加 `**`、`_` 或 `~` 即可进行格式化。
+
+| 样式 | 写法 | 效果 |
+| ------------- | ----------------- | --------------- |
+| 粗体 | `**bold**` | **bold** |
+| 斜体 | `_italic_` | _italic_ |
+| 删除线 | `~strikethrough~` | ~strikethrough~ |
+
+你可以组合使用它们。例如，写 `**_bold and italic_**` 可以得到 **_bold and italic_** 文本。
+
+要编写上标和下标文本，你需要使用 HTML，即在文本周围添加 `` 或 ``。
+
+| 文本大小 | 写法 | 效果 |
+| ----------- | ------------------------ | ---------------------- |
+| 上标 | `superscript` | superscript |
+| 下标 | `subscript` | subscript |
+
+## 链接到页面
+
+你可以通过将文本包裹在 `[]()` 中来添加链接。例如，写 `[link to google](https://google.com)` 可以[link to google](https://google.com)。
+
+文档中页面之间的链接需要使用根相对路径。基本上，你应该包含完整的文件夹路径。例如，`[link to text](/writing-content/text)` 会链接到我们组件部分中名为 "Text" 的页面。
+
+像 `[link to text](../text)` 这样的相对链接打开速度会更慢，因为我们无法对其轻松进行优化。
+
+## 引用块
+
+### 单行
+
+要创建一个引用块，在段落前添加一个 `>`。
+
+> Dorothy followed her through many of the beautiful rooms in her castle.
+
+```md
+> Dorothy followed her through many of the beautiful rooms in her castle.
+```
+
+### 多行
+
+> Dorothy followed her through many of the beautiful rooms in her castle.
+>
+> The Witch bade her clean the pots and kettles and sweep the floor and keep the fire fed with wood.
+
+```md
+> Dorothy followed her through many of the beautiful rooms in her castle.
+>
+> The Witch bade her clean the pots and kettles and sweep the floor and keep the fire fed with wood.
+```
+
+### LaTeX
+
+Mintlify 通过 Latex 组件支持 [LaTeX](https://www.latex-project.org)。
+
+8 x (vk x H1 - H2) = (0,1)
+
+```md
+8 x (vk x H1 - H2) = (0,1)
+```
+
+## 折叠面板
+
+当某个章节有一个简短的顶层答案，并在其中可选地包含详情时，使用嵌套折叠面板。
+
+[跳转到常见检查](#deployment-troubleshooting:common-checks)
+
+
+ 从部署日志开始，确认项目使用的是预期的分支。
+
+
+ - 确认最新的提交已完成构建。
+ - 检查所需的环境变量是否已设置。
+ - 修复配置更改后，重新运行部署。
+
+
+
+```md
+
+ Start with the deployment logs and confirm the project is using the expected branch.
+
+
+ - Confirm the latest commit has finished building.
+ - Check that required environment variables are set.
+ - Re-run the deployment after fixing configuration changes.
+
+
+```
diff --git a/docs/cn/essentials/navigation.mdx b/docs/cn/essentials/navigation.mdx
new file mode 100644
index 0000000..f675141
--- /dev/null
+++ b/docs/cn/essentials/navigation.mdx
@@ -0,0 +1,87 @@
+---
+title: '导航'
+description: 'docs.json 中的 navigation 字段定义了出现在导航菜单中的页面'
+icon: 'map'
+---
+
+导航菜单是每个网站上的链接列表。
+
+每次添加新页面时，你都需要更新 `docs.json`。页面不会自动出现。
+
+## 导航语法
+
+我们的导航语法是递归的，这意味着你可以创建嵌套的导航分组。页面名称中无需包含 `.mdx`。
+
+
+
+```json Regular Navigation
+"navigation": {
+ "tabs": [
+ {
+ "tab": "Docs",
+ "groups": [
+ {
+ "group": "Getting Started",
+ "pages": ["quickstart"]
+ }
+ ]
+ }
+ ]
+}
+```
+
+```json Nested Navigation
+"navigation": {
+ "tabs": [
+ {
+ "tab": "Docs",
+ "groups": [
+ {
+ "group": "Getting Started",
+ "pages": [
+ "quickstart",
+ {
+ "group": "Nested Reference Pages",
+ "pages": ["nested-reference-page"]
+ }
+ ]
+ }
+ ]
+ }
+ ]
+}
+```
+
+
+
+## 文件夹
+
+只需将你的 MDX 文件放入文件夹，并更新 `docs.json` 中的路径即可。
+
+例如，要让一个页面位于 `https://yoursite.com/your-folder/your-page`，你需要创建一个名为 `your-folder` 的文件夹，其中包含一个名为 `your-page.mdx` 的 MDX 文件。
+
+
+
+除非将其嵌套在另一个文件夹中，否则你不能使用 `api` 作为文件夹名。Mintlify 使用 Next.js，它将顶层的 `api` 文件夹保留给内部服务器调用使用。诸如 `api-reference` 这样的文件夹名是允许的。
+
+
+
+```json Navigation With Folder
+"navigation": {
+ "tabs": [
+ {
+ "tab": "Docs",
+ "groups": [
+ {
+ "group": "Group Name",
+ "pages": ["your-folder/your-page"]
+ }
+ ]
+ }
+ ]
+}
+```
+
+## 隐藏页面
+
+未包含在 `docs.json` 中的 MDX 文件不会出现在侧边栏中，但仍可以通过搜索栏和直接链接来访问。
diff --git a/docs/cn/essentials/reusable-snippets.mdx b/docs/cn/essentials/reusable-snippets.mdx
new file mode 100644
index 0000000..0d468cd
--- /dev/null
+++ b/docs/cn/essentials/reusable-snippets.mdx
@@ -0,0 +1,102 @@
+---
+title: "可复用片段"
+description: "可复用的自定义片段，让内容保持同步"
+icon: "recycle"
+---
+
+import SnippetIntro from '/snippets/snippet-intro.mdx';
+
+
+
+## 创建自定义片段
+
+**前提条件**：你必须在 `snippets` 目录下创建你的片段文件。
+
+
+ `snippets` 目录中的任何页面都会被视为片段，不会被渲染为独立的页面。如果你希望从某个片段创建一个独立页面，请将该片段导入到另一个文件中，并将其作为组件调用。
+
+
+### 默认导出
+
+1. 在你的片段文件中添加你希望在多个位置复用的内容。可选地，你可以添加变量，这些变量在导入片段时可以通过 props 填入。
+
+```mdx snippets/my-snippet.mdx
+Hello world! This is my content I want to reuse across pages. My keyword of the
+day is {word}.
+```
+
+
+ 你想要复用的内容必须放在 `snippets` 目录中，导入才能正常工作。
+
+
+2. 将片段导入到目标文件中。
+
+```mdx destination-file.mdx
+---
+title: My title
+description: My Description
+---
+
+import MySnippet from '/snippets/path/to/my-snippet.mdx';
+
+## Header
+
+Lorem impsum dolor sit amet.
+
+
+```
+
+### 可复用变量
+
+1. 从你的片段文件中导出一个变量：
+
+```mdx snippets/path/to/custom-variables.mdx
+export const myName = 'my name';
+
+export const myObject = { fruit: 'strawberries' };
+```
+
+2. 从目标文件中导入该片段，并使用变量：
+
+```mdx destination-file.mdx
+---
+title: My title
+description: My Description
+---
+
+import { myName, myObject } from '/snippets/path/to/custom-variables.mdx';
+
+Hello, my name is {myName} and I like {myObject.fruit}.
+```
+
+### 可复用组件
+
+1. 在你的片段文件中，通过以箭头函数的形式导出组件，创建一个接收 props 的组件。
+
+```mdx snippets/custom-component.mdx
+export const MyComponent = ({ title }) => (
+
+
{title}
+
... snippet content ...
+