Portal style classes
The CSS style sheets that are used for the portal page are dynamically generated by JSPs located in the /themes/Portal/ directory. You can change the tag definitions and the class definitions in the CSS style sheets. However, verify you do not delete any style sheets or remove any style classes. Portlets require these style classes for JSP output. The Page Builder theme does not support the portal style classes.
Dynamically generated style sheets require far fewer files to support variations based on locale, browser, and color palette.
The following provides information about the CSS File structure:
styles.jsp root page which includes children styles_cacheSettings.jspf sets headers to control how the output CSS is cached styles_rules.jspf defines logic to be consumed by style definitions styles_theme.jspf contains style definitions for the theme styles_portlet.jspf contains standard styles for portlets styles_ibm.jspf contains styles for IBM portlets styles_help.jspf contains styles for portlet help files styles_oob.jspf contains styles for out of box Information portlet JSPs
Modify dynamic styles
All logic controlling the generation of dynamic styles is contained in styles_rules.jspf. This JSP fragment creates a map of rules for use by the style definitions. Refer to this file for the rules available for use in style definitions, as well as to modify the logic as required for installation.
To add own additional styles, create own JSP fragment, such as styles_myStyles.jspf, and modify styles.jsp to include it as well. In this way, styles are incorporated into the portal style sheet and are able to use the dynamic rules.
Cache dynamic styles
Dynamic styles vary their output by browser, locale, and color palette. The tag...
<portal-theme:cacheProxyUrl>
.generates a cacheable url to styles.jsp that encodes the browser, locale and color palette variables. This allows the output CSS to be cached by the server for improved performance.
Style classes for portlets
The style sheets that are used by WebSphere Portal contain classes that can be used by portlets to ensure visual consistency among portlets on the page. Using these classes ensures that no matter what theme has been selected, the portlet look and feel matches that of other portlets and the portal page.
To determine which classes to invoke in portlet output, portlet developers can examine the styles_portlet.jspf file that is located in the IBM WAS directory:
$PORTAL_HOME/installer/wp.ear/installableApps/wps.ear/wps.war/themes/html/Portal/
The file includes comments explaining the use of each class.
Portlet helps use the style classes in styles_help.jspf. For most tags, using class="help" ensures that the portlet help renders consistently with helps for other portlets on the page.
Parent
Customize the portal
Work with portal navigation
Use JSTL tags in the portal JSPs
Related tasks
Import a theme
Deploy the theme
Create a new skin
Enable automatic JSP reloading
Add support for new clients
Add support for new markup languages
Change banner text
Use the color palette in themes
Performance guidelines for themes and skins