IBM Web Content Manager - The IBM Learner Portal is currently ...

When you are developing a website using IBM Web Content Manager and WebSphere Portal, you are
splitting the elements of your website between content, context, layout, and style.
Content:
There are two types of content:
Dynamic
Dynamic content is generated dynamically based on a set of preconfigured parameters,
such as navigator or menu.
Static
Static content is content where you store markup or files directly in a component, content
item or site area. Where you store your static content depends on how the content will be
used:
v Page-specific content is stored in content items.
v Content related to a section of your site may be stored in a site area.
v Content that is reused in multiple sections of your site is stored in components.
Layout:
The layout and structure of each page in your website are defined using the following:
v The overall structure of each page is determined by the theme you are using, the page layout
you have chosen, and the web content viewer portlets you have added to the page layout.
v The layout of the content displayed within each web content viewer is determined by markup
used by the current presentation template, and by the markup stored within the elements and
components referenced within the presentation template.
Context:
The context of the content currently displayed is also important. The layout and design of the
page where a content item is displayed will be different depending on:
v The current portal page (Different pages may use different themes, layouts, web content viewer
portlets, and even different presentation templates.)
v The current site area (Content linked to different site areas may use different template maps
that map to different site areas.)
v The current user (Different users may have different access to various page elements, including
individual pages, portlets, and web content items.)
Style:
Each of these contextual variables allows you to display content or components in different ways,
depending on the current context. Additionally, the profile of the current portlet, content item, or
current user can determine what is displayed on a page, as do any personalization features used
by your website.
While you can place stylistic elements directly within your HTML, it is becoming increasingly
more common to use CSS to store and manage all the stylistic elements of a website. In a IBM
Web Content Manager site, the CSS can be:
v Stored server-side and referenced within a WebSphere ® Portal theme
v Stored directly within a content item or component
Accompanying guide for SPVC - not for distribution
One good practice is to store your CSS markup within an HTML field stored in a content item.
This allows you quick access to the CSS if you need to make a change. In addition you can use
advanced features such as workflows and inline editing to help you maintain your CSS. By
storing all your stylistic elements in CSS, you can quickly make stylistic changes to your website
simply by editing a CSS file instead of editing multiple items.
When a web page is rendered, IBM Web Content Manager takes all these individual item types and
combines them to build a complete web page.
2 IBM Web Content Manager: Developing Websites Using IBM Web Content Manager 7 (Student Guide)