Create static content for the portal

WebSphere Portal creation of pages with portal content using static HTML or other markup.

Create a an HTML page using standard web authoring tools or a text editor. We can include portlets as dynamic elements, and containers as placeholders for portlets in the pages. We can display these portlets using server side aggregation, AJAX, or iFrame techniques. We can update an existing static page by uploading a modified HTML file while preserving the portlet customization on that page.

Static pages can be rendered in the portal by the following two ways:

• As standalone web pages that control the complete browser area.
• As part of the portal content area. In this case the portal still controls the banner and navigation area.

We can deploy and manage the static content pages using any of the portal administration tools.

We can use portlet communication with static pages, for example by wires.

Compared to dynamic content pages based on the portal container model, static HTML pages also have the following characteristics:

• We create and administer static pages similarly as other portal pages.

• To update a static page, make changes in the HTML file, then replace the portal page with the updated page using the Manage Pages and Properties portlets or other portal administration tools. We can use the portal Page Customizer to update the static page layout if the static page contains portlet containers defined by the portlet container microformat.

• We provide national language support by bundling localized markup files into the a compressed file, together with the HTML file that defines the static content. At rendering time the portal globalization algorithms decide which locale will be rendered, based on the request, on settings, and on the locall available.

• The portal defines a set of microformats for skins and portlet actions, such as configuring the portlet settings, portlet communication, and navigation for rendering. These microformats are designed to be styled by CSS provided by the static page author.

• Static pages can include drag and drop actions. These actions are defined via a microformat. Users with the appropriate access rights can drag and drop UI elements, such as portlets or pages.

• We provide JS, CSS, or image files for static pages by bundling them into a compressed file, together with the HTML file that defines the static content. These resources can then be referenced via relative links from the static page template.

• We can have static pages rendered by server side aggregation or by client side aggregation.

• Use skins and other graphic features with static content: When we write a static page and include it in the portal, the portal can render the page itself, but not with the visual features that we might have configured for the portal.

  For example, we cannot encode skins within static pages. When the portal renders such a page, portlets on the page are rendered without a skin. To have portlets on static pages rendered with a skin, we use CSS style sheets or JavaScript that later use the microformats at rendering time.

The following topics describe how created static pages in HTML, and what features we can use.

When you have written the static page, we can include it in the portal using the Manage Pages portlet.

Decision point: After including a page in the portal, we cannot change the page from static content to standard portal layout or from standard portal layout to static content. To change the page type after you have created it, you need to delete the existing page and create a new page of the required type.

When a static page uses the default Portal 8.0 theme, Portal 7.0.0.2 theme, or Page Builder theme, users can change the style of the page, but they cannot change the layout of the page or add content to it.

See

• Define and render a static portal page in HTML

Parent: Create static content
Related:
Including static content pages in the portal