Sam & Claude
a3048cdef2
- New page: docs/guide/sl/reference/okrajsave.md (15 abbreviations explained in plain Slovenian — LLM, JSON, JSONL, ACL, PF, NAT, ZFS, API, HTTPS, TCP, SHA, BCP, ISO, UI, VPS) - Linked from reference index - First occurrence of each abbreviation in every Slovenian page now links to the glossary - Fix broken ./install/ link (English + Slovenian) - requirements title: 'Zahteve' → 'Osnovne zahteve' - prettier-clean
2.1 KiB
| title | description |
|---|---|
| Troubleshooting | Common localized-docs problems in the Astro/Starlight cms-jail workflow. |
Troubleshooting
Localized page does not appear on the site
First make sure the translated markdown exists in the repo at the mirrored path:
ls docs/guide/sl/operate/terminal-capture.md
The locale path must match the English page's relative path exactly. Then redeploy from the cms jail project:
cd /usr/home/<tenant>/<tenant>-docs
npm run deploy
If that succeeds, verify the live route with curl.
A page shows English inside an otherwise translated locale
That is expected: a locale only overrides the pages you have translated.
Untranslated pages fall back to the default (English) locale. Translate and
commit the missing page under docs/guide/<lang>/ to replace the fallback.
Locale route 404s
Check that:
- the file exists under
docs/guide/<lang>/at the right path - the locale is enabled in the Starlight config of the cms-jail docs project
- you redeployed after adding the file
Build fails inside the cms jail
Use the runtime path for builds and deploys:
cd /usr/home/<tenant>/<tenant>-docs
npm run build
A common cause is malformed frontmatter in a translated file — confirm the
title: / description: keys are intact after translation.
Docs deploy works, but translations still look stale
Check whether the translated markdown was actually committed before the deploy:
cd /home/<agent>/clawdie-ai
git diff -- docs/guide/sl docs/guide/de
If there are no new locale changes, the deploy is working and the content simply was not updated yet.
Tenant sites disappeared after a docs deploy
That should not happen. The docs deploy path protects:
/usr/local/www/<tenant>/sites/
If tenant-site output was still removed, inspect the deploy script in the Astro project and confirm the protected-path behavior is still present.
If a future Crowdin integration is added, pull/sync failures against Crowdin would be a separate class of problem documented alongside it. Crowdin is not part of the current flow.