Device classes and Portal resources
A client can be assigned a device class by assigning a capability. The name of the capability must start with com.ibm.portal.devicesupport.deviceclass= and continue with the administrative name of a device class, as provided with their definition.Pages
Device classes can be used to filter pages from the content model. For more information, read Filtering the content model.Layout templates
A layout template for a static portal page can specify variants for device classes that use a naming convention. The layout template that matches the client's device class can then be used to render the page. For more information about how to define static pages and layout templates, read Defining and rendering a static portal page in HTML.Theme modules
Parent topic: Responsive Web Design
Creating and deleting device classes
Assigning device classes
Registering theme modules
Filtering the content model
Defining and rendering a static portal page in HTML
A contribution in a theme module can define subcontributions for a specific device class. For more information, read Registering theme modules.
Additional information about device classes for developers
There are several ways to obtain information about device classes for developers.
scheme is a special URI format that accesses different resources, depending on the device class. This scheme is used by the Portal 8001 theme in the definition of several dynamic content spots.