Skip to content

Translation Workflow

User roles

Mukurtu manager, protocol steward, language steward, contributor, language contributor, curator, community record steward

Mukurtu CMS sites support translation into one or more languages through the Mukurtu Multilingual module. Once the module is configured and a language is added to your site you can translate site components and content in any order you choose, but following this workflow can streamline translation.

Once the Mukurtu Multilingual module is installed and a language is added, site content can be translated. There are several different types of fields that make up content forms in Mukurtu, and they are configured separately. For instance, full HTML fields in content can be translated by inputting the translation directly into the field, but fields that are populated by taxonomy terms must be translated in the taxonomy.

Enable Mukurtu Multilingual and add languages

Refer to the Enable Multilingual Mode article to configure Mukurtu Multilingual and add one or more languages to your site.

Configure font

Refer to the Configure Font article to configure custom fonts on your Mukurtu CMS site. For most sites this is not required.

User interface translation

Refer to the User Interface Translation article for instructions on how to translate your user interface. User interface translation allows a translator to search for specific translated and untranslated strings. Because translation tasks involve many strings, user interface translation allows translators to export, edit, and import translations as a .po file.

Configuration translation

Refer to the Configuration Translation article for instructions on how to translate all the configuration text on their site that has translatable text, such as the site name, role names, and other structural components.

Translate taxonomies

Refer to the Translate Taxonomies article for instructions on how to translate taxonomy vocabularies on your site.

Translate Local Contexts directory descriptions

Refer to the Translate Local Contexts article for instructions on how to translate Local Contexts directory descriptions.

Local Contexts projects and labels must be translated at the Local Contexts Hub. Visit Local Contexts: Working with the Labels in the Hub for more information.

Translate content

Tip

Translating site content can be labor intensive. To ensure content can be accessed when browsing in all languages, we recommend creating and saving a translation for all content when it is created, even if no fields are translated. This will make content available in it's original language when it's viewed if there is no translation yet.

For instructions on how to translate content, refer to Translate Content