Home Page Template

Last Updated 10.10.02

General Description

The home page template is the first page of the application a user typically sees. It is used to provide the user an overall picture of the functionality and contents of an application. It can provide content status and be a page that informs a user which items or tasks need attention. There are also several template options available for a home page of an application. This guideline contains the following information regarding home page templates: Other page templates, like the Overview Page Template, may be used in place of one of the home page templates listed above. This type of "home" page is a typical starting point for step by step processes.

Guideline Attributes

Spec Version # - 3.1
Spec Contributors - Betsy Nute
UI Models - all models
Example Products - all products
Related Guidelines - Tabs, Page Footer Options, Content Templates, Search Templates, Help Methods, Messaging Dialogs (Errors, Info, Warning)


Interaction and Usage Specifications

Home Page Template Components
Below lists the components that are used in a Home Page Template.

General Home Page Template Usage Principles

Typical Content Used in Various Columns Within a Home Page

Content Matrix for Home Pages - Intranet Home Pages vs. Internet Home Pages
Below are common types of content seen in an application home page. This content should not be cross product, but product specific. The Oracle Applications Portal is the location for cross product content. Below lists common content that is seen in intranet vs. intranet applications. The third column displays typical Portal content. The portal content should be used as reference only.
Intranet Home Page Content Internet Home Page Content Typical Portal Content
Content within portal should typically not be repeated in a home page.
  • Notifications - Product notifications only.
  • Search - Search functionality for within product only.
  • News - Product specific news displayed only.
  • Overview of Tasks and Content - Subheader sections used to logically group content.
  • Summary Data regarding application - May be a summary table, or shortened table with access to full list, like "Most Recent Expense Reports." May also contain status info.
  • High level navigation structure for application - Tab/Navigation that is persistant through application is present.
  • Common Navigation Links to deeper into product - to common tasks/flows below the level 1 tab bar.
  • Categories or Catalog of Items/Objects - If a catalog is applicable to application.
  • Welcome information/High Level Application Instructions
  • Notifications - Product notifications only.
  • Search - Search functionality for within product only.
  • News - Product specific news displayed only.
  • Login/Logout Information - Internet applications typically have notion of "guest user" vs. "registered user." When logged in, the registered user typically has more functionality exposed within application and more priveledges.
  • Summary Data regarding application - May be a summary table, or shortened table with access to full list, like "Most Recent Purchase Orders. " May also contain status info.
  • High level navigation structure for application - Tab/Navigation that is persistant through application is present.
  • Common Navigation Links to deeper into product - to common tasks/flows below the level 1 tab bar.
  • Categories or Catalog of Items/Objects - If a catalog is applicable to application.
  • Welcome information/High Level Application Instructions
  • Notifications - all products notification, not product specific.
  • Search - Search functionality for portal.
  • News - News from all products/industries/domains.
  • Calendar - Calendar applicable to all corporate events, product events, etc.
  • List of all Applications
  • Application specific content - Portlets surfaced at portal level with application content or links to specific tasks within an application. The portlet does not have functionality, just content. [This information is customizable by the user.]
  • Current Documents
  • Business Intelligence Information
  • Favorites - customizable list of favorite links
  • See Oracle Application Portal specifications for greater details.

Content Flow for Home Pages
  • Follow a vertical columnar layout, with content displayed from top to bottom of a page in columns. Horizontal layout is not recommended since the contents of sections/containers within the page may not line up, and there may be excessive vertical white space.


Visual Specifications

Home Page Templates

Open/Closed Issues

Open Issues

Closed Issues

09.11.00 - duplication of portals functionality should be avoided.
09.11.00 - Terminology of "Home" may be reevaluated. Currently "home" is also a tab in portal. May want to change applications "home" tab so user does not get confused with 2 homes. Update:Jan 2002 - portal does not have a "home" tab.