Sam & Claude
95c487546d
New docs/guide/ tree — canonical home for operator-facing procedural docs. Starlight frontmatter added to all files. 0.12 alignment fixes applied: - v0.11.0 → v0.12.0 throughout - PI_TUI_PROVIDER/MODEL → DEEPSEEK_API_KEY - Headless Codex login → Agent runtime setup (zot + RPC mode) - /login and auth.json references removed - pi → zot in provider-fallback spawn reference - colibri-provider-verify (was pi-provider-smoke) - Language cleanup: smoke test → verification, fake → test, can't self-fix → requires operator intervention, broken → unresponsive, Fix anything broken → Verify all checks pass Two-tree model: docs/wiki/ (decisions) + docs/guide/ (procedural). Single source of truth in colibri. clawdie-ai docs/public/ to be retired.
2.3 KiB
2.3 KiB
| title | description |
|---|---|
| Setup Instructions | Set up Crowdin access and use the current cms-jail Astro workflow for localized docs. |
Setup Instructions
This page covers the current localization setup path.
What you need
- the Clawdie repo checked out on the host
- a Crowdin API token
- a working cms jail with the Astro docs project already provisioned
The docs runtime is not set up as a separate standalone Astro install anymore.
Step 1: Configure Crowdin access
You can provide the token in any one of these ways.
Option A: token file
mkdir -p ~/.config/clawdie
echo "tskey-your-token-here" > ~/.config/clawdie/crowdin-token
chmod 600 ~/.config/clawdie/crowdin-token
Option B: environment file
cd /home/<agent>/clawdie-ai
echo 'CROWDIN_PERSONAL_TOKEN=tskey-your-token-here' >> .env
Option C: shell environment
export CROWDIN_PERSONAL_TOKEN=tskey-your-token-here
Step 2: Verify Crowdin connectivity
Run from the host repo root:
cd /home/<agent>/clawdie-ai
./scripts/crowdin-sync.sh --status
If this works, the localization sync scripts can see your token.
Step 3: Push source strings
When English source docs change:
cd /home/<agent>/clawdie-ai
./scripts/crowdin-sync.sh --push
This publishes source markdown from docs/public/ to the Crowdin project.
Step 4: Pull translations back into the repo
After translators have updated a locale:
cd /home/<agent>/clawdie-ai
./scripts/crowdin-sync.sh --pull
This updates translated markdown under paths like:
docs/public/sl/docs/public/de/docs/public/hr/
Step 5: Deploy localized docs
Deploy still happens through the shared Astro project in the cms jail:
cd /usr/home/<tenant>/<tenant>-docs
npm run deploy
That command:
- syncs host-side docs content into the Astro tree
- builds the static site
- deploys it into the cms jail webroot
Step 6: Verify
Check the live site:
curl -sI https://docs.clawdie.si/
curl -sI https://docs.clawdie.si/en/
Then verify any locale-specific pages you expected to change.
Notes
- Edit markdown on the host, not inside the jail.
- Crowdin manages translations, not deployment.
- Astro deployment is shared with the docs publishing flow, not a separate localization runtime.