Prepare release
Owner: Build team
<forma-lane-board>
Preserves item-to-lane membership in a bounded board with narrow-screen containment.
<forma-lane-board>patterns/lane-board.htmlA lane board shows items grouped into named lanes, such as workflow stages or owners, laid out as columns. Membership is structural: each lane is a labelled section with a heading, a count and an ordered list of items, so which lane an item is in is announced and survives any width. The board scrolls horizontally inside itself when the lanes do not fit, instead of squeezing them or overflowing the page. Moving items between lanes, drag and drop, and deciding which moves are legal are application behavior; Forma only provides the columns and inherits the shared direct-manipulation hooks for items the application is moving.
minmax(min(18rem, 85vw), 1fr): at least 18rem wide on large screens, 85% of the viewport on phones so the next lane peeks in.The smallest correct markup: the canonical pattern from patterns/lane-board.html inside its public tag. Copy this first, then adapt labels, names and state.
Rendered from the canonical pattern file.
Owner: Build team
State: blocked
<forma-lane-board class="forma-component-tag">
<section class="forma-lane-board" aria-label="Work board">
<section class="forma-lane-board__lane" aria-labelledby="lane-ready">
<header class="forma-lane-board__header"><h2 id="lane-ready">Ready</h2><span>2 items</span></header>
<ol class="forma-lane-board__items"><li><article class="forma-surface"><h3>Prepare release</h3><p>Owner: Build team</p></article></li></ol>
</section>
<section class="forma-lane-board__lane" aria-labelledby="lane-review">
<header class="forma-lane-board__header"><h2 id="lane-review">Review</h2><span>1 item</span></header>
<ol class="forma-lane-board__items"><li><article class="forma-surface"><h3>Verify evidence</h3><p>State: blocked</p></article></li></ol>
</section>
</section>
</forma-lane-board>
Click or tap the code once to select all of it, then copy.
Three stages with counts. The empty Blocked lane keeps its heading and says it is empty, so users can tell "nothing blocked" from "lane missing". The board is focusable because it can scroll.
Owner: Docs
Owner: Platform
Owner: Data
Due tomorrow
Nothing is blocked.
<forma-lane-board class="forma-component-tag">
<section class="forma-lane-board" aria-label="Release 4.2 board" tabindex="0">
<section class="forma-lane-board__lane" aria-labelledby="lane-board-release-board-todo">
<header class="forma-lane-board__header"><h2 id="lane-board-release-board-todo">To do</h2><span>2 items</span></header>
<ol class="forma-lane-board__items">
<li><article class="forma-surface"><h3>Update migration guide</h3><p>Owner: Docs</p></article></li>
<li><article class="forma-surface"><h3>Rotate signing key</h3><p>Owner: Platform</p></article></li>
</ol>
</section>
<section class="forma-lane-board__lane" aria-labelledby="lane-board-release-board-doing">
<header class="forma-lane-board__header"><h2 id="lane-board-release-board-doing">In progress</h2><span>1 item</span></header>
<ol class="forma-lane-board__items">
<li><article class="forma-surface"><h3>Bulk export to Parquet</h3><p>Owner: Data</p><p><span class="forma-status-lozenge" data-state="attention">Due tomorrow</span></p></article></li>
</ol>
</section>
<section class="forma-lane-board__lane" aria-labelledby="lane-board-release-board-blocked">
<header class="forma-lane-board__header"><h2 id="lane-board-release-board-blocked">Blocked</h2><span>0 items</span></header>
<p>Nothing is blocked.</p>
</section>
</section>
</forma-lane-board>
Click or tap the code once to select all of it, then copy.
Each item has a native button that moves it to the next lane, the non-drag path the application must provide. The target lane shows the shared data-forma-drop="candidate" cue (a dashed outline, not only color) and a live message reports the outcome in text. A light motion weight keeps any settle of moved cards quick.
Static specimen. Its buttons stand for application actions that the consuming application implements; this script-free documentation does not perform them. Its controls are shown for their markup and appearance and cannot be operated here.
Backend engineer
Backend engineer
Luis Ferreira moved from Screening to Interview.
<forma-lane-board class="forma-component-tag">
<section class="forma-lane-board" aria-label="Hiring pipeline" tabindex="0" data-forma-motion-weight="light">
<section class="forma-lane-board__lane" aria-labelledby="lane-board-move-without-drag-screen">
<header class="forma-lane-board__header"><h2 id="lane-board-move-without-drag-screen">Screening</h2><span>1 candidate</span></header>
<ol class="forma-lane-board__items">
<li><article class="forma-surface"><h3>Amara Okafor</h3><p>Backend engineer</p><button type="button">Move Amara Okafor to Interview</button></article></li>
</ol>
</section>
<section class="forma-lane-board__lane" aria-labelledby="lane-board-move-without-drag-interview" data-forma-drop="candidate">
<header class="forma-lane-board__header"><h2 id="lane-board-move-without-drag-interview">Interview</h2><span>1 candidate</span></header>
<ol class="forma-lane-board__items">
<li><article class="forma-surface"><h3>Luis Ferreira</h3><p>Backend engineer</p><button type="button">Move Luis Ferreira to Offer</button></article></li>
</ol>
</section>
</section>
<p role="status">Luis Ferreira moved from Screening to Interview.</p>
</forma-lane-board>
Click or tap the code once to select all of it, then copy.
Each mobile example renders in its own document inside a real narrow viewport, so Forma's media and container queries run exactly as they would on a phone. Choose a width to compare.
On a phone each lane takes most of the screen width and the next lane peeks in, showing that the board continues sideways.
min(18rem, 85vw) wide, so at 320px each lane is about 272px and the edge of the next lane is visible as a scroll cue.overscroll-behavior-inline: contain; the page does not scroll sideways.<forma-lane-board class="forma-component-tag">
<section class="forma-lane-board" aria-label="Support board" tabindex="0">
<section class="forma-lane-board__lane" aria-labelledby="lane-board-mobile-new">
<header class="forma-lane-board__header"><h2 id="lane-board-mobile-new">New</h2><span>1 ticket</span></header>
<ol class="forma-lane-board__items"><li><article class="forma-surface"><h3>SUP-2291</h3><p>Invoice PDF missing line items</p></article></li></ol>
</section>
<section class="forma-lane-board__lane" aria-labelledby="lane-board-mobile-waiting">
<header class="forma-lane-board__header"><h2 id="lane-board-mobile-waiting">Waiting on customer</h2><span>1 ticket</span></header>
<ol class="forma-lane-board__items"><li><article class="forma-surface"><h3>SUP-2280</h3><p>Export stuck at 90%</p></article></li></ol>
</section>
<section class="forma-lane-board__lane" aria-labelledby="lane-board-mobile-done">
<header class="forma-lane-board__header"><h2 id="lane-board-mobile-done">Resolved</h2><span>0 tickets</span></header>
<p>No resolved tickets today.</p>
</section>
</section>
</forma-lane-board>
Click or tap the code once to select all of it, then copy.
The canonical pattern in a true 320px viewport, the minimum width every Forma component must support without page-level horizontal scrolling.
Forma components have no JavaScript API. Their public contract is the markup: native elements and attributes you write, and the CSS hooks below. The CSS hook table is generated from the built stylesheet, so it always matches the shipped implementation.
| Attribute | On | Values | Default | Description |
|---|---|---|---|---|
aria-label | root section | string | — | Names the board. |
tabindex | root section | 0 | — | Makes the horizontally scrolling board focusable so keyboard users can scroll it; Forma draws a focus outline for it. |
aria-labelledby | lane section | id of the lane heading | — | Names each lane by its heading, which is what makes lane membership announced. |
data-forma-drop | lane or item | candidate | accepted | rejected | absent | Shared drop presentation written by the application during a move: dashed, solid or dashed-with-fill outline. See Reorder states. |
data-forma-motion-weight | root | light | standard | heavy | standard | Presentation-only mass for settling of items the application is moving inside the board. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-lane-board | Block class | — | Root: a column-flow grid of lanes that scrolls horizontally inside itself. |
.forma-lane-board__header | Element class | — | Lane heading and count on one baseline, spaced apart. |
.forma-lane-board__items | Element class | — | Unstyled list of items with a small gap. |
.forma-lane-board__lane | Element class | — | One lane: a vertical grid of header and items that can shrink. |
[data-forma-motion-weight] | Attribute hook | "heavy", "light", "standard" | Light, standard or heavy mass for the shared direct-manipulation settle of items inside the board (items carrying data-forma-manipulation). The board itself does not animate. Never encodes importance. |
| Keys | Result |
|---|---|
| Tab / Shift+Tab | Moves to the board, then through links and buttons inside items, lane by lane in source order. |
| Arrow keys (board focused) | Scroll the board. Native scrolling of a focused overflow region. |
| Moving items | Not provided. The application must offer buttons or a menu to move items between lanes; drag must never be the only path. |
Not a form control.
| State | How it is expressed | Presentation |
|---|---|---|
| Overflowing | more lanes than fit | The board scrolls horizontally inside itself; lanes keep their minimum width. |
| Board focus | :focus-visible on the board | 2px outline in the current text color. |
| Empty lane | no items in the lane | Application writes a zero count and a sentence in place of the list. |
| Drop target | data-forma-drop on a lane | Candidate is a dashed outline, accepted solid, rejected dashed with a fill. |
| Item moving | data-forma-manipulation on an item | Application-written shared hook: dragging tracks directly, settling returns with damped motion. |
minmax(min(18rem, 85vw), 1fr), so they share extra width on large screens and never shrink below 18rem (or 85vw on phones).max-inline-size: 100% and overflow-x: auto, keeping overflow inside itself.dragging tracks with no transition, settling returns with the damped inertial model and never overshoots.data-forma-motion-weight on the board sets the mass those settles inherit.prefers-reduced-motion: reduce the settle duration becomes effectively instant and items appear at their final position.Forma motion is physics-derived: perceived mass changes how a surface accelerates and settles, never what state it is in. Compare the three presentation weights of the same markup:
Owner: Build team
State: blocked
Owner: Build team
State: blocked
Owner: Build team
State: blocked
Generated fault-injection specimens expose content, spacing, color-cue, and reduced-effective-contrast risks. They screen presentation robustness as engineering screens without claiming human-subject validation.