Understanding the Portal 8.0 modularized theme
Modern websites and browsers enable incredible new capabilities that can greatly enhance your user's web experiences. However, these capabilities are not without cost in terms of large page sizes and more processing in the browser when each page is rendered. These capabilities are worth it when you need them, but removing them for an entire site or including them only on pages that take advantage of these capabilities provides for more flexibility.
The module framework
The module framework allows extensions to contribute to different areas of a page to provide flexibility, enhance the user experience, and maximize performance.
Customizing the theme
The module framework allows themes to be customized in order to provide flexibility, enhance the user experience, and maximize performance.
Developing themes for a production portal
All themes must be configured. Some themes have static content. Others have dynamic content. You can develop, package, and deploy themes in various ways.
Updating a Portal 220.127.116.11 theme to use Dojo 1.7
Update an existing Portal 18.104.22.168 theme to use Dojo 1.7, OneUI 3.0 and the status bar.
Updating a Page Builder theme to use Dojo 1.6
Update an existing theme to use modules by making the theme and skins modular. After a theme is modularized, you can use Dojo v1.6.1 and the prepackaged modules for WebSphere
® Portal V8.0. Dojo v1.6.1 is the maximum level supported by a Page Builder theme.
Customizing the site toolbar
The site toolbar can be customized in order to provide flexibility and enhance the user experience.
Device classes are used in IBM
Portal as an abstraction for common properties for the device of a client. For instance, tablet computers can be grouped into a device class tablets
, since they share a form factor and possibly other traits such as touch interface, or additional hardware sensors.