layout.actions

Commands side by side: a form’s buttons, a dialog’s choices

Component

<Layout>

Renders

<div>

Profile

View as Markdown

Example

Preview

One

Two

Three

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

Choosing between neighbours

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

If it is
Use
Commands side by side: a form’s buttons, a dialog’s choices
layout.actions this page
Controls that act on the content below them
layout.toolbar
The main calls to action under a page’s pitch headline
layout.pitch.actions
Commands on their own, like a form’s buttons
rather than layout.headline
layout.actions this page
A form’s or dialog’s buttons
rather than layout.pitch.actions
layout.actions this page
Commands
rather than layout.meta
layout.actions this page
Controls on the page itself
rather than layout.overlay
layout.actions 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.row

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.actions 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.row
Children in a wrapping row
```
flex flex-row flex-wrap items-center
```
layout.actions
Commands side by side: a form’s buttons, a dialog’s choices
```
gap-3
```

Final classes

flex flex-row flex-wrap items-center gap-3

Definition

'layout.actions': {
  kind: 'semantic',
  description: 'Commands side by side: a form’s buttons, a dialog’s choices',
  refs: ['arrange.row'],
  binding: { classes: 'gap-3' },
  notFor: [
    {
      context: 'controls that act on the content below them',
      instead: 'layout.toolbar',
    },
    {
      context: 'the main calls to action under a page’s pitch headline',
      instead: 'layout.pitch.actions',
    },
  ],
},