GitHub

nav.step

One step in a multi-step flow. Pass current on the active step

Component

<Action>

Renders

<a>

Profile

UI
View as Markdown

Navigation intents

Example

Preview
defaultcurrent
<Action intent="nav.step" href="/somewhere" current={isCurrent}>Step</Action>

Choosing between neighbours

Find the row that describes your element, and use the intent on the right.

  • If it is

    Use

  • One step in a multi-step flow. Pass current on the active step

    nav.step this page

  • Pages in site navigation

    nav.page

  • Steps in a multi-step flow

    rather than nav.paging
    nav.step this page

  • Steps in a multi-step flow

    rather than nav.sequel
    nav.step this page

Connections

Declared in the registry, both directions. Where an intent is used in your own code is something check and the gallery see; this site has no app code.

For registry authors

Starter intents. These are the intents prongs add puts in your registry, shown in this site’s theme. Yours are your own registry.ts: rename, restyle and add to them, and see them with prongs add gallery.

What this intent is built from and its entry in components/prongs/registry.ts. You only need this to change how it looks or to add an intent like it.

How nav.step resolves, and its definition

Each layer adds to the one before it; a later class wins over an earlier one that sets the same thing.

  • control.menu

    Plain navigation link; strong while current

    text-sm text-muted-foreground hover:text-foreground
aria-[current]:text-link
  • nav.step

    One step in a multi-step flow. Pass current on the active step

Final classes
text-sm text-muted-foreground hover:text-foreground
aria-[current]:text-link
Element behaviour
{ currentValue: 'step' }
Definition
TS
'nav.step': {
  kind: 'semantic',
  description: 'One step in a multi-step flow. Pass current on the active step',
  refs: ['control.menu'],
  binding: { behavior: { currentValue: 'step' } },
  notFor: [{ context: 'pages in site navigation', instead: 'nav.page' }],
},