Defining and rendering a static portal page in HTML
To include a new static portal page in the portal, first create an HTML file.
You can create this page by starting with a static HTML file or an HTML fragment.
When you use only characters that can be encoded in ASCII in the names of the compressed file and the directories and files within the compressed file, you can use a compressed tool of choice to create the file package. If you use characters that are not ASCII encoded, for example special characters or DBCS, in the names of the compressed file and the directories and files within the compressed file, you need to create the compressed file by using the JRE tool jar.exe.
- The static HTML file can contain references to portlets, containers, and navigation. It defines the places in the portal page that host portlets or portlet containers. When the page is rendered, these places are filled by the server with the - possibly dynamic - content of portlet and with a microformat that defines metadata for these portlets, for example, portlet actions and the portlet title. For this purpose, the portal provides the following microformats:
- The portlet microformat. This defines portlet windows and portlet actions, such as Edit default settings, Configure, Maximize, Minimize, Personalize, and Delete.
- The container microformat. This defines portlet containers as placeholders for portlets.
- For drag-and-drop actions, the portlet microformat can provide the drag source, and the container microformat provides the drop target.
- The navigation microformat. This defines the navigation if static page is rendered as a web page.
The portlet window and portlet container microformats can contain object IDs. The server can handle these object IDs dynamically.
When you write the static page, you can use CSS or JavaScript techniques that use the microformats to produce and render a user friendly user interface.
- You can define whether the static page is rendered as a web page or as part of a portal page:
- To render the page as a standalone static page, include the <html> element as a root element in the markup file.
- To render the page as part of a portal page, omit the <html> element.
- You can also include other resources as part of the page, such as cascading style sheets or graphic images. You need to bundle all the files into a compressed file. This single compressed file is then used to create or update the static page.
- You can use portal frameworks such as Live Text with static pages. To achieve this, include static page as part of a dynamic portal page when you add the static page to the portal in a later step.
- To enable globalization, that is to represent static page in different languages or locales, you bundle localized static markup files into a compressed file.
For example, these can be HTML files, graphic files, such as JPGs, style sheets such as CSS or JS files. Observe the following naming convention for localized files: For a base file base_file_name.file_name_extension, you need to name the localized version of the file base_file_name_locale.file_name_extension. Example: For a base file named my_page.html, the English version of the file is my_page_en.html, and the US English version of the file is my_page_en_us.html. Although these files have different file names, they logically represent the same resource and are referenced by references to their base name. The portal serves the localized version of the resource when appropriate.
- Example HTML markup for defining a portal page
- Class attributes for portlets on static pages
- Class attributes for a portlet container on static pages
- Class attributes for components on static pages
- Class attributes for iWidgets on static pages
- Navigation options for static pages
- Portlets for adding dynamic elements to static pages
Parent
Create static content for the portal