What is docs?

OpenClaw's documentation site is what you're looking at when you read the guides and references at docs.openclaw.ai. This particular repository is a mirror, a publishing pipeline that takes documentation written elsewhere, translates it into multiple languages, and serves it as a fast website with built-in search and a language picker. The actual English source material lives in a separate repository, and this one is specifically designed to receive, translate, and publish it. The process works in stages. When someone updates the English docs in the main repository, an automated workflow copies those changes here. Then translation workflows kick in, using an AI model to generate localized versions of each page. The system is smart about efficiency: it tracks which files have actually changed and only re-translates those, skipping everything else to save time and cost. A weekly scheduled run acts as a safety net, catching anything that was missed during incremental updates. The final site is built as static files, uploaded to Cloudflare's hosting platform, and served through a lightweight router that handles clean URLs and search requests. This setup is for the team maintaining OpenClaw, the people writing documentation, managing translations, and keeping the docs website running smoothly. For example, if a developer updates an installation guide in English, this pipeline automatically figures out which translated versions need refreshing, generates them, and publishes the updated site. Contributors who want to fix a typo or clarify a paragraph should edit the English source in the main repository, not here, since this repository is essentially generated output. What's notable is the careful engineering around cost and reliability. Translation is expensive, so the system avoids re-translating unchanged pages and retries automatically when the AI model returns something malformed. Incremental updates and full weekly translations run on separate tracks so a small edit doesn't accidentally cancel a larger reconciliation job. The upload process similarly avoids re-uploading files that haven't changed, keeping publishing fast and cheap.