3.1.2 Componentization and the page design concept 

Table of contents Next Previous

Componentization and the page design concept

One of the many strengths of Lotus Web Content Management is the use of componentization . The elements of a Web page are created as distinct units and then are put together in a variety of ways. This function allows you to create flexible Web pages that authors can create simply and that administrators can maintain easily. Each of the elements that are created can be reused in many other pages and in other elements. So, each element should be designed from the beginning to be reusable and modular. See Figure 6 illustrating an example Web page in which some typical component types are highlighted. The menu component is reused in the homepage.


Figure 6 Components on the River Bend page (31_6)

Figure 7 below illustrates the relationship between components and shows how a Web page is a composite of design and content components. In essence, a typical Web page can be constructed from the following elements:

• Presentational layer :

The look and feel that controls how the page should be presented. Determining factors include:

• What device or type of browser is intended for displaying the information
• Font, color and other graphical components to be displayed

• Content layer :

The information about the page. Determining factors include:

• Content input using a content template
• Tools for accessing content, such as authentication (sign in), search, and so forth

• Information architecture layer :

How the content fits into the overall site information structure. Determining factors include navigational aids, such as a navigator, menus, and breadcrumbs.

Figure 7 Web page component layers (31_7)
The concept of componentization remains consistent throughout the different roles that are associated with creating, maintaining, and administering a Web site, namely authoring, site design, and maintenance processes. This componentization allows for the traditional, encompassing role of a Web master to be separated into a more specific role.

Considerations for reusability

The concept of componentization is derived from the concept that a user can create a component once and reuse it many times in various different contexts and design areas. This reusability can be achieved by adhering to the following guidelines:

• Use a naming convention for the objects that is descriptive to make it easier for other developers to identify objects for reuse. The River Bend Web site uses prefixes such as NAV for navigators and Menu for menus.
• Identify the different types of pages in the site and look for common elements between the pages.
• Remember that you can use additional information components to allow content creators to customize a Web page to their needs.
• A site can often be broken down into a set of page styles, such as the Home page, content pages, menu pages, and so forth. You can then deploy these pages across the site to maximize reuse.

Attention: While it is true that components can be reused many times, take care to ensure that these components are not too dissected and nested such that they became cumbersome to maintain. In addition, remember that nesting components can impact page rendering and site performance.

Tips: Preferably, all objects should be modular so that they do not rely on any other object to close a < table   tag or to put < script   tags around it. You should be able to change a component slightly without having to change any other elements that rely on that component. All functionality should remain within the component that needs it (either coded directly in the component or in the form of another complete component).