Connect through language too
We want people to find a way into what we share. We look after translations while keeping each publication’s voice and original words.
The website language and a story’s language
Navigation and institutional pages have their own Spanish, English and Portuguese versions. An entry may have been written in another language: that is its original language. Keeping these two things separate prevents the menu from determining the translation by mistake.
How Google helps
The website uses reviewed or saved translations for the current version of an entry. To create new translations within the website, we can configure Cloud Translation API Basic v2 in Account administration. That Google Cloud integration needs its own configuration and billing; installing the ZIP does not activate it.
Using the Google Translate link
If a translation is unavailable, the link opens the publication in Google Translate with the known original language and the visitor’s selected language. Very short texts may need Google to detect the source. Choosing an original language in the editor helps avoid confusion. External translation depends on Google, and checking the meaning remains worthwhile.
The original words stay here
A translation never replaces the stored original. Its links, images and structure remain available. Forms or calendars embedded from other services may have language choices of their own.
How search engines find us
SEO includes the care we take with clear titles, metadata, language-specific addresses and a sitemap. This information uses lowercase roscaille foundation. Internal tools and the guide ask search engines not to index them. Search results may take time to change until the engine visits the page again.
Alpha 1.5.3 · Building on the September 2026 baseline