Localisation

DeveloperHub provides localization for your documentation in two ways:

  • Using an automated third party service, such as Localize.
  • By using different documentation for different languages.

Localise using Localize

Localize helps you quickly translate websites and applications into new languages and makes your translation process more efficient.

To use Localize with DeveloperHub, set up a script using Custom HEAD Tags like this:

HTML
Copy

The two options rememberLanguage and saveNewPhrasesFromSource are recommended by Localize.

We manage variables in your documents as specified by Localize.

Localise using different documentation

To localise using different documentation, you need to create documentation for each language.

In your v1.0 version, you can have these documentation sections: en, de, and es. If you already have documentation for Android SDK, iOS SDK, etc., you can expand it to Android SDK (EN), Android SDK (DE), and Android SDK (ES), and so on.

You can customize the UI text to better suit your needs. For detailed instructions, please refer to UI translation.

Which localisation method should I choose?

It depends on how complex your documents and resources are.

If your docs are small enough and you can manage updates in one language and translate it into others, you can use different documentation for each language.

If your docs are large and you want an easy solution, consider using Localize or another third-party service. This makes it simpler to keep all parts of your documentation up to date in different languages. When you add or change content, you'll be asked to approve the new translations, ensuring your docs stay in sync. Plus, you won’t need to change your project structure.

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
  Last updated