...
For organizations with several channels and multiple publication channels (multi-channel publishing), it is often essential to be able to manage content from a central location and to reuse it in multiple places. This means not only content but also web users, forms etc. In a default installation with more than one channel, all content is strictly separated. Content sharing is not done automatically, so if you want to do this you have to configure it. Most of these configuration properties involve assigning different read/write permissions for different channels. Editors of the various channels must explicitly allow one another to read and reuse content. By explicitly specifying what can be read per channel, everything can be set up in a safe and flexible manner.
...
| Note |
|---|
In the following sections, the term "content" is used in a broader context and is used should be regarded as a synonym for regular content types, model types, settings, web users, etc. Language labels don't belong to this form of content. Language labels are maintained in a single object pool that is valid for all channels (see Language Labels). |
...
In order to share content between channel A and channel B, the configuration has to be changed to be able to expose (share) the content of one channel with another as well as to receive (accept) content from another channel. Sharing content is configured in three steps. For each channel, specify the following:
- Which content types are is available for sharing.
- Which content should be shared with which other channel(s).
- Which content should be accepted from other channel(s).
In this example, we will configure two channels so that articles from the Content repository Repository are shared between channel A and channel B, and editors on both channel A and B are able to add new articles and to use each other’s articles on their channel.
...
Below is a list of all model types that can be shared. When there are no comments for a model type, the individual items of a model type can be shared. For example, with the queries you can choose on a query level which queries are shared or not.
...
Model Type | Comment |
Application integration: filter definitions | |
Applications | |
| Content Repository | The entire Content Repository is always shared and not individual content types. |
Form resources | Form resources and form steps |
Form models | |
Form rules (all handlers) | |
| Forms | |
Languages | |
Page section labels | |
Personalization | Both personalization expressions as well as personalization models |
Presentations | Only presentations and no presentation variants |
Queries | |
| User groups | |
Web users | All web users are always shared and not individual web users. |
...
Multiple Channels versus Language Switch
...
Language Switch | Extra Channels |
The site structure for all language versions of the channel is the same. Not all pages have to be translated or published. | Each channel has its own site structure. |
Authorization per language is not possible. An editor can edit pages and page sections content in all the available languages. | Authorization is fully adjustable per channel. Each channel has its own edit environment. |
All languages use the same presentation. | There are many ways to separate the design or share parts of the design between several channels. |
No additional license is required to maintain multiple language versions of your channel(s), however it does require extra development work. | An additional license is required for each extra channel. |
...