Skip to main content

Cookie control banner

Necessary Cookies
These cookies are necessary for this website to function correctly. They are set when you perform certain actions on the site, such as creating an account, logging in, changing your privacy preferences or submitting a form. You can block these cookies in your browser, but this will stop parts of the site from working properly.
Functional Cookies
These cookies allow the website to provide extra functionality and more personalised experiences. They may be set by us or by third party providers whose services we have added to our pages. If you choose not to allow these cookies, these services may not work correctly.
Analytical Cookies
These cookies record anonymous data on how visitors use our website to help us monitor how well our website works. This data includes how many people have looked at specific pages, how long visitors stay on the site, and what devices they use. We use this data to identify changes that we could make to improve your experience and make our website more efficient.
Marketing Cookies
We set some cookies so you are shown more relevant marketing content. These include cookies from third-party advertising networks to show you different adverts on their services if you have previously visited our site. If you choose not to allow these cookies, you may experience less relevant advertising on other sites.
Browse Documentation

Translate an entry

Created by Contensis product team, last modified by r.bromley on 24 Sep 2020

Translating an entry follows a common language workflow. Entries can only be translated into another language once there is a published version of the default language. This workflow ensures that as the default language entry is updated, authors of different languages will see that a change has been made. The change will be highlighted by the entry's workflow state, such as when an entry has Never been translated.

Note: We consider the default language as the common business language used in a project, from which all other languages are translated.

All language variations are associated with a default language entry. The default language entry acts as a container for all language variations (the default language is always the same as the default language of a project). The number of languages available for a given entry will depend on those supported by the content type.

After an entry has been created and published in the default language, each language variation will become available for translation.

Translate an entry from the language panel

  1. Press the Entries button in the sidebar to open the Entries listing screen. You can reduce the number of entries displayed using the Type filter. The entry listing will update to show all entries for the content type you've selected.
  2. Locate the entry requiring translation in the listing. If the entry is available in other language variations you will see Show other languages in the language column of the listing. Press Show other languages. The language panel will be displayed.
  3. The language panel shows all language variations for the entry. Entries awaiting translation will have an action to translate, whilst those already translated will be available to edit. Pressing Translate or Edit will open the entry in a split view entry editor for translation.
  4. You can now populate the fields for the new language. The copy field option can be used to quickly copy content from one language to the language variation where content remains the same.
  5. Press Save between any changes – the minor version will increment upon each save. When you have finished, press the Submit or Publish button. Once published the language variation will be available through the Delivery API, together with the default language content.

Note: In the split view entry editor, the left-hand panel displays the default language content unless the language has been changed in the dropdown. The other panel represents the language you are currently editing.