@deriv-com/dds-marketing 0.1.0 → 0.2.0

package/.llm/components/tablebody.md

@@ -0,0 +1,258 @@
+<!-- GENERATED from table-body.contract.json. Do not edit. -->
+
+# TableBody
+
+The rows of data, under the header. It is where the table's rules reach the rows: a line belongs between two data rows and nowhere else, so the section that holds only data is the one that hands them out.
+
+## Use when
+
+- The data itself — every row that a reader compares against the others
+
+## Do not use
+
+- The row names the columns rather than filling them → `TableHead`
+- An empty state. A table with nothing in it is not a table with an empty row — a row spanning every column to say "no results" is a sentence pretending to be data. Render the message instead of the table
+- Rows of differing shapes. Every row here answers the same questions in the same order, which is the promise the whole component exists to make
+
+## Anatomy
+
+TableBody renders one element.
+
+- `root` — `<tbody>`, class `dds-tablebody`. The data section, and where the rules live. It takes the table's size and its dividers, and hands both to every row it holds, which is the second step of a cascade that starts at the table and ends at a cell.
+  
+  It paints nothing. The surface belongs to the table, which holds the corner it has to be clipped by — a fill here would square that corner off at the bottom of the last row.
+
+Apply these classes from the generated `tableBodyParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `TableRow`
+- Never contains: `Table`, `TableHead`, `TableBody`, `TableHeaderCell` — in children or in any prop that takes a node
+- Holds at least 1
+
+## Props
+
+### size — `sm` | `md` | `lg` (default `md`)
+
+- `sm` — Compact. Dense data a reader scans rather than reads — a ledger, a positions table, anything where fitting more rows on screen is worth more than air around each one
+- `md` — Balanced, and the default: rows a reader moves through at reading pace, with enough room that the eye does not slip between them
+- `lg` — Spacious. Few rows, each carrying something substantial — a plan comparison, a summary of three accounts. Reach for it when the table is the page rather than a part of it
+Never for: Making the text bigger or smaller. It changes how tall a row is and nothing else — the type stays one size down the whole table, because a reader comparing values across three tables at three densities is comparing the values rather than the tables. A table too wide for its column scrolls, and a smaller size only makes the same problem harder to read
+
+### dividers — `rows` | `grid` | `none` (default `rows`)
+
+- `rows` — The default. A line between rows and none between columns, which is what stops the eye slipping from one row's start to another's end — the mistake a wide table invites and the one a reader never notices making
+- `grid` — Lines both ways, for a table read as a matrix rather than as a list of records: a rate card, a comparison where the reader traces a column as often as a row. It is more lines than most tables need, so it should be asked for
+- `none` — No lines at all. Right for two or three rows, where the rules are more structure than data, and for a table whose columns are already separated by their alignment
+Never for: Marking a group. A missing line is not a heading — a table that wants sections wants a header row inside the body, or two tables. Nor `grid` as decoration on a long table: every vertical line is another thing between a reader and the value they came for
+
+### hoverable — `boolean` (default `true`)
+
+Use when: Handed down by the table. It draws a wash under the pointer so a reader knows which row a press would land on — and only on a device that has a pointer, which the row's own stylesheet gates
+Never for: Saying a row is chosen. Hover is where the pointer is and nothing more; `selected` is the answer a reader gave, and a row that looked picked on approach would say they had picked everything they passed over
+
+### overflow — `wrap` | `truncate` (default `wrap`)
+
+- `wrap` — The default. Text too long for its column wraps and the row grows taller, so nothing is hidden — right whenever the value is the point and a reader has to read all of it
+- `truncate` — Rows must stay one line high — a dense table a reader scans down, where a row that grew would break the rhythm they are scanning by. The value is clipped with an ellipsis and the whole of it is still reachable, so this trades seeing for scanning rather than losing anything
+Never for: Making a column narrow enough to be worth truncating. Clipping is what a column does when it has run out of room, not a way to give it less — a table of ellipses has hidden its data behind a hover on every cell
+
+Also accepts everything from `HTMLAttributes<HTMLTableSectionElement>`.
+
+## 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
+
+❌ TableBody for: The row names the columns rather than filling them
+   A header is announced before every value in its column, which is what makes the data readable a cell at a time. A name placed here is read as data and the columns go unnamed
+   → use `TableHead` instead.
+
+## Example
+
+```tsx
+import { TableBody, TableRow, TableCell } from '@deriv-com/dds-marketing'
+
+<TableBody>
+  <TableRow>
+    <TableCell>Alice Johnson</TableCell>
+    <TableCell>alice@example.com</TableCell>
+    <TableCell>Engineer</TableCell>
+  </TableRow>
+  <TableRow>
+    <TableCell>Bob Smith</TableCell>
+    <TableCell>bob@example.com</TableCell>
+    <TableCell>Designer</TableCell>
+  </TableRow>
+  <TableRow>
+    <TableCell>Charlie Brown</TableCell>
+    <TableCell>charlie@example.com</TableCell>
+    <TableCell>PM</TableCell>
+  </TableRow>
+</TableBody>
+```
+
+## In use
+
+Most rows below hold the same set, written once here:
+
+```tsx
+import { TableCell, TableRow } from '@deriv-com/dds-marketing'
+
+const tablerows = (
+  <>
+    <TableRow>
+  <TableCell>Alice Johnson</TableCell>
+  <TableCell>alice@example.com</TableCell>
+  <TableCell>Engineer</TableCell>
+</TableRow>
+    <TableRow>
+  <TableCell>Bob Smith</TableCell>
+  <TableCell>bob@example.com</TableCell>
+  <TableCell>Designer</TableCell>
+</TableRow>
+    <TableRow>
+  <TableCell>Charlie Brown</TableCell>
+  <TableCell>charlie@example.com</TableCell>
+  <TableCell>PM</TableCell>
+</TableRow>
+  </>
+)
+```
+
+### What it holds
+
+The data itself — every row a reader compares against the others.
+
+```tsx
+import { TableBody } from '@deriv-com/dds-marketing'
+
+// Three columns
+<TableBody>{tablerows}</TableBody>
+```
+
+### Row density
+
+Taken from the table and handed to every row, so a table's air is one decision made once rather than a measure repeated per cell.
+
+```tsx
+import { TableBody } from '@deriv-com/dds-marketing'
+
+// sm
+<TableBody size="sm">{tablerows}</TableBody>
+
+// md
+<TableBody size="md">{tablerows}</TableBody>
+
+// lg
+<TableBody size="lg">{tablerows}</TableBody>
+```
+
+### When a value is too long
+
+Handed down so every cell in the section agrees. Wrapping grows the row; truncating keeps it one line high.
+
+```tsx
+import { TableBody } from '@deriv-com/dds-marketing'
+
+// wrap
+<TableBody overflow="wrap">{tablerows}</TableBody>
+
+// truncate
+<TableBody overflow="truncate">{tablerows}</TableBody>
+```
+
+### Dividers
+
+A line belongs between two data rows, so the section holding only data is the one that hands the rules out.
+
+```tsx
+import { TableBody } from '@deriv-com/dds-marketing'
+
+// rows
+<TableBody dividers="rows">{tablerows}</TableBody>
+
+// grid
+<TableBody dividers="grid">{tablerows}</TableBody>
+
+// none
+<TableBody dividers="none">{tablerows}</TableBody>
+```
+
+### Hover
+
+Handed to every row, so a table's rows agree about whether they light up under the pointer.
+
+```tsx
+import { TableBody } from '@deriv-com/dds-marketing'
+
+// hoverable
+<TableBody hoverable>{tablerows}</TableBody>
+
+// Read-only
+<TableBody hoverable={false}>{tablerows}</TableBody>
+```

package/.llm/components/tablecell.md

@@ -0,0 +1,248 @@
+<!-- GENERATED from table-cell.contract.json. Do not edit. -->
+
+# TableCell
+
+One value in a row, under the column that names it. It is a slot: what goes in is the page's to compose, which is what lets a cell hold a badge, a link or a control rather than only text. What it decides is where the value sits in the column and whether its digits line up with the ones above and below.
+
+## Use when
+
+- A value in a data row — a name, an amount, a date, a state
+- A cell holding a component rather than words: a Badge against a name, a Link at the end of the row
+- Numbers a reader compares down the column, where `numeric` ranges them to the end and sets the digits in tabular figures
+
+## Do not use
+
+- The cell names the column rather than filling it → `TableHeaderCell`
+- A cell that spans the row to hold a message. It is announced against a header that does not describe it, and it breaks the shape every other row keeps
+- Nesting a table. A grid inside a cell is a second set of rows and columns announced inside the first, and no reader can hold both
+- Text long enough to be a paragraph. A cell is compared against the ones above it, and a column of paragraphs is a column nobody reads down
+
+## Anatomy
+
+TableCell renders one element.
+
+- `root` — `<td>`, class `dds-tablecell`. The cell. Its padding is the table's size made concrete — the air around a value is the whole of what a density changes, so it is set here rather than on the row, which draws only its rule.
+  
+  The type does not move with it. A size that also changed the font would make three tables at three densities three different readings of the same data, and a reader comparing across them would be comparing the tables. One size of type down the whole component, and the density is height alone.
+  
+  It aligns to the top of the row rather than the middle. Rows are as tall as their tallest cell, and a cell of one line centred beside a cell of three floats in the middle of a row with nothing across from it; ranged to the top, every value in a row starts on the same line.
+  
+  `numeric` is what sets tabular figures, and the rule about it is the system's rather than this component's: Inter's default figures are proportional, so a column of amounts drawn with them has its decimal points at slightly different places and stops being a column a reader can compare down.
+  
+  It draws the rule above itself. A `<tr>` border is painted only while a table collapses its borders, and this table separates them so it can hold a corner — so the line between two rows is a run of cell edges rather than one row edge, and `border-spacing: 0` on the table is what keeps them touching.
+  
+  `overflow` decides what a value too long for its column does. Wrapping grows the row and hides nothing, which is right whenever the value is the point. Truncating keeps every row one line high, which is what a reader scanning a dense table is actually using — and the whole value stays reachable, so it trades seeing for scanning rather than losing anything.
+  
+  Type follows the size axis rather than holding at one role. It did not: every cell set font.body.md whatever size the table was, so `sm` tightened the padding around text that had not moved and a dense table came out dense in one direction only — twelve pixels of inset around sixteen pixels of copy, which is a proportion no step of the scale asks for. A reference table is the case that needs it: many columns, read across, and the width to hold them only exists at a size the body scale actually has.
+
+Apply these classes from the generated `tableCellParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: any content
+- Never contains: `Table`, `TableHead`, `TableBody`, `TableRow`, `TableCell`, `TableHeaderCell` — in children or in any prop that takes a node
+
+## Props
+
+### size — `sm` | `md` | `lg` (default `md`)
+
+- `sm` — Compact. Dense data a reader scans rather than reads — a ledger, a positions table, anything where fitting more rows on screen is worth more than air around each one
+- `md` — Balanced, and the default: rows a reader moves through at reading pace, with enough room that the eye does not slip between them
+- `lg` — Spacious. Few rows, each carrying something substantial — a plan comparison, a summary of three accounts. Reach for it when the table is the page rather than a part of it
+Never for: Making the text bigger or smaller. It changes how tall a row is and nothing else — the type stays one size down the whole table, because a reader comparing values across three tables at three densities is comparing the values rather than the tables. A table too wide for its column scrolls, and a smaller size only makes the same problem harder to read
+
+### align — `start` | `center` | `end` (default `start`)
+
+- `start` — Words. Names, descriptions, statuses — anything read left to right starts where the reading does, and a column of them shares one edge the eye can run down
+- `center` — Rare, and worth arguing for: a single glyph or a very short state where neither edge means anything. A centred column of words has two ragged edges instead of one
+- `end` — Numbers that line up under each other — amounts, counts, percentages. The decimal point is what a reader compares down a column, and ranging to the end is what puts it in one place
+Never for: Making a table look balanced. Alignment says what kind of thing a column holds; using it to even out a layout tells the reader the numbers are words
+
+### numeric — `boolean` (default `false`)
+
+Use when: The cell holds digits a reader compares against the cells above and below — an amount, a count, a percentage. It sets tabular figures, so every digit takes the same width and the decimal points line up down the column. Ranging the column to the end is `align`'s job and a separate decision — the two travel together on almost every numeric column, and keeping them apart is what lets a centred count exist
+Never for: Any number at all. The system's own rule is not "is this a number" but "does it line up under another one" — a reference code or a year written once beside a name is read rather than compared, and tabular figures cost it the better fit of proportional ones for nothing
+
+### dividers — `rows` | `grid` | `none` (default `rows`)
+
+- `rows` — The default. A line between rows and none between columns, which is what stops the eye slipping from one row's start to another's end — the mistake a wide table invites and the one a reader never notices making
+- `grid` — Lines both ways, for a table read as a matrix rather than as a list of records: a rate card, a comparison where the reader traces a column as often as a row. It is more lines than most tables need, so it should be asked for
+- `none` — No lines at all. Right for two or three rows, where the rules are more structure than data, and for a table whose columns are already separated by their alignment
+Never for: Marking a group. A missing line is not a heading — a table that wants sections wants a header row inside the body, or two tables. Nor `grid` as decoration on a long table: every vertical line is another thing between a reader and the value they came for
+
+### overflow — `wrap` | `truncate` (default `wrap`)
+
+- `wrap` — The default. Text too long for its column wraps and the row grows taller, so nothing is hidden — right whenever the value is the point and a reader has to read all of it
+- `truncate` — Rows must stay one line high — a dense table a reader scans down, where a row that grew would break the rhythm they are scanning by. The value is clipped with an ellipsis and the whole of it is still reachable, so this trades seeing for scanning rather than losing anything
+Never for: Making a column narrow enough to be worth truncating. Clipping is what a column does when it has run out of room, not a way to give it less — a table of ellipses has hidden its data behind a hover on every cell
+
+Also accepts everything from `TdHTMLAttributes<HTMLTableCellElement>`.
+
+## 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.
+
+- Announced as: `cell`
+- the value is text a reader can hear, not a colour or a glyph alone. A status drawn as a dot with no words beside it is a cell that says nothing to a screen reader and nothing to anyone who cannot tell the colours apart
+
+## 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
+
+❌ TableCell for: The cell names the column rather than filling it
+   A header is announced before every value beneath it, and a styled data cell is not — so a header written as a cell leaves the column unnamed for anyone reading it a cell at a time
+   → use `TableHeaderCell` instead.
+
+## Example
+
+```tsx
+import { TableCell } from '@deriv-com/dds-marketing'
+
+<TableCell>Alice Johnson</TableCell>
+```
+
+## In use
+
+### Where the value sits
+
+Alignment says what kind of thing a column holds. Words start where the reading does; numbers range to the end, where a reader compares the decimal points.
+
+```tsx
+import { TableCell } from '@deriv-com/dds-marketing'
+
+// start — words
+<TableCell align="start">Alice Johnson</TableCell>
+
+// center — a short state, rarely
+<TableCell align="center">Active</TableCell>
+
+// end — numbers
+<TableCell align="end" numeric>1,204.50</TableCell>
+```
+
+### Digits that line up
+
+Inter's default figures are proportional, so a column of amounts has its decimal points in slightly different places and stops being comparable down.
+
+```tsx
+import { TableCell } from '@deriv-com/dds-marketing'
+
+// numeric — tabular figures
+<TableCell numeric align="end">1,204.50</TableCell>
+
+// Read once, not compared
+<TableCell numeric={false}>Reference 4471</TableCell>
+```
+
+### Row density
+
+The padding and the type together: the air around a value and the size it is set at are what a density actually changes.
+
+```tsx
+import { TableCell } from '@deriv-com/dds-marketing'
+
+// sm
+<TableCell size="sm">Alice Johnson</TableCell>
+
+// md
+<TableCell size="md">Alice Johnson</TableCell>
+
+// lg
+<TableCell size="lg">Alice Johnson</TableCell>
+```
+
+### When a value is too long
+
+Wrapping grows the row and hides nothing. Truncating clips with an ellipsis and keeps every row one line high.
+
+```tsx
+import { TableCell } from '@deriv-com/dds-marketing'
+
+// wrap
+<TableCell overflow="wrap">Charlotte Featherstonehaugh-Willoughby</TableCell>
+
+// truncate
+<TableCell overflow="truncate">Charlotte Featherstonehaugh-Willoughby</TableCell>
+```
+
+### Dividers
+
+The cell draws the line above itself, and the one beside it where the table is read as a matrix.
+
+```tsx
+import { TableCell } from '@deriv-com/dds-marketing'
+
+// rows
+<TableCell dividers="rows">Alice Johnson</TableCell>
+
+// grid
+<TableCell dividers="grid">Alice Johnson</TableCell>
+
+// none
+<TableCell dividers="none">Alice Johnson</TableCell>
+```