oomol · alwaysmavs · Dec 20, 2025 · Dec 20, 2025
diff --git a/.trae/documents/Optimize Headless Page for Developers.md b/.trae/documents/Optimize Headless Page for Developers.md
@@ -1,9 +1,11 @@
 I will optimize the `/headless` page to align with the "developer-first" and "freedom" philosophy you described.
 
 ### Plan Overview
+
 The goal is to transform the page from a generic product description to a developer-centric manifesto that emphasizes freedom, open source, and lack of lock-in.
 
 ### 1. Update `src/pages/headless/index.tsx`
+
 I will restructure the page to include a new "Philosophy" section and update the Hero section.
 
 - **Hero Section**: Refocus the message on "Runtime in a Container" and "Run Anywhere".
@@ -15,9 +17,11 @@ I will restructure the page to include a new "Philosophy" section and update the
     - **Trust**: "Code is Law" spirit.
 
 ### 2. Update Internationalization (i18n)
+
 I will update `i18n/zh-CN/code.json` (and English equivalent) with the new copy to ensure the tone is right.
 
 **New Copy Preview (Chinese):**
+
 - **Hero Description**: "本质上是将 OOMOL Studio 的运行环境以容器镜像的方式交付给开发者。自由部署，拒绝捆绑。"
 - **Philosophy Title**: "我们的承诺：自由与开放"
 - **Key Points**:
@@ -26,7 +30,8 @@ I will update `i18n/zh-CN/code.json` (and English equivalent) with the new copy
   - "安心共建：尊重开发者意志，公开透明，Code is Law。"
 
 ### 3. Visual/Structure Changes
+
 - Add a section emphasizing the "Open Source" aspect, possibly with a link to the GitHub repo for the runtime.
 - Use existing UI components (like `FeatureCard`) but repurposed for these new values.
 
-I will proceed with editing `src/pages/headless/index.tsx` and the translation files upon your confirmation.
+I will proceed with editing `src/pages/headless/index.tsx` and the translation files upon your confirmation.
diff --git a/.trae/documents/Redesign Cloud Page with Developer-First Narrative.md b/.trae/documents/Redesign Cloud Page with Developer-First Narrative.md
@@ -1,28 +1,33 @@
 I will update the **OOMOL Cloud** page (`src/pages/cloud`) to reflect the new developer-centric narrative, focusing on "Empathy," "Simplicity," and the "Three Core Modes."
 
 ### 1. Update Translation Files (`i18n/zh-CN/code.json` & `i18n/en/code.json`)
+
 I will update the `CLOUD.*` keys to match the new copy.
-*   **Hero Section:**
-    *   Title: "Focus on Coding, Enjoy Programming" (专注代码，享受编程)
-    *   Subtitle: "You write the Function Block, leave the rest to OOMOL." (你只管写函数 Block，剩下的交给 OOMOL。)
-*   **Pain Points Section (New):**
-    *   Narrative: "Writing code is creative; delivering it shouldn't be a burden. Forget about server provisioning, environment setup, and deployment headaches." (作为开发者，我们深知：写代码是创造的乐趣，但交付往往是枯燥的负担...)
-*   **Three Modes (The Solution):**
-    *   **Function Library:** Share and compose (发布为函数库，供他人复用或组合)
-    *   **Serverless API:** One-click deploy, auto-scaling (部署为云函数，提供 Serverless API 服务)
-    *   **MCP for AI:** Native AI integration (以 MCP 方式提供给 AI 调用)
-*   **Pricing/Closing:**
-    *   "Pay-as-you-go. No upfront costs. Save money, save effort." (按调用收取费用，不用预支钱。省钱省力，享受编程。)
+
+- **Hero Section:**
+  - Title: "Focus on Coding, Enjoy Programming" (专注代码，享受编程)
+  - Subtitle: "You write the Function Block, leave the rest to OOMOL." (你只管写函数 Block，剩下的交给 OOMOL。)
+- **Pain Points Section (New):**
+  - Narrative: "Writing code is creative; delivering it shouldn't be a burden. Forget about server provisioning, environment setup, and deployment headaches." (作为开发者，我们深知：写代码是创造的乐趣，但交付往往是枯燥的负担...)
+- **Three Modes (The Solution):**
+  - **Function Library:** Share and compose (发布为函数库，供他人复用或组合)
+  - **Serverless API:** One-click deploy, auto-scaling (部署为云函数，提供 Serverless API 服务)
+  - **MCP for AI:** Native AI integration (以 MCP 方式提供给 AI 调用)
+- **Pricing/Closing:**
+  - "Pay-as-you-go. No upfront costs. Save money, save effort." (按调用收取费用，不用预支钱。省钱省力，享受编程。)
 
 ### 2. Update Page Component (`src/pages/cloud/index.tsx`)
+
 I will restructure the page layout:
