How Fabrikam moved 40 sites in a weekend
The team migrated every regional site to the shared design system without changing a single URL, then retired four separate stylesheets.
<forma-split>
Marketing-layer two-part layout: a dominant primary region and a supporting region that wraps below when space runs out.
<forma-split>patterns/split.htmlA split puts a dominant primary region beside a supporting region on site pages: install steps beside requirements, a product explanation beside a code sample, a narrative beside a quote. The first child keeps at least 55% of the row and absorbs extra space; the last child prefers about a third of the row, between 18rem and 30rem. When both cannot fit, the supporting region wraps below the primary one. The switch is content-driven with no breakpoint, and the gap uses the site's fluid section spacing, so place it inside .forma-site.
The smallest correct markup: the canonical pattern from patterns/split.html inside its public tag. Copy this first, then adapt labels, names and state.
Rendered from the canonical pattern file.
The primary region takes the available space. The supporting region wraps below it when the row runs out of room.
<forma-split class="forma-component-tag">
<div class="forma-site">
<div class="forma-split">
<div>
<h2>Install</h2>
<p>The primary region takes the available space. The supporting region wraps below it when the row runs out of room.</p>
</div>
<aside aria-label="Requirements">
<h3>Requirements</h3>
<p>Node 22 or later.</p>
</aside>
</div>
</div>
</forma-split>
Click or tap the code once to select all of it, then copy.
Primary text explains the configuration; the supporting region is a code sample. On a wide page they sit side by side; as the page narrows the code wraps below the explanation.
Each site records the exact Forma release it uses in a lock file. Upgrades are explicit, reviewed and reversible.
forma 0.3.0
destination assets/forma
<forma-split class="forma-component-tag">
<div class="forma-site">
<div class="forma-split">
<div>
<h2>Pin one version per site</h2>
<p>Each site records the exact Forma release it uses in a lock file. Upgrades are explicit, reviewed and reversible.</p>
</div>
<figure class="forma-code-figure">
<figcaption id="split-product-code-sample-caption">forma.lock</figcaption>
<pre class="forma-code" tabindex="0" aria-labelledby="split-product-code-sample-caption"><code>forma 0.3.0
destination assets/forma</code></pre>
</figure>
</div>
</div>
</forma-split>
Click or tap the code once to select all of it, then copy.
A customer story with a facts list as the supporting region. The facts keep a readable width between 18rem and 30rem while the story absorbs the remaining space.
The team migrated every regional site to the shared design system without changing a single URL, then retired four separate stylesheets.
<forma-split class="forma-component-tag">
<div class="forma-site">
<div class="forma-split">
<article aria-labelledby="split-narrative-with-facts-title">
<h2 id="split-narrative-with-facts-title">How Fabrikam moved 40 sites in a weekend</h2>
<p>The team migrated every regional site to the shared design system without changing a single URL, then retired four separate stylesheets.</p>
</article>
<aside aria-labelledby="split-narrative-with-facts-facts">
<h3 id="split-narrative-with-facts-facts">At a glance</h3>
<dl class="forma-facts">
<div class="forma-facts__item"><dt>40 sites</dt><dd>Migrated in two days</dd></div>
<div class="forma-facts__item"><dt>4 stylesheets</dt><dd>Retired after launch</dd></div>
</dl>
</aside>
</div>
</div>
</forma-split>
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.
The install layout at phone width. The primary region needs 55% of the row and the aside at least 18rem, so they cannot share a line and the aside wraps below.
min(100%, 55%), so it never overflows a 320px screen.<forma-split class="forma-component-tag">
<div class="forma-site">
<div class="forma-split">
<div>
<h2>Install</h2>
<p>Run the installer once per site. It verifies every download against the release checksums.</p>
</div>
<aside aria-labelledby="split-mobile-wrapped-requirements">
<h3 id="split-mobile-wrapped-requirements">Requirements</h3>
<p>Bash 4 or later and a network connection to the release host.</p>
</aside>
</div>
</div>
</forma-split>
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-labelledby | article / aside | id of the region heading | — | Names each region by its heading. |
tabindex | pre.forma-code | 0 | — | Makes a scrollable code block keyboard-scrollable in the code sample example. |
| Hook | Kind | Values or default | Description |
|---|---|---|---|
.forma-split | Block class | — | Wrapping flex row. First child: flex: 999 1 0 with minimum min(100%, 55%). Last child: basis clamp(18rem, 32%, 30rem). Gap is half the fluid section space. |
| Keys | Result |
|---|---|
| Tab / Shift+Tab | Moves through the primary region and then the supporting region, in source order. |
Not a form control.
| State | How it is expressed | Presentation |
|---|---|---|
| Side by side | row fits 55% plus the aside basis and gap | Primary region grows; supporting region stays between 18rem and 30rem. |
| Wrapped | row too narrow | Supporting region moves below the primary region at full width. |
--forma-layout-section-space, a fluid token, so spacing scales with the viewport..forma-site: its gap and the surrounding typography and tone come from the marketing role tokens.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.