@deriv-com/dds-marketing 0.1.0 → 0.2.0

package/.llm/components/grid.md

@@ -0,0 +1,659 @@
+<!-- GENERATED from grid.contract.json. Do not edit. -->
+
+# Grid
+
+A field of equal tracks, and one measure between them. It draws nothing — no ground, no edge, no padding — and owns one decision: how many things sit across, and how narrow a track may get before one of them drops.
+
+It is the third answer to several things that will not fit on a line. A row squashes them, a wrapped row lets them fall where they fall, and this puts them in columns that agree — every cell the same width as the cell above it, every row starting at the same place. That agreement is the whole of what it offers and the only reason to reach for it over a wrapped Row.
+
+It has no breakpoints and takes none. The column count is a ceiling rather than a promise: a track that would be squeezed below its floor is not drawn, and the grid resolves to fewer columns on its own. That matters on a page read at every width there is: a field of feature cards has to go from three across to one without the page naming a single breakpoint, and the floor is what decides where each drop happens.
+
+## Use when
+
+- Several things of the same kind are read across and down, and a cell has to line up with the cell above it — a field of stat cards, a set of tiles, a gallery
+- The count is more than a line holds and the page cannot say what width it will be read at. The floor decides when a column drops, so the page never names a breakpoint
+- The cells must finish level regardless of how much is in each. A grid row is as tall as its tallest cell and hands that height to the rest, which a wrapped line does not
+
+## Do not use
+
+- The things sit on one line and there is no second row to agree with → `Row`
+- The things are read one above the next → `Stack`
+- The set must stay on one line and the reader moves along it → `Scroller`
+- The cells are the fields of one record, repeated down the page → `Table`
+- Page layout with named regions — a hero beside a picture, a header above both. Those regions are different things at different widths and a grid here has no way to say so: every track is the same size as every other, which is what this is and is exactly wrong for a page frame
+- Padding. It sets space between its cells and none at all around them, so a grid reached for to inset a region leaves the surface that should have carried the padding with none
+- One child. A field of one is the child, drawn a second time — the tracks are inert, and what is left is an element that renders, costs a node, and explains nothing
+- Reaching a width. It is as wide as whatever holds it and declares no size of its own. The track floor is a floor and not a width: it says when a column drops, never how wide a cell ends up
+- Cells of different kinds. Every track is the same width, so a grid holding a wide thing and a narrow thing gives both the wide one's measure and the narrow one all that space to sit in. Things that differ belong on a Row, which lets each be what it is
+
+## Anatomy
+
+Grid renders one element.
+
+- `root` — `<div>`, class `dds-grid`. The field, and the whole of what this component is. It paints nothing, holds no corner and takes no padding: an arrangement is not a surface, and one that brought a ground of its own would be a second surface inside whatever it was put in.
+  
+  The track expression is the one thing here a contract cannot hold, and it lives in grid-impl.css for that reason. It is arithmetic — the width n columns would each take at this gap, against the floor a track may not go below — and a token binding states a property and a role rather than a calculation. What the contract does bind is both of its terms: the floor reaches CSS as `--dds-grid-track`, the gap as `--dds-grid-gap` alongside the `gap` property it already sets, so every number in that expression is still a token and the impl file holds only the shape of the sum. It is the first contract in either package to bind a custom property, and that is what the field is for — a value the component needs to compute with rather than to paint.
+  
+  Tracks collapse rather than stand empty. Four cards asked to sit in a field of six are four cards sharing the width, not four cards and two holes, because a grid drawn around a count the content did not reach reads as something missing. That is `auto-fit`, and it is the reason the column count is a ceiling rather than a promise.
+  
+  The top three steps of this package's gap ramp are redefined below 768px, so a field asks for a role and gets a tighter measure on a phone — and because the gap is one of the two terms the track expression is built from, that also moves the width at which a column drops. The responsiveness is inherited twice over and declared nowhere.
+  
+  It declares `min-inline-size: 0`, which is what lets a grid nested inside a flex container shrink below its content rather than pushing that container wider. Without it a field of cards inside a Row would refuse to narrow, the columns would never drop, and the failure would surface as overflow somewhere else entirely.
+  
+  There is no `justify` here, which is the one place this parts company with Stack and Row. Every track is `1fr`, so the tracks take the whole width by construction and there is never spare room along the inline axis to share out. A prop offering to distribute what cannot exist is a prop that draws nothing at every value, and one of those on Stack is already the hardest thing in this family to explain.
+
+Apply these classes from the generated `gridParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: any content
+
+## Props
+
+### gap — `none` | `xs` | `sm` | `md` | `lg` | `xl` | `2xl` | `3xl` (default `lg`)
+
+- `none` — No gap at all, for a field whose cells are meant to read as one object rather than as a set. The only step here that is a decision rather than a measure
+- `xs` — The tightest gap between related elements, for a field read as one texture rather than as separate cells
+- `sm` — The step the token names for sibling controls — a field of small tiles, where the tightness makes the set read as one block
+- `md` — The step the token names for stacked items, taken as a field: cells close enough to be scanned in one pass rather than weighed one at a time
+- `lg` — The default, and what the token names for feature cards in a grid, footer columns and pricing plans. Reach for this unless the cells are smaller or larger than a card
+- `xl` — Between the parts of a card, taken as a field — cells that each hold a picture as well as words. Drops one step below 768px, a phone having a third of the width to spend
+- `2xl` — Between one section of a page and the next, laid out as a field. Drops one step below 768px, a phone having a third of the width to spend
+- `3xl` — The largest gap, for separating whole movements of a page laid out as a field. Drops one step below 768px, a phone having a third of the width to spend
+
+Use when: The measure between cells, in both directions. One value rather than two, because a field whose rows and columns are differently spaced reads as rows first and stops being a grid
+Never for: Reaching a cell width. The gap and the column count together decide how wide a cell lands, but the gap is a relationship between cells and not a way of sizing one. A cell that needs a particular width is a track floor, and past that it is a component with a size
+
+### min — `sm` | `md` | `lg` (default `md`)
+
+- `sm` — The narrow floor, for a cell holding a logo, an icon and a word, or one short claim. Six of these clear the page's measure with its gutter still on both sides
+- `md` — The default floor, for a feature card: a heading and a line or two beneath it. Four fit the page's measure, so a field of three has room to spare
+- `lg` — The wide floor, for a cell holding a picture as well as words, or a pricing plan with a list under it. Three fit the page's measure and four do not
+
+Use when: How narrow a track may get before the field drops a column. This is the whole of the component's responsiveness, and choosing it is choosing where the layout changes
+Never for: Setting a cell's width. It is a floor and never a measure: a cell lands as wide as the region and the column count leave it, which is almost always wider than this. A grid whose floor was picked to make a cell a particular size is a width written where a threshold belongs, and it is the wrong width at every other viewport
+
+### align — `start` | `center` | `end` | `stretch` (default `stretch`)
+
+- `start` — Cells keep their own height and sit against the top of their row, so a short cell beside a tall one ends early rather than being drawn out
+- `center` — Cells keep their own height and sit in the middle of their row
+- `end` — Cells keep their own height and sit against the bottom of their row
+- `stretch` — The default. Every cell takes the full height of its row, so a field of cards finishes level however much is in each — which is the reason most fields are a grid rather than a wrapped line
+
+Use when: How cells of different heights meet within a row. The default is what makes a field of cards look like a field
+Never for: Giving a row a height. Every value here arranges cells within the height the tallest cell in that row establishes; none adds any
+
+### columns — `2` | `3` | `4` | `6` (default `3`)
+
+- `2` — Two across — cells that hold enough to be read rather than scanned, or a field beside a picture
+- `3` — The default, and what most fields of feature cards want. Three is the most a reader takes in as a set rather than as a list
+- `4` — Four across, for cells holding a claim and a line — a field of benefits, a set of tiles
+- `6` — Six across, for marks rather than cards — partner logos, payment methods, regulator badges. A field this wide is read as a texture
+
+Use when: How many cells sit across at full width. A ceiling rather than a promise: fewer are drawn as the region narrows, which is what makes this responsive without a breakpoint
+Never for: Guaranteeing a count. A track squeezed below its floor is not drawn, so a field asked for six may hand back three — which is the behaviour, not a failure. Where exactly n must be on screen at every width, no grid can promise it and a Scroller is the honest answer. It is also why this is not a styling axis: the generated sheet does not vary by it and Figma has no expression to hold it, so the count reaches CSS as an attribute grid-impl.css reads and reaches a designer as a description rather than as a variant
+
+Also accepts everything from `HTMLAttributes<HTMLDivElement>`.
+
+## Choosing a variant
+
+Placement in, props out. When one of these describes what you are building, take
+its props — do not re-derive them from the variant descriptions above.
+
+- **A field of feature cards under a section heading** — `columns="3"` `min="md"`
+  The defaults. Three across at full width, dropping to two and then one as the page narrows, with nothing written about a breakpoint
+- **A row of partner logos** — `columns="6"` `min="sm"` `gap="md"`
+  The most columns this offers and the narrowest floor. Six is where a field stops being read as rows and starts being read as a texture, which is right for marks and wrong for cards
+- **Pricing plans, each with a list of what it includes** — `columns="3"` `min="lg"`
+  The wide floor, so three plans are drawn at the page's measure and drop to two rather than being squeezed to a width the list cannot survive
+- **The columns of a footer** — `columns="4"` `min="sm"` `gap="lg"`
+  What the token names for footer columns, and a narrow floor because each holds a heading and a short list of links
+
+## Accessibility
+
+Guaranteed by the component. Write none of it by hand: the ids these attributes point at are generated per instance, so an attribute set from outside either says the same thing twice or points at nothing.
+
+- the field announces nothing of its own. It is an arrangement, and an arrangement is not something a reader needs told — what is in it carries the meaning, and each cell keeps whatever name or role it would have had anywhere else
+- the order the cells are written in is the order they are read in. Nothing here reorders anything, and nothing here should be made to — a field whose visual order and DOM order disagree is read in one order, seen in another, and tabbed through in a third
+- a field of things of a kind is marked as one somewhere other than here. Tracks are not structure: twelve cards in a grid are announced as twelve unrelated things however neatly they line up, and the markup around them is what says otherwise
+- nothing depends on how many columns are drawn. The count changes with the width of the region and is never reported, so copy reading "the three below" is wrong at the first narrow screen and wrong silently
+
+## Rules
+
+- **On a phone a section's actions stack and each fills the width, including when there is only one** — On a phone a page's actions stack, and each one fills the width. Not most of it, and not the width its label happens to need — the whole column.
+
+Two side by side is what this replaces. On the narrowest screen each gets half a column minus the gap, which is rarely enough for a real label: the words wrap inside the pills, the two buttons come out different heights, and the pair reads as a broken row rather than as a choice. Stacked, each has the whole width and neither has to shorten its words to fit.
+
+A single action fills too, and that is the part worth saying, because it is the one that looks unnecessary. A lone button has the room to sit at its natural width and still should not: a full-width control is the phone's convention for the thing the screen is asking you to do, and a pill hugging its label reads as one option among others that are not there. It also makes the target predictable — the whole width, wherever the thumb lands — which a centred pill does not.
+
+Filling is the row's job rather than the button's. A button has no width of its own and is not given one; the row it sits in becomes a column and stretches its children, so nothing about the control changes and the same button is full width here and its own size on a desktop.
+
+This is the phone's breakpoint, size.breakpoint.md, and not the wider one that decides whether a heading is centred. Those are different questions and they break at different widths: a heading stops being centred when the measure is the screen, while a button stops being full width much sooner than that — stretched across a tablet it is a long way from its own label, and a label centred in a metre of pill is harder to hit than one in a pill the size of the words.
+
+What this is not about is every row of controls. A set of filter chips, a pagination strip, a toolbar, a link sitting after a sentence — none of these is the page asking for something, and stacking them to full width would turn a strip the eye skims into a list it has to read. The test is whether the row is the call to action the section was written for.
+  Guidance only — cannot be checked automatically.
+- **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, Input and Switch simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ Grid for: The things sit on one line and there is no second row to agree with
+   A single line of items has nothing to line up under, so tracks buy nothing and cost a decision. Row is also what a set of different things wants — a grid is for cells of a kind
+   → use `Row` instead.
+
+❌ Grid for: The things are read one above the next
+   A grid of one column is a column, drawn by a component that had to be told twice how many columns to draw
+   → use `Stack` instead.
+
+❌ Grid for: The set must stay on one line and the reader moves along it
+   A rail keeps the order in one direction and hands the reader the overflow. Where the number on screen matters less than the sequence, that is the rail's case rather than this one
+   → use `Scroller` instead.
+
+❌ Grid for: The cells are the fields of one record, repeated down the page
+   Columns that mean something — a name, a date, an amount — are a table's, and a table says which value belongs to which field. This lines cells up and says nothing about what any of them is
+   → use `Table` instead.
+
+## Example
+
+```tsx
+import { Grid, Card, CardBody } from '@deriv-com/dds-marketing'
+
+<Grid columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+```
+
+## In use
+
+### What it is for
+
+Cells of a kind read across and down, each lining up with the one above it. That agreement is the whole of what a grid offers over a wrapped line.
+
+```tsx
+import { Card, CardBody, Grid } from '@deriv-com/dds-marketing'
+
+// A field of feature cards
+<Grid columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+```
+
+### How many across
+
+A ceiling rather than a promise. Each is drawn at the page's measure and drops to fewer as it narrows, with no breakpoint named anywhere.
+
+```tsx
+import { Card, CardBody, Grid } from '@deriv-com/dds-marketing'
+
+// 3 — the default — most fields of cards
+<Grid columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+
+// 2 — cells read rather than scanned
+<Grid columns="2">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+
+// 4 — a claim and a line
+<Grid columns="4">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+
+// 6 — marks rather than cards
+<Grid columns="6">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+```
+
+### When a column drops
+
+The floor is the whole of the component's responsiveness. A wider floor means a column drops sooner — which is the point, since content stops being readable before it stops fitting.
+
+```tsx
+import { Card, CardBody, Grid } from '@deriv-com/dds-marketing'
+
+// md — the default floor — a feature card
+<Grid columns="4" min="md">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+</Grid>
+
+// sm — narrow — a logo or one claim
+<Grid columns="4" min="sm">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+</Grid>
+
+// lg — wide — a picture, or a plan with a list
+<Grid columns="4" min="lg">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+</Grid>
+```
+
+### Every step between cells
+
+The same six cards at each step. The measure decides whether the field reads as one block, a set, or six things that happen to share a band.
+
+```tsx
+import { Card, CardBody, Grid } from '@deriv-com/dds-marketing'
+
+// none — cells that read as one object
+<Grid gap="none" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+
+// xs — a field read as one texture
+<Grid gap="xs" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+
+// sm — small tiles, read as one block
+<Grid gap="sm" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+
+// md — scanned in one pass
+<Grid gap="md" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+
+// lg — the default — feature cards in a grid
+<Grid gap="lg" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+
+// xl — cells with a picture — tightens
+<Grid gap="xl" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+
+// 2xl — one section to the next — tightens
+<Grid gap="2xl" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+
+// 3xl — whole movements — tightens
+<Grid gap="3xl" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client money sits in segregated accounts." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+  <Card>
+    <CardBody title="Support in 12 languages" description="A person, not a script, around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="No minimum deposit" description="Start with whatever you are comfortable with." />
+  </Card>
+  <Card>
+    <CardBody title="Trade on any device" description="One account across web, desktop and mobile." />
+  </Card>
+</Grid>
+```
+
+### How cells of different heights meet
+
+The default hands every cell in a row the height of the tallest, which is why a field of cards is a grid rather than a wrapped line. The others let each cell keep its own.
+
+```tsx
+import { Card, CardBody, Grid } from '@deriv-com/dds-marketing'
+
+// stretch — the default — cells finish level
+<Grid align="stretch" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client funds are held in segregated accounts, separate from the money the business runs on." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+</Grid>
+
+// start — cells keep their height, at the top
+<Grid align="start" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client funds are held in segregated accounts, separate from the money the business runs on." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+</Grid>
+
+// center — cells keep their height, centred
+<Grid align="center" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client funds are held in segregated accounts, separate from the money the business runs on." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+</Grid>
+
+// end — cells keep their height, at the foot
+<Grid align="end" columns="3">
+  <Card>
+    <CardBody title="Regulated globally" description="Licensed in six jurisdictions, with oversight in each." />
+  </Card>
+  <Card>
+    <CardBody title="Funds held separately" description="Client funds are held in segregated accounts, separate from the money the business runs on." />
+  </Card>
+  <Card>
+    <CardBody title="Withdraw any day" description="No lock-in and no waiting period." />
+  </Card>
+</Grid>
+```