RockChinQ
2957e3a04f
The English and Japanese guide/features pages led their platform enumerations with China-only platforms (WeChat, WeCom, DingTalk), and the "AI customer service" example named China-only platforms to a global / Japanese audience. Reorder the marketing enumerations and examples so each locale leads with the platforms mainstream in its region: - en: Discord, Telegram, Slack first, then QQ/WeChat/WeCom/Lark/DingTalk - ja: LINE, Slack, Discord, Telegram first, then the China platforms Only the hero/landing prose and the use-case examples are reordered; the functional webhook/adapter reference lists are left as-is. The Chinese docs already lead with China platforms and are unchanged. No platform is added that LangBot does not actually support.
LangBot Official Documentation
This repository is the documentation repository for LangBot. Code repository:
LangBot Code Repository
This is the documentation for LangBot 4.0. For 3.0 documentation, please see thev3branch
Contributing to Documentation
The documentation is generated based on Mintlify. Local development requires Node.js installation.
Clone this repository and execute the following command in the directory to install dependencies:
npm install
After completion, you can modify the documentation. After modifications, use the following command to start locally:
npm run dev
Or use the mintlify CLI directly (recommended):
npx mintlify dev
Using Images
Place images in the images directory, then reference them using the absolute path (relative to the project root), such as:
Deployment Details
Now hosted on Mintlify. Commits to the main branch trigger automatic deployment.
Some Standardization Guidelines
- Folder and file naming: Use all lowercase, separate words with
-, such asplugin-intro.mdx - Sub-file (folder) naming: No prefix (i.e., the folder name), such as: in the
deployfolder, the folderlangbot, themanualfile in thelangbotfolder is calledmanual.mdx - Documentation files should use
.mdxformat to support Mintlify components. - Configure sidebar navigation structure in
docs.json.