Unlayer Documentation

Unlayer Documentation

Welcome to Unlayer Documentation. It takes less than 5 minutes to get our editor up and running on your project.

These guides will take you through the process and get you up and running.

Get Started    

Localization

You can change the locale used in Unlayer's user interface as part of the configuration parameters passed to the plugin.

The locale value needs to be passed to the initialization code in ISO 639-1 format (example: en-US). The default locale is set to en-US.

Available Languages

Currently, we have the following translations available. Please submit translations in your language and we'll add them to the bundle.

LanguageRegionCode
ArabicUAEar-AE
ChineseChinazh-CN
ChineseTaiwanzh-TW
DanishDenmarkda-DA
EnglishUSAen-US
EnglishCanadaen-CA
EstonianEstoniaet-EE
FarsiIranfa-IR
FinnishFinlandfi-FI
FrenchFrancefr-FR
FrenchCanadafr-CA
GermanGermanyde-DE
ItalianItalyit-IT
KoreanKoreako-KR
PortugueseBrazilpt-BR
RussianRussiaru-RU
SpanishSpaines-ES
SwedishSwedensv-SE
TurkishTurkeytr-TR

Submitting Translations

You can submit new language translations by creating a PR on this GitHub repo: https://github.com/unlayer/translations


Opening the Editor

You can pass the locale when initializing the editor. The default is en-US.

unlayer.init({
  ...
  locale: 'en-US'
});

Overriding Translations

You can override any word or sentence of any language like this:

unlayer.init({
  ...
  locale: 'en-US',
  translations: {
    'en-US': {
      "tools.tabs.content": "Content",
      "tools.tabs.row": "Row"
    }
  }
});

Available Keys

You can check all available translations keys here: https://github.com/unlayer/translations/blob/master/en.json

Updated 3 months ago


Localization


Suggested Edits are limited on API Reference Pages

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