Show TOC

BreadcrumbsLocate this document in the navigation structure

Every application page must manage a breadcrumb trail that defines the position of the page within the selected top menu or left-menu item. Breadcrumbs provide a textual representation of the page in the overall set of available functions.

Note Breadcrumbs should be the first text item on each page—error or information messages must appear below the breadcrumb text.
Enclose breadcrumb text in HTML tags:
<h1 class = "[<type>]"> 
<wicket:message key = "[breadcrumbtextkey]" /> 
</h1> 
where <type> is one of:
  • home – for application home pages only.
  • signup – for application sign-up page only.
  • phone – when the page relates to a mobile phone.
  • lock – when the page relates to a security option.
  • house – when the page relates to address information.
  • search – when the page is a search or find operation.
  • attachment – when the page is an attachment operation.
  • bank – when the page relates to a banking operation.
  • friends – when the page relates to a personal or friend operation.
  • coins – when the page relates to a general money operation.
  • wallet – when the page relates to a wallet oriented operation.
  • payments – when the page relates to a payment.
Breadcrumb trails must expand when users follow actions that take them to other pages. To separate elements of a breadcrumb, use a standard separator.
<h1 class = "[type]">    
  <wicket:message key = "[breadcrumb1textkey]" />    
  <wicket:message key = "application.breadcrumb.separator" />    
  <wicket:message key = "[breadcrumb2textkey]" />    
</h1>


Breadcrumbs for Web Applications

Note Breadcrumb text must relate to a short page name, not to an instruction or help text.