duo-localization
Ship your product to people who do not share your language, script, reading direction, demographics or fluency with software — and decide which markets that opens. Covers writing into the register users actually speak instead of the formally correct one, why device locale is a bad proxy for intent, right-to-left as a component problem rather than a string problem, why a copy win in one market does not port, sidestepping grammatical defaults that assert things about the user, how layout silently reverts your content decisions, translating to a consumption budget, and giving local teams authority to diverge from the source text. Use when someone asks how do we launch in another country, should we just translate this, why is conversion worse in this market, does our app work in Arabic or Hebrew, why did our winning experiment fail abroad, or who should own translated copy.
- Version
- 2.0.0
- License
- MIT
Pinned to revision 78072c9528fb, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/duo-localization/SKILL.md
- skills/duo-localization/references/a-winning-message-is-valid-only-where-it-won.md
- skills/duo-localization/references/device-locale-is-not-intent.md
- skills/duo-localization/references/layout-overrides-your-content-policy.md
- skills/duo-localization/references/local-teams-own-expressive-copy-and-full-editions.md
- skills/duo-localization/references/localize-into-the-register-people-speak.md
- skills/duo-localization/references/localize-to-a-consumption-budget.md
- skills/duo-localization/references/reading-direction-is-a-component-problem.md
- skills/duo-localization/references/rewrite-rather-than-default-the-assumption.md
Every link opens the file at its source, pinned to the revision this page describes.