This guide helps CMS Lite users create, manage, and publish non-English content. Follow these steps to ensure your content is consistent, accessible, and user-friendly across languages.
For translating communications products, contact your ministry’s Communications Director.
For all other content, translation services can be procured from the Corporate Supply Arrangement.
Along with English, CMS Lite and gov.bc.ca officially support 12 languages:
Other languages, such as Russian and Ukrainian, may be rendered, but page features will be in English.
Ensure that both English and non-English versions have a uniform structure, including headings, paragraphs, and lists. It is essential that both versions convey the same message and information.
Cloning from English content in CMS Lite is the first step. Remember to always paste unformatted text to avoid hidden language tags from word processing documents. Use "Paste as plain text" or "Paste from Word" buttons where appropriate.
Note: For languages that read content from right to left, some formatting may need to be adjusted or changed.
To remove background formatting, shown in the text editor as a blue highlight:
Note: Do not remove blue highlights for non-English text tagged on an English language page.
The language selector allows users to easily switch between languages. It links to other language versions of the same page.
It looks like this:
English | 繁體中文 | 简体中文 | Français | ਪੰਜਾਬੀ | Tagalog
The language selector is added immediately below the introduction on all non-English pages, as well as the English version. The language for the active page should not be linked. This shows the reader at a glance where they currently are.
If your content changes frequently and you are unable to publish updates to all languages at the same time, non-English pages may be temporarily out-of-date. Include a notice on non-English pages directing readers to the English version for the latest information.
The standard wording (in English) is:
For the most up-to-date information, view this page in English.
This line is installed in the page language underneath the language selector on all non-English pages.
When there are English and non-English versions of a page, it's helpful to include the publication date in the metadata. This helps users of non-English pages see if updates have been made to match the English page.
Use hyperlinks to connect the user with information in the same language. If content being linked to is only available in English, make that clear after the link.
For example:
Link to assets which are in the page language when possible. Translate alt text used for images or other assets into the page language so that they can be read by screen reader software.
Do not update anchor names to non-English languages. Anchor names created on a non-English page should match the English version. When a page is cloned from English, these should already be set.
Learn how to use the Rich text editor for multimedia, formatting, and navigation.
For accessibility reasons, all non-English text must be tagged in CMS Lite.
Use the Page language field on the Settings tab.
The labels in the content body, including supplemental content boxes, will change to the selected language. However, labels and links in the header and footer are hard-coded in English and will not update.
Use the Set Language icon to tag the text.
Tagging text with the correct language signals screen readers to switch to the appropriate language. This ensures proper pronunciation for visually impaired users. An example of individual words which have been tagged can be seen in the language selector.
For pages that are entirely in a non-English language, you must update all page and asset metadata to the page language. This includes images, alt-text, and PDFs.
Update the titles on the Settings tab.
Title: 卑詩福利資訊站
Nav Title: 卑詩福利資訊站 (B.C. Benefits Connector)
Page Path: tc
Title: 醫療保健
Nav Title: 醫療保健 (Health care TC)
Page Path: health
Update Metadata using the Metadata tab.
Use the Tags tab to update social media preview text.
Select the language for non-English assets (images, documents, PDFs):
Any keywords or other metadata used for PDFs should be in the page language.
Use the following checklist before publishing non-English language page content.
8. Approval
Get approval from GCPE. Any materials prepared for public consumption must be approved by GCPE through the Communications Director assigned to your ministry