Layout: Recommended Common Application Elements
Login and Logout Pages
A login page is a public page accessible to anyone. As
such, it can have the standard UW look for informational
pages. However, a login page does two additional things:
It provides a login button linked to the Pubcookie
It states which browser levels are supported by the
application (i.e., levels with which the application has
been tested). It is recommended that this statement
"bracket" browser levels, e.g., "works with levels 4-5",
as opposed to stating an open-ended "level 4 and above."
The latter will leave you scrambling to test and fix any
problems that come up with new browser releases.
Beyond that, the page can explain what the application
does, how to obtain access, how to provide a link to a demo or
training site, etc.
A logout page is accessed when a user clicks a logout
button. Functionally, this action destroys any
application-specific authorization and then displays the
standard logout page, which is maintained by the
Pubcookie team. From this page, the user will have
the option to destroy the generic Pubcookie
authentication they obtained by providing their UW
NetId and password.
We're adopting most of the look of the informational WWW
pages (see examples below). Differences include:
The standard toolbar (Search | Directories | Reference
Tools) is replaced by Help | Log Out.
The application's name/logo may appear symmetrically
opposite the "University of Washington" image, preferably
looking distinct (i.e., using a different font and/or
colors). Clicking on the application's name/logo may link
back to the login page.
If appropriate, the application may use breadcrumbs in
the sub-header area, as defined for informational pages. Avoid
using arrows or < signs when not displaying breadcrumbs.
Any non-standard toolbars, tabs, or other navigational
aids should leave some blank space so that they are distinct from
one another. Example.
Application footers do not need a "last updated date,"
but should provide the name of the application's owner
and their contact information.
Symmetrically opposite the seal, an application may
display its own logo or any other logos as appropriate.