layout.subnav

A page with its own section nav beside its content: settings, account, a project’s admin. Put the nav first (a nav of nav.page links), then the content. On phones the nav sits above it

Component

<Layout>

Renders

<div>

Profile

View as Markdown

Example

Preview

One

Two

Three

<Layout intent="layout.subnav">
  …
</Layout>

Choosing between neighbours

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

If it is
Use
A page with its own section nav beside its content: settings, account, a project’s admin. Put the nav first (a nav of nav.page links), then the content. On phones the nav sits above it
layout.subnav this page
The frame of the whole app, around every signed-in page
layout.shell
One page with its own section nav, like settings
rather than layout.shell
layout.subnav 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.

Built from
arrange.stack

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 layout.subnav 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.

arrange.stack
Children in a column, free to shrink inside a row or grid
```
flex min-w-0 flex-col
```
layout.subnav
A page with its own section nav beside its content: settings, account, a project’s admin. Put the nav first (a nav of nav.page links), then the content. On phones the nav sits above it
```
gap-8 md:grid md:grid-cols-[12rem_minmax(0,1fr)] md:items-start
```

Final classes

flex min-w-0 flex-col gap-8 md:grid
md:grid-cols-[12rem_minmax(0,1fr)] md:items-start

Definition

'layout.subnav': {
  kind: 'semantic',
  description: 'A page with its own section nav beside its content: settings, account, a project’s admin. Put the nav first (a nav of nav.page links), then the content. On phones the nav sits above it',
  refs: ['arrange.stack'],
  binding: {
    classes: 'gap-8 md:grid md:grid-cols-[12rem_minmax(0,1fr)] md:items-start',
  },
  notFor: [
    {
      context: 'the frame of the whole app, around every signed-in page',
      instead: 'layout.shell',
    },
  ],
},