chore(sync): mirror docs from openclaw/openclaw@219afbc2cc

.openclaw-sync/source.json

@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "84fb62170a56b18907891b83861092e4933366d4",
-  "syncedAt": "2026-04-05T09:07:10.945Z"
+  "sha": "219afbc2ccb4c1e8997403f2c124836fb0943197",
+  "syncedAt": "2026-04-05T09:31:05.969Z"
 }

docs/docs.json

@@ -124,6 +124,14 @@
       "source": "/context",
       "destination": "/concepts/context"
     },
+    {
+      "source": "/zh-CN",
+      "destination": "/zh-CN/index"
+    },
+    {
+      "source": "/zh-CN/",
+      "destination": "/zh-CN/index"
+    },
     {
       "source": "/compaction",
       "destination": "/concepts/compaction"

docs/plugins/community.md

@@ -13,6 +13,10 @@ channels, tools, providers, or other capabilities. They are built and maintained
 by the community, published on [ClawHub](/tools/clawhub) or npm, and
 installable with a single command.
 
+ClawHub is the canonical discovery surface for community plugins. Do not open
+docs-only PRs just to add your plugin here for discoverability; publish it on
+ClawHub instead.
+
 ```bash
 openclaw plugins install <package-name>
 ```
@@ -116,14 +120,13 @@ We welcome community plugins that are useful, documented, and safe to operate.
 
   </Step>
 
-  <Step title="Open a PR">
-    Add your plugin to this page with:
+  <Step title="Use docs PRs only for source-doc changes">
+    You do not need a docs PR just to make your plugin discoverable. Publish it
+    on ClawHub instead.
 
-    - Plugin name
-    - npm package name
-    - GitHub repository URL
-    - One-line description
-    - Install command
+    Open a docs PR only when OpenClaw's source docs need an actual content
+    change, such as correcting install guidance or adding cross-repo
+    documentation that belongs in the main docs set.
 
   </Step>
 </Steps>

docs/start/getting-started.md

@@ -88,6 +88,38 @@ Need to install Node? See [Node setup](/install/node).
   </Step>
 </Steps>
 
+<Accordion title="Advanced: mount a custom Control UI build">
+  If you maintain a localized or customized dashboard build, point
+  `gateway.controlUi.root` to a directory that contains your built static
+  assets and `index.html`.
+
+```bash
+mkdir -p "$HOME/.openclaw/control-ui-custom"
+# Copy your built static files into that directory.
+```
+
+Then set:
+
+```json
+{
+  "gateway": {
+    "controlUi": {
+      "enabled": true,
+      "root": "$HOME/.openclaw/control-ui-custom"
+    }
+  }
+}
+```
+
+Restart the gateway and reopen the dashboard:
+
+```bash
+openclaw gateway restart
+openclaw dashboard
+```
+
+</Accordion>
+
 ## What to do next
 
 <Columns>