@aurodesignsystem-dev/auro-nav
v0.0.0-pr100.1
Published
auro-nav HTML custom element
Downloads
863
Readme
Nav
<auro-nav> is a HTML custom element for the purpose of showing users a secondary navigation aid that helps them understand the relation between the location of their current page and higher level pages.
Use Cases
The <auro-nav> element acts as a container for a series of links representing a level of depth in the site content.
The <auro-nav> element should only be used for multi-page projects that have 3 to 5 levels of page depth.
Install
$ npm i @aurodesignsystem/auro-navDefine Dependency in Project
Defining the dependency within each project that is using the <auro-nav> component.
import "@aurodesignsystem/auro-nav";Use CDN
In cases where the project is not able to process JS assets, there are pre-processed assets available for use. Legacy browsers such as IE11 are no longer supported.
<script type="module" src="https://cdn.jsdelivr.net/npm/@aurodesignsystem/auro-nav@latest/+esm"></script>Basic Example
<auro-nav>
<auro-breadcrumb href="http://auro.alaskaair.com/components/auro/nav">Home</auro-breadcrumb>
<auro-breadcrumb href="http://auro.alaskaair.com/components/auro/nav">Level 2</auro-breadcrumb>
<auro-breadcrumb href="http://auro.alaskaair.com/components/auro/nav">Level 3</auro-breadcrumb>
<auro-breadcrumb href="http://auro.alaskaair.com/components/auro/nav">Level 4</auro-breadcrumb>
<auro-breadcrumb>Current</auro-breadcrumb>
</auro-nav>Custom Component Registration for Version Management
There are two key parts to every Auro component: the class and the custom element definition. The class defines the component’s behavior, while the custom element registers it under a specific name so it can be used in HTML.
When you install the component as described on the Install page, the class is imported automatically, and the component is registered globally for you.
However, if you need to load multiple versions of the same component on a single page (for example, when two projects depend on different versions), you can manually register the class under a custom element name to avoid conflicts.
You can do this by importing only the component class and using the register(name) method with a unique name:
<custom-nav>
<custom-breadcrumb href="http://auro.alaskaair.com/components/auro/nav">Home</custom-breadcrumb>
<custom-breadcrumb href="http://auro.alaskaair.com/components/auro/nav">Level 2</custom-breadcrumb>
<custom-breadcrumb href="http://auro.alaskaair.com/components/auro/nav">Level 3</custom-breadcrumb>
<custom-breadcrumb href="http://auro.alaskaair.com/components/auro/nav">Level 4</custom-breadcrumb>
<custom-breadcrumb>Current</custom-breadcrumb>
</custom-nav>