Class attributes for components on static pages | HCL Digital Experience

When you place a component on a static HTML page to be rendered by the portal, use a suitable CSS file to format the portlet. The CSS file uses the component microformat. You can use this microformat if you want to render components on your static HTML page with a skin of your choice. When you write the static page, you can use CSS or JavaScript techniques to convert the microformat into a friendly user interface. The component references in the static HTML page are replaced by the content of the component and the component microformat.

For more information, see the following list of class attributes for portlet components. An example of a component that is rendered from HTML is also provided.
portlet-window / component-control
This value of the class attribute identifies the containing <div> tag for the component window as it was defined by the web designer when the static page was written. The style attribute and the name attribute contain the same information that was provided by the author of the page on the <div> element that referenced the component. The attribute id-ObjectID is the prefixed object ID of the component window, which is globally unique in the portal. Refer to the following example for rendering a page from full HTML markup:
      <title>Sample Static Page</title>
      <p>This is a static page example.</p>
      <p>Welcome component</p>
      <div class="component-container" name="componentContainer1">
         <div class="portlet-window component-control" name="componentWindow1" 
              style="portlet-definition:wps.p.Welcome To WebSphere Portal">
This value of the class attribute introduces the metadata section of the portlet. All metadata is encapsulated in this container so that it can be hidden by CSS. The xoxo class denotes that this contains a list of items.
This value of the class attribute represents the localized title of the portlet. The lang attribute identifies the actual locale.
This value of the class attribute lists the different portlet actions or operations that can be started in the portlet window.
Note: Such operations are not necessarily actions in the sense of HTTP. Instead, some actions are safe interactions, whereas others can be unsafe, as they modify the server. In the list of actions each interaction is either represented as a link to denote a safe interaction or as a form to denote an unsafe interaction.
This value of the class attribute describes the actual actions or operations. Those actions that would result in an idempotent operation are denoted by the selected attribute. In addition, each action is classified by an action-specific attribute to allow CSS to style these actions, for example, by adding action-specific icons. The list of possible actions is computed on the server by using the Operations Feed. This feed is extensible, and therefore new operations can be added over time.
This value of the class attribute denotes the body of the portlet.
This value of the class attribute identifies the beginning of the microformat for placing an iWidget instance on a static page. Additional information about the iWidget microformat for including iWidgets into a broader set of markup, such as a portal page, provided by the iWidget specification and on the topic about Including iWidgets in a static page.
This value of the class attribute identifies a selected item, either the portlet itself or an action. If it appears on the <div> tag for the portlet window, this means that the portlet was the target of the interaction that produced the page.
This value is an optional class on the portlet window. It denotes that this portlet window can be dragged around on the screen by users. This attribute is valid only if the portlet window is part of a modifiable portlet container, and if the user has the rights to modify the page and the container is not locked. Refer to the Container Microformat to see how a drop target is represented and how the actual drag and drop operation can be done.
Note: A drag and drop action is triggered from the client side, but is run on the server.
This attribute denotes that the following is a list of items.

Example of rendering a component from HTML

The following is an example of a microformat representation for a portlet window on a page:

<div class='portlet-window' id='7_CGAH47L00OGRB02DA9LR6H1024' name='window2' >
   <ul class='xoxo portlet-info' >
      <li class='portlet-title' lang='en'>
      <li class='portlet-actions' >
         <ul class='xoxo portlet-action' >
            <li class='portletoperation-view selected' >
               <a href='?uri=wp.operations:onPortletModeView
                  rel='view' >Back</a>
            <li class='portletoperation-normal selected' >
               <a href='?uri=wp.operations:onWindowStateNormal
                  rel='normal' >Restore</a>
            <li class='portletoperation-minimized' >
               <a href='?uri=wp.operations:onWindowStateMinimized
                  rel='minimized' >Minimize</a>
            <li class='portletoperation-maximized' >
               <a href='?uri=wp.operations:onWindowStateMaximized
                  rel='maximized' >Maximize</a>
            <li class='portletoperation-delete_portlet' >
               <form method='POST' action='?uri=wp.operations:onDeletePortlet
                     rel='delete_portlet' >Delete</form>
   <div class='portlet-window-body' >