Translating CMS content for a multilingual store
Key Takeaway
Add translation languages to the workspace before you export content. After you import, publish the managed content, because imported translations arrive in Draft status.
Salesforce CMS translation lets you offer CMS content in more than one language. You first add translation languages to a CMS workspace. Then you move each content item through a translation lifecycle: export it for a localization partner, import the translated files, and publish. In a multilingual B2B store, CMS translation covers CMS content, while store data and labels are translated with separate tools.
Where you do CMS translation
CMS translation is available in Lightning Experience in Enterprise, Performance, Unlimited, and Developer Editions. You work in the Digital Experiences app, which was previously named Salesforce CMS. You open it from the App Launcher.
You can translate content in a CMS workspace and in an enhanced CMS workspace. The steps to add languages differ between the two workspace types. The translation lifecycle differs too.