You can change the profile for a specific page to define the modules loaded.

You can change the profile for the theme or a specific page to define the modules loaded.

You can change the profile for the theme or a specific page to define the modules loaded.

The process of assigning a device class to one of the supported clients in WebSphere Portal. Usually, when a certain device class needs to be supported, the first step is to create client definitions for each of the devices that belong to this class. Then, you create a device class and assign the ...

You can manually assign a device class to a client.

IBM® WebSphere Portal offers a filtering feature for portlet capabilities based on the existing client side capabilities.

To enable device support, which represents your static page for different device classes, bundle the static markup files that are deviceclassspecific into a compressed file.

Device classes are used in IBM® WebSphere 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 ...

Set the following properties in the Wp ConfigService Resource Environment Provider to enable or disable the various capability filters.

You can create and delete device classes using the XML configuration interface.

This example creates a client that matches devices sending iPhone in the user agent. The device class smartphone is also assigned to the client.

You can scope layouts so that only certain ones show up in your custom theme. The IBM® WebSphere Portal 7.0.0.2 theme included with the portal uses this technique.

Add static content for the custom theme you created based on one of the portal readyuse themes.

You can add modules to your profile to use IBM® Sametime® with the IBM WebSphere Portal 7.0.0.2 theme.

The module framework can optimize the markup for adding the data from various contributions based on the type.

Modules can contribute different types of data to the extension points within the page.

You can make your custom skin the default skin for your custom theme

You can add dynamic content to your custom theme by using either clientside or serverside logic.

One of the features of the theme is its draganddrop capability for arranging layout content. The drag and drop framework within IBM® WebSphere Portal is based on the implementation of Dojo.

You now have a unique copy of the dynamic resources for your theme. However, you still need to modify the dynamic resource references in the static resources of the theme to point to the dynamic resources for your theme rather than the dynamic resources for the IBM® WebSphere Portal 7.0.0.2 ...

Create your own module if IBM® WebSphere Portal does not provide a module with the functions or configurability that you need.

The second order of theme configuration is through resource environment provider (REP) custom properties in the WP GlobalThemeConfig REP. Changes to the REP custom properties apply across all themes, and the values, therefore, cannot vary from theme to theme.

Theme metadata properties are specific to a single theme. To reinforce this scope, it is good practice to prefix your property names with yourTheme. If you have a property that you want to apply across multiple themes or a property that is specific to a module, set up a resource environment ...

Avatars are used to represent the item being dragged. You can customize the look and feel of the avatar.

Instructions on how to include a custom dynamiccontent spot in a theme template: