Atlassian is standardising the header pattern across its suite of apps. To have consistent experiences with multiple products we're making the common areas of usage look and work the same every time.
Each app will have its own logo and set of specific navigation. The right side of the header is for search, administration tasks, help and the user menu.
Status
API status:
general
Web resource key:
com.atlassian.auiplugin:aui-header
AMD Module key:
N/A
Experimental API:
5
General API:
5.1
Examples
Code
Soy
This example includes the optional Quicksearch pattern:
AخA
{call aui.page.header}
{param logo: 'jira' /}
{param headerLink: '#' /}
{param primaryContent}
<ul class="aui-nav">
<li><a href="https://example.com/">Navigation item or dropdown trigger</a></li>
<li><a href="https://example.com/">Often an icon-only dropdown</a></li>
</ul>
{/param}
{/call}
Options
The logo can be set to a product logo or simple text
Header navigation can be simple links, dropdown2 triggers, a primary button for the hero action
Header contains a quick search pattern
Header navigation items can contain an icon or avatar (aui-avatar-small) and also be dropdowns. If you include these, they must contain the aui-dropdown2-trigger-arrowless so that no right caret is displayed.
Initialisation
The header is initialised automatically. The timing depends on which of these two triggers occurs first:
when the document has loaded, or
asynchronously after the header is inserted into the DOM.
This is to avoid reliance on all DOM content being loaded before the header is navigable.
Rendering a logo
AUI supports adding a logo to the application header pattern. It is assumed that this is the
desired default behaviour, so plain-text is hidden in the basic markup pattern.
To add a logo to the header, there are two common approaches.
To render plain-text in the place of the logo, you can add the aui-header-logo-textonly CSS class
to the aui-header-logo element.
You must include the this class to ensure proper rendering for plain text.