Layout of the portal page
Before customizing your portal site, it helps to understand the underlying structure of the portal as it is determined by the portal JSPs. The portal page is composed of JSPs for screens, themes, and skins that are typically created by the Web designer of the portal. These JSPs reside in the corresponding /screens, /themes, /skins directories under...
was_root/installedApps/hostname/wps.ear/wps.war
Within this location, subdirectories for markup, locale, and client types are used to support portal aggregation.
- themes
- determine the look and layout of the portal, including colors, fonts, and images outside of the portlet content area (Home screen). Themes often provide the initial navigation to portal pages.
- screens
- the area of the portal that typically displays portlets (Home screen), but can also display other content in its place, for example, a login form or error message. Screens are selected from navigation icons in the theme.
- skins
- represent the border rendering around components, such as row containers, column containers, or portlets. Skins also provide navigation to levels deeper than the navigation that is provided by the themes. Skins can use the theme name to select the graphics that match the theme colors. Skins are installed independently from themes. However, the administrator can set a default skin for a theme.
The starting place for building the portal page is Default.jsp in the /themes directory. The screen and skin are called by the corresponding <wps:screenRender/> and <wps:compositionRender/> tags from the engine tag library.
|
Theme (Default.jsp) ...
|
See also