Content libraries

Content libraries store the assets for the website, including but not limited to pages, content, images, authoring and presentation templates, and workflows.

All pages are stored in a Portal Site library. The Portal Site library is immediately available and includes the welcome page, getting started page, and more. Create more libraries to store the website content and assets. We can create multiple libraries to organize your content or to reflect the companies structure. We might create a library for a specific department that requires different access control. In most cases create a minimum of two libraries:

1. A design library where you store all the items required for the web content system itself

2. A content library used to store the content that is developed by the content creators

The access control and syndication configuration is unique for each library created.

When we are searching through content libraries, we can search for items by their titles. However, if we choose to sort items by title, the sorting option filters pages by the Unique name or Identifier of the page, and not the title specified in the page settings.

New libraries and default items

When creating a new library, we can select to include default items. The default items are helpful if we are not familiar with standard library assets such as authoring templates, presentation templates, and workflows. Include the default items to see examples we can customize and use.

To create a new library, open the administration portlet and click Portal Content > Web Content Libraries.

When we create a web content library, ensure the name of the library does not match the URL context of any virtual portals on the same server. If the name of a library and the URL context of a virtual portal have the same value, incorrect rendering behavior can result.

When to use the Portal Site library with Web content

Storing web content in the Portal Site library

• This scenario is easy to setup, but means the content cannot be syndicated, exported or imported separately.

• Managed pages must be enabled.

• The Web content will be moved or deleted when a page is moved or deleted.

Storing web content in dedicated content libraries

• This scenario is easy to deploy so long as the content mappings are setup correctly. The content can be syndicated, and exported or imported separately.

• The Web content is associated with a page using a Web content mapping.

• The Web content will not be moved or deleted when a page is moved or deleted.

• Web content can be stored in separate libraries, allowing us to logically organize the content, and setup separate syndication scenarios.

• Create libraries
  Web content libraries are used to store the web content and managed pages. Syndication is used to keep libraries in synch between the different server environments.

• Web content library default items
  When creating a web content library, we can choose to include a set of default web content items in the new library. These items can be used as a starting point for the WCM system and website.

Parent Build the website

Related concepts:

IBM Web Content Manager Multilingual Solution
Create a content library