Create websites for different localities

Although websites that automatically display content for different localities or languages are not directly supported by Web Content Manager, it is possible to maintain separate libraries within Web Content Manager for different localities.

Create libraries and search collections for different localities

When creating a multi-locale solution, IBM recommends that you do the following:

• Create a separate library for each locality.

• Create another library for any content that will be shared across localities.

• Create a separate search collection for each locality.

If a language does not exist in the list of languages available when creating a library, we can add that language to the list of supported Web Content Manager languages. See "Language Support" in the Web Content Manager information center for further information.

Naming consistency

IBM recommends that the same names are given to corresponding items in each library. This will simplify the navigation between localities as only the library name will be different in URLs pointing to the same content in different localities. For example, only the library name will be different for content displayed in French and German localities:

• http://host/wps/connect/frenchlibrary/sitearea/content

• http://host/wps/connect/germanlibrary/sitearea/content

Maintain content in different localities

At present, Web Content Manager does not manage the synchronization of content between localities.

A workflow can be used to assist with the synchronization of content between localities using the joint approval feature. We can add a stage to a workflow that would require joint approval from a member in a group representing each locality. You would configure this stage to send an email to notify each joint-approver that an item has been updated. Each joint-approver would not approve the item until they had updated the same item in their locality to match the changes in the primary locality.

Parent: Developing