Multi-Site Management, Localization, and Translation
MSM (Multi-Site Manager) manages live copies of a blueprint. Understand blueprints, live copies, rollouts, and inheritance. Live copy relationships are defined by cq:LiveRelationship and cq:LiveCopy properties; rollouts push changes from blueprint to live copies, and inheritance can be canceled per component/property. Know the rollout configurations and synchronization triggers.
Localization uses language copies and the translation framework. Understand the translation project, translation connectors (e.g., human vs machine), and the translation cloud service configuration. Language copies can be created as live copies or independent copies-know the tradeoff. The i18n dictionary and HTL @ i18n support UI localization.
Traps: confusing live copy (inherits and syncs) with language copy (a translated duplicate); assuming inheritance can't be broken (it can, per property); forgetting that rollout configs determine what syncs. Another trap: translation projects require a configured connector and cloud config; without it, the workflow stalls. Also, MSM and language copies can conflict if both are applied to the same tree.
Worked example: to translate a site, create a language copy for /content/mysite/fr from the English master, then create a translation project referencing the connector; translated content is written back to the language copy.
Rule of thumb: live copies sync structure/content from a blueprint; language copies hold translated content-choose deliberately.