How Translations Get to Your Website

A more technical description of how Localize works

The following details how Localize delivers translations for your application. It assumes that you have already used Localize to add the translations for your source content.

  1. The first time a user loads a page in your website, the Localize library is called to retrieve the translations for the currently selected target language.
  2. Localize puts the translations for all published phrases in the Project into one file (for the currently selected target language), and sends it back to the browser.
  3. The translations are stored in the browser's cache to optimize performance.
  4. The Localize library then replaces the source language with the target language phrases in the current web page, and the web page is displayed to the user.
  5. When the user navigates to another page, the translations are already loaded in the browser, so no translations need to be downloaded, resulting in a quicker load time on subsequent pages.

User Data

Localize will not bring in user data entered in form fields in your website. This is for security reasons.

How Translations Get to Your Website


A more technical description of how Localize works

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.