Zesty.io Supports multiple locales/languages for each content item
When a Zesty.io Content Instance is created, it uses English as the default language. It is possible to add more languages to a Zesty.io Content Instance. Multi-lang content is premium feature of Zesty.io, reach out to your account manager to learn more.
Adding Multi-lang Content
The API must be used to add additional locales/languages to a Content Instance.
Note: adding a language makes that language's relative pages available in preview, to have a added language be accessible to the live production domain, you need to activate the language
Adding a Language
What happens when a new language is added?
When a new language is created, Zesty.io's API will automate a process to duplicate all content into a language specific version of that content. The default language is content is copied into the new language version (it is not automatically translated). For example, if you had an english about page (url /about/), and added Spanish with the locale of Mexico, a new content items would be created with the URL /es-mx/about/ and the content item would be pre-filled with the default language content. These means you would have a Spanish placeholder content item with english words in it to start. All copied new language pages start at version one (with default language content pre-filler) and have their own version control.
The default language can only be chosen at the creation of a content instance. Talk to a Zesty.io support tech for help doing this.
How to Activate a language
Languages are added "non-active" meaning they are not accessible via the published website. It is setup that way so developers can add a language and prepare all the content by updates and publishing without affecting the live website. Once a language is ready to go live, it must be activated.
Activating a Language
How Does Web Engine Handle Multi-lang/Multi-Locale Content
When Web Engine detects there are multiple languages on a Content Instance it will add specific code that is read by browsers, screen readers, and search engines to direct users to different languages/locales of the content it serves.
For example purposes, let's use the domain www.acme.com, and assume it has two languages, English (en-us) and Spanish (es-mx).
Server Headers Appended for Locale/Multi-lang, perMDN Specs****
Server headers served when accessing https://www.acme.com/about/