-*   **Hero:** Update title, description, and stats to highlight "No Ops" and "Pay-as-you-go".
-*   **Pain Points Section:** Add a new text-focused section to present the "Developer's Dilemma" narrative with affinity.
-*   **Core Modes Section:** Replace the generic "Use Cases" with the specific "Three Modes" (Library, API, MCP) as described.
-*   **Value/Pricing Section:** Emphasize the "Pay-as-you-go" model and "Enjoy Programming" philosophy.
+
+- **Hero:** Update title, description, and stats to highlight "No Ops" and "Pay-as-you-go".
+- **Pain Points Section:** Add a new text-focused section to present the "Developer's Dilemma" narrative with affinity.
+- **Core Modes Section:** Replace the generic "Use Cases" with the specific "Three Modes" (Library, API, MCP) as described.
+- **Value/Pricing Section:** Emphasize the "Pay-as-you-go" model and "Enjoy Programming" philosophy.
 
 ### 3. Update Styles (`src/pages/cloud/styles.module.scss`)
-*   Add styling for the new **Pain Points** section (clean, readable typography, centered layout).
-*   Adjust existing card styles if necessary to fit the new content structure.
 
-This approach ensures the page speaks directly to developers' pain points and clearly presents OOMOL Cloud as the solution, exactly as requested.
+- Add styling for the new **Pain Points** section (clean, readable typography, centered layout).
+- Adjust existing card styles if necessary to fit the new content structure.
+
+This approach ensures the page speaks directly to developers' pain points and clearly presents OOMOL Cloud as the solution, exactly as requested.
diff --git a/.trae/documents/Redesign Studio Page to Developer Philosophy.md b/.trae/documents/Redesign Studio Page to Developer Philosophy.md
@@ -4,18 +4,19 @@ I will redesign the `src/pages/studio/index.tsx` page to be a "Design Philosophy
 
 1.  **Shift Tone:** Change from "Product Marketing" to "Engineering Blog/Manifesto".
 2.  **New Structure:**
-    *   **Header:** "Built by Developers, For Developers."
-    *   **The "Why" (The Frustration):** A storytelling section about why traditional workflow tools fail developers (black boxes, proprietary DSLs, bad editors).
-    *   **The "How" (Design Decisions):**
-        *   **Principle 1: Code is the Source of Truth.** Explaining the `Node == Function` mapping.
-        *   **Principle 2: Respect the Tooling.** Why we integrated full VS Code (Monaco) and LSP, not just a text area.
-        *   **Principle 3: No Artificial Limits.** Why we use real Docker containers, allowing full `npm`/`pip` access.
-    *   **The Result:** A brief summary of what this enables (bridging visual & code).
+    - **Header:** "Built by Developers, For Developers."
+    - **The "Why" (The Frustration):** A storytelling section about why traditional workflow tools fail developers (black boxes, proprietary DSLs, bad editors).
+    - **The "How" (Design Decisions):**
+      - **Principle 1: Code is the Source of Truth.** Explaining the `Node == Function` mapping.
+      - **Principle 2: Respect the Tooling.** Why we integrated full VS Code (Monaco) and LSP, not just a text area.
+      - **Principle 3: No Artificial Limits.** Why we use real Docker containers, allowing full `npm`/`pip` access.
+    - **The Result:** A brief summary of what this enables (bridging visual & code).
 3.  **Visual Style:**
-    *   Use a cleaner, editorial layout (more whitespace, better typography).
-    *   Use code snippets side-by-side with "Node" visuals to demonstrate the mapping.
-    *   Remove the repetitive "Feature Grid" and "Comparison Table" that duplicates the homepage.
+    - Use a cleaner, editorial layout (more whitespace, better typography).
+    - Use code snippets side-by-side with "Node" visuals to demonstrate the mapping.
+    - Remove the repetitive "Feature Grid" and "Comparison Table" that duplicates the homepage.
 
 **File Changes:**
-*   `src/pages/studio/index.tsx`: Complete rewrite of the content.
-*   `src/pages/studio/styles.module.scss`: Update styles for the editorial/manifest layout.
+
+- `src/pages/studio/index.tsx`: Complete rewrite of the content.
+- `src/pages/studio/styles.module.scss`: Update styles for the editorial/manifest layout.
diff --git a/.trae/documents/优化 OOMOL App 页面方案.md b/.trae/documents/优化 OOMOL App 页面方案.md
@@ -3,53 +3,61 @@
 我将根据您的设计思路，重构 `/app` 页面，使其更具开发者亲和力，并清晰传达 "Block 函数 -> C 端产品" 的核心价值。
 
 ## 1. 核心叙事调整
+
 将页面重心从简单的 "功能罗列" 转移到 "开发者价值实现" 上。
 **核心理念**：OOMOL App 是连接 **开发者代码 (Block)** 与 **用户需求** 的桥梁。
 **流程**：`编写函数 (Block)` -> `OOMOL 封装` -> `交付产品 (Chat/Applet)`
 
 ## 2. 页面结构设计
 
 ### A. Hero 区域 (首屏)
+
 - **标题**: "OOMOL App：交付 AI 产品的最后一公里"
 - **副标题**: "无需编写 UI，将你的 Block 函数直接转化为 AI Chat 技能与 Applet 小程序，瞬间交付给用户。"
 - **CTA**: 保留下载与文档链接，增加 "查看示例"（如果有）。
 
 ### B. 概念阐述 (The "Why")
+
 - **文案**: "代码即产品 (Code is Product)"。
 - **视觉/描述**: 展示一个简单的函数代码片段，经过 OOMOL 处理，分别变成 "对话界面" 和 "表单界面" 的示意。
 - **开发者痛点解决**: 强调 "零前端代码"、"自动参数解析"、"即刻上线"。
 
 ### C. 双产品介绍 (The "What")
+
 采用对比或并列布局，清晰区分 Chat 与 Applet 的定位：
 
-| 产品 | **OOMOL Chat (AI 助手)** | **OOMOL Applet (表单小程序)** |
-| :--- | :--- | :--- |
-| **定位** | AI 辅助执行 (AI-Assisted) | 直接功能调用 (Direct Execution) |
-| **用户场景** | **"我不清楚具体怎么做"**<br>需求模糊，需要 AI 拆解任务、组合工具。 | **"我知道我要什么"**<br>需求明确，高频使用，追求速度与精准。 |
-| **开发者视角** | **Tools as Skills**<br>你的函数成为 AI 的技能/手脚。 | **Function as App**<br>你的函数直接生成独立小应用。 |
-| **交互形态** | 自然语言对话，多轮交互。 | 结构化表单，填参即用。 |
-| **Icon** | 🤖 智能助手 | 📱 小程序/表单 |
+| 产品           | **OOMOL Chat (AI 助手)**                                           | **OOMOL Applet (表单小程序)**                                |
+| :------------- | :----------------------------------------------------------------- | :----------------------------------------------------------- |
+| **定位**       | AI 辅助执行 (AI-Assisted)                                          | 直接功能调用 (Direct Execution)                              |
+| **用户场景**   | **"我不清楚具体怎么做"**<br>需求模糊，需要 AI 拆解任务、组合工具。 | **"我知道我要什么"**<br>需求明确，高频使用，追求速度与精准。 |
+| **开发者视角** | **Tools as Skills**<br>你的函数成为 AI 的技能/手脚。               | **Function as App**<br>你的函数直接生成独立小应用。          |
+| **交互形态**   | 自然语言对话，多轮交互。                                           | 结构化表单，填参即用。                                       |
+| **Icon**       | 🤖 智能助手                                                        | 📱 小程序/表单                                               |
 
 ### D. 开发者亲和力优化 (Developer Affinity)
+
 - **术语使用**: 使用 "参数 (Parameters)"、"返回值 (Return Values)"、"函数调用 (Function Call)" 等开发者熟悉的词汇。
 - **视觉元素**: 在介绍功能时，配合代码视角的注解。例如 "Applet 界面 = 自动根据 Schema 生成 UI"。
 
 ## 3. 执行计划
 
 ### 1. 修改 `i18n` 翻译文件
+
 - 在 `i18n/zh-CN/code.json` 中添加新的文案 Key (如 `APP.new.hero.title`, `APP.product.chat.desc` 等)。
 - 在 `i18n/en/code.json` 中添加对应的英文翻译，确保国际化支持。
 
 ### 2. 重构 `src/pages/app/index.tsx`
+
 - 移除旧的 `useCases` 和 `coreFeatures` 数据结构。
 - 实现新的页面布局：
-    - **Hero**: 强调 "函数交付"。
-    - **Concept**: 插入新的概念介绍段落。
-    - **ProductSplit**: 左右分栏展示 Chat 和 Applet。
+  - **Hero**: 强调 "函数交付"。
+  - **Concept**: 插入新的概念介绍段落。
+  - **ProductSplit**: 左右分栏展示 Chat 和 Applet。
 - 保持原有的设计风格 (SCSS)，复用 `Layout` 和通用组件。
 
 ### 3. 验证
+
 - 确认中英文案显示正确。
 - 确认页面响应式布局正常。
 
-请确认此方案，我将开始执行。
+请确认此方案，我将开始执行。
diff --git a/docs/cloud-services/_category_.json b/docs/cloud-services/_category_.json
@@ -0,0 +1,10 @@
+{
+  "label": "Cloud",
+  "position": 5,
+  "link": {
+    "type": "generated-index",
+    "description": "Cloud services including Connect Service and Headless deployment."
+  },
+  "collapsed": true,
+  "className": "sidebar-submenu-item"
+}