Localization - Getting started

Localization in Document360 is the process of adapting your knowledge base's content, visuals, and behavior to a specific language or region, so readers experience it as if it were built natively for them. It goes beyond translating text — localization can also cover visual styling, formats, and automatic language detection for each reader. Any team serving customers in more than one language or region can use localization to reduce support friction and reach new markets.

What complete localization includes

Complete localization in Document360 covers more than translated article text:

• Visual customization — graphics, color, aesthetics, fonts, and images can be adapted per language.
• Regional formats — units of measure, currencies, and address/date formats can be localized to match the reader's region.
• Automatic language detection — Document360 can detect and load a reader's preferred language based on their login location or browser language settings.
• Cultural relevance — a fully localized knowledge base incorporates nuances that make it feel native, rather than simply machine-translated.

When to use localization

Use localization when:

• Your customer base spans multiple countries or language groups, and a single-language knowledge base creates friction for non-English readers.
• You want to reduce support ticket volume by letting readers self-serve in their native language.
• Your brand needs region-specific visuals, formats, or terminology to feel credible to local customers.
• You want new customers in a target market to find and trust your documentation without relying on browser-based translation tools.

For the setup steps — adding a language to a workspace, translating content, and configuring language settings — see Multilingual Knowledge base.

Best practices

• Use Translate with Eddy AI as a first pass, then review manually. Machine translation gets you a working draft quickly, but human review ensures accuracy and preserves intended meaning — especially for domain-specific terminology.
• Localize all customer-facing content, not just articles. This includes FAQs, user guides, smart bars, cookie consent text, and interface controls, so the experience feels consistent end to end.
• Keep translated content in sync with the source. Use the Review reminder feature to get notified when source articles change, so translations don't silently go stale.
• Prioritize high-traffic content first. You don't need every article translated on day one — start with the content your readers access most, then expand coverage over time.

FAQ