While you might create your very own content type model, the following description is based on the assumption that you use the content type model of CoreMedia Blueprint. For a custom content type model you must meet certain requirements which are described at the end of this section.

Content Types

CMLocalized is the parent content type that defines all required properties for the multi-site feature. Any content item in any site must be of a type that is a child of CMLocalized. Any content items within a site violating this requirement, may trigger improper or unexpected behavior during operational tasks such as translating or synchronizing content items. For further information see Section 7.1, “Content Type Model”.

<DocType Name="CMLocalized" Parent="CMObject" Abstract="true">
  <StringProperty Name="locale" Length="64"/>
  <LinkListProperty Name="master" Max="1"
                    LinkType="CMLocalized"
                    extensions:weakLink="true"/>
  <IntProperty Name="masterVersion"/>
  ...
</DocType>

Weak Link Attribute

The contents of each site have to be published and withdrawn independently of their master. Therefore, the weakLink attribute of every master property must be set to true - see also Content Type Model - LinkListProperty in Content Server Manual.

Attributes for Translation

The attributes extensions:translatable and extensions:automerge, which can be attached to all properties, affect the translation behavior. extensions:automerge also affects the synchronization behavior.

Translatable Properties

The properties that have to be translated to derived sites can be marked as translatable in the content type model by attaching the extensions:translatable attribute to the property declaration - see also Content Type Model - Translatable Properties in Content Server Manual.

Section “Translatable Predicate” describes other ways to mark a property as translatable, for example to mark nested properties of a Struct property as translatable.

<DocType Name="CMTeasable" Parent="CMHasContexts" Abstract="true">
  <LinkListProperty Name="master" Max="1"
                    LinkType="CMTeasable"
                    Override="true"
                    extensions:weakLink="true"/>
  <StringProperty Name="teaserTitle" Length="512"
                  extensions:translatable="true"/>
  <XmlProperty Name="teaserText" Grammar="coremedia-richtext-1.0"
               extensions:translatable="true"/>
  <XmlProperty Name="detailText" Grammar="coremedia-richtext-1.0"
               extensions:translatable="true"/>
  ...
</DocType>

Automatically Merged Properties

Usually all property changes from the master content will be merged automatically to the derived content when a translation task is accepted. To disable automatic merging for a property, set the extensions:automerge attribute to false as described in Content Type Model - Translatable Properties in Content Server Manual.

For a synchronization workflow, all properties are synchronized, by default, between a master content and its derived content. You can disable this behavior by setting extensions:automerge to false or by unchecking the checkbox Keep synchronized with Master of the content in Studio (see Section 4.7.4.3, “Removing Content Permanently from Synchronization” in Studio User Manual for details).

Custom Content Type Models

Even if it is not recommended, you can use your own content type model with the Multi-Site feature of CoreMedia Content Cloud. Prerequisite is, that you can configure the Site Model mentioned before to meet the requirements of your own content type model. In addition, you probably need to adapt your content type model to fit the requirements of the multi-site concept.

Therefore, every content type, which may occur in a site must contain all properties, listed below.

Please adapt the configuration of each property to the properties of CMLocalized in the example above.