Software Development
Docs Localization Strategy
Decides whether, where and how to localize developer documentation - which languages from traffic, browser-language and market evidence, machine, LLM, human or community translation, which pages first and which never, per-page source-commit pins, drift detection, outdated banners, fallback, locale ownership and retirement. Use whenever someone asks whether or how to translate their docs, a Japanese or Brazilian Portuguese docs site, LLM-translating the documentation, a community translation program, translated docs falling out of date, or whether a language is worth it. Do NOT use for translating one file or README on request, or for product UI string i18n. Do NOT use for hreflang or canonical fixes - use samber/developer-relations-skills@docs-seo.
- Publisher / source
- samber/developer-relations-skills (found on skills.sh)
- Upstream record
- samber/developer-relations-skills
- Version
- Version 2
- Published
- Publication review
- Approved for publication
- Content fingerprint
f2456becc13e03276cb32c511391e4bb6b2e9a20c53b74861d0dfd4d182420b3