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.
The home page contains aggregated information from throughout the application.
The type of information that should appear on a home page are frequently
or recently used items and/or current status information.
It is recommended that all applications have some type of "home" page or start page to give
the users an overall picture of the functionality and contents of the application.
The layout of the home page template may vary among applications. (See rest
of this guideline for more details.)
The common home page templates are:
1 Column
Home Page
2 Column
Home Page
(with Ancillary Information)
2 Column
Home Page
(without Ancillary Information)
3 Column
Home Page
Other templates with similar purposes as a "home" page may also substitute
layouts shown above. Below lists another valid template that can be used
in place of a "home" page:
Overview Page Template - This
is typically used as the "home page" for step by step processes.
The appropriate home page template should be chosen based on the content,
hierarchical structure and amount of information needed to be surfaced at
the top level of the application.
An intranet application and an internet application should both have a
home page.
A home page may contain 1 to 3 columns. Each column has specific types
of contents. Below lists the columns and the specific types of contents they
may have:
1st Column (Side Navigation Bar) - Search within Product only, Navigation
links to deeper within application (do not repeat tab bar links), Browsing
or Catalog list of links.
2nd/Middle Column (on white background) - Welcome text (as needed),
important information, Summary Data regarding application, quick login
area (if applicable)
3rd Column (Place in Content Container) - Ancillary Information (i.e.,
tips for application, "how to" hints for application, product specific
news, marketing/communications type information, Related Links), status
information.
NOTE: Some home pages with very dense information may
have containers with further application information, related links or
status information in the third column. The third column should never
contain critical information, since it may not bee seen as quickly as
the first or middle columns.
Search on Home Page Search gives users the ability to get to the object(s) or section
of the application that is most important to them. The search field
is typically found at the top area of the side navigation within the
home page.
Welcome Text and "Quick" Login
Area on Home Page
Welcome text is typically text that identifies the user and informs
the user of the application being logged in as a "registered user".
When it is used on the home page, the text should appear above all content
and below the navigation elements at the top of the page (tab navigation,
breadcrumbs, etc). "Quick" Login area is used in internet
home pages to allow the user to quickly "login" to the application.
It usually includes user login access intructions and tip information.
Welcome Text - If welcome text is needed, a simple line
of text will suffice (see image at right). This text should
be used only if absolutely necessary, potentially in an infrequently
used application or application used infrequently by third-party
companies.
"Quick" Login
Area - Used in internet applications only, a quick
login area may be used on a home page to allow the user to
quickly login from "guest user" status to "registered user".
Welcome Text
and "Quick" Login Area
A home page may have horizontal (level 2) navigation as needed. Subsections
to a home page are typically seen in outward facing or internet applications
with a heavy marketing/comminucations push. Common subsections may be:
About [Product Name]
Press Releases
News
etc.
"Quick" Tables on a Home Page A "quick" table provides read-only, overview information of objects
in a tabular format within the home page. The number of objects within
"quick" tables should be fairly light. Below are more heuristics
for quick tables:
It is recommnended to not include actions within a quick table.
If actions must exist, then there should be a maximum of 2 to
3 icons within the quick table. These actions are to be represented
as functional icons only. These icons perform a specific action
and then navigates use to an object list.
A quick table should not have a control bar.
The full object list should "live" elsewhere in the
application hierarchy. To navigate to the full object list, use
a "Full List" button.
Home Page containing Quick Tables
Content Containers with Ancillary Information A home page may have content containers with related links, recent
news or other ancillary content. It should be used as needed and is
placed on the rightmost column of the homepage.
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.
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.
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.]
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.
Notifications (at a glance) List - Intranet and Internet Home Pages
A shortened list of notifications can be seen on a home page. Below is a
schematic example.
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.
