@deriv-com/dds-marketing 0.1.0 → 1.0.0

package/.llm/components/scroller.md

@@ -0,0 +1,478 @@
+<!-- GENERATED from scroller.contract.json. Do not edit. -->
+
+# Scroller
+
+A rail, and one measure between the things on it. It draws nothing — no ground, no edge, no padding — and owns one decision: that a set too long for the space stays on one line and the reader moves along it.
+
+It is the third answer to a line that has run out of room, and the only one that keeps the order intact. A Row squashes its items or lets them fall onto a second line where nothing aligns; a Grid puts them in tracks and gives up the sequence; this keeps them where they were put and hands the reader the overflow. Where the order is the content — a timeline, a set of steps, a run of testimonials, a rail of logos — that is the difference between a component that shows the set and one that rearranges it.
+
+On a page it earns its keep on a phone most of all. A field of three cards becomes a column of three on a narrow screen, and a column is a scroll the reader has to make past content they did not ask to read; a rail keeps the set one thing tall and hands them the choice of going further.
+
+What it mostly exists to get right is the part nobody sees. A scrolling region with no focusable child inside it cannot be reached by a keyboard at all: the rail looks perfect, the mouse works, and a reader on a keyboard is simply never shown the half that is off screen. Nothing reports it and no visual review catches it. The rail carries its own tab stop and its own name for exactly that reason, which is also why the name is not optional.
+
+## Use when
+
+- A set is longer than the space and its order is worth keeping — steps in a sequence, results already ranked, a timeline, a run of chips a reader is scanning rather than comparing
+- The things are of a kind and of a size, so a line of them reads as a line rather than as a row of unrelated objects that happen to be beside one another
+- Seeing part of the next item is what tells the reader there is more. A rail cut off mid-item is the affordance, and it is the one thing a wrapped line and a grid cannot offer
+
+## Do not use
+
+- Everything fits, or should be made to fit → `Row`
+- The set may break onto a second line and nothing is lost by it → `Row`
+- The items should line up in columns as well → `Grid`
+- The region scrolls down rather than across → nothing here does this
+- Hiding a set that should be seen. Anything past the first screenful is found only by a reader who knows to look, so a rail holding the one thing a page exists to say has hidden it behind a gesture. What is off the edge is optional by construction
+- Navigation a reader must be able to survey. A set of destinations that does not fit is a set that needs a menu, a panel or fewer destinations — a rail makes the reader move to find out what their options are, and they cannot count what they cannot see
+- Padding. It sets space between its items and none at all around them, and a rail reached for to inset a region leaves the surface that should have carried the padding with none
+- One child. A rail of one never scrolls: what is left is a focusable, named, grouped region announcing itself around a single item the reader could already see
+- A table that is too wide. Cells that must line up with the cells above them are a table's columns, and a table scrolls itself — wrapping one in a rail takes the header out of the region that scrolls, so the columns and their names come apart
+
+## Anatomy
+
+Scroller renders one element.
+
+- `root` — `<div>`, class `dds-scroller`. The rail, 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.
+  
+  It is focusable, which no other primitive in this family is. A scroll container whose children are all inert — cards that are not links, chips that are not buttons, images — is unreachable by keyboard, and the browser gives it no tab stop of its own. So this takes one, carries `role="group"` and takes a name, which is why `label` is the one required prop here. Focused, it scrolls with the arrow keys, Home and End, which is behaviour the browser already provides and this component only has to make reachable. The cost is one extra stop in the tab order where the items are themselves focusable, and that is the right trade: an unnecessary stop is an inconvenience a reader can pass in one keypress, and an unreachable region is content they never learn exists.
+  
+  Its items do not shrink. That rule lives in scroller-impl.css as a `> *` because the children are whatever the page passed and there is no part here to put a class on — the same positional fact AspectRatio states about its one child. It is also the difference between a rail and a squashed Row: a flex item shrinks to fit before it overflows, so without it the set does exactly what the rail was reached for to avoid, and does it silently.
+  
+  It scrolls on the inline axis only, and the block axis is deliberately left alone. Nothing here overflows downward on purpose, and a rail that clipped vertically would cut the focus ring off whatever item is focused inside it — a focus indicator drawn outside an element's box being the usual casualty of a container that hides one axis.
+  
+  The top three steps of this package's gap ramp are redefined below 768px, so a rail asks for a role and gets a tighter measure on a phone — which is also where it does most of its work, and where the measure decides how much of the next item shows at the edge.
+  
+  The scrollbar is not hidden. It is the only standing sign that a region moves, and a rail that hides it is relying entirely on an item being cut off at the edge — which is true until the set happens to end near the boundary, at which point the rail looks complete and is not. Overscroll is contained, so reaching the end of the rail does not hand the gesture to the page behind it or to the browser's back navigation, which is the failure a horizontal rail causes most often and the one a reader is least able to explain.
+
+Apply these classes from the generated `scrollerParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: any content
+- Never contains: `Table`, `Scroller` — in children or in any prop that takes a node
+
+## Props
+
+### gap — `none` | `xs` | `sm` | `md` | `lg` | `xl` | `2xl` | `3xl` (default `lg`)
+
+- `none` — No gap at all, for a rail whose marks 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 rail read as one strip rather than as separate items
+- `sm` — The step the token names for sibling controls — a rail of chips, filters or small marks
+- `md` — The step the token names for stacked items, taken across: items that are peers but not controls, where the control step would run them together
+- `lg` — The default, and what the token names for feature cards, footer columns and pricing plans — the rail of cards this is most often reached for
+- `xl` — Between the parts of a card, taken along a rail — items 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 along a rail. 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 along a rail. Drops one step below 768px, a phone having a third of the width to spend
+
+Use when: The measure between items along the rail, and the one place it differs from the same measure elsewhere: a gap ends at the last item, where margins on the items would run on past it and turn the end of the rail into scrollable emptiness the reader is dragged into
+Never for: Reaching a distance. The gap is a relationship between two items rather than a measure from anything, and one picked to make a particular item land at the edge is a position written in the wrong units — it lands elsewhere at every other width
+
+### align — `start` | `center` | `end` | `stretch` (default `stretch`)
+
+- `start` — Items keep their own height and sit against the top of the rail, so a short item ends early rather than being drawn out to match its neighbours
+- `center` — Items keep their own height and sit in the middle of the rail
+- `end` — Items keep their own height and sit against the bottom of the rail
+- `stretch` — The default. Every item takes the full height of the rail, so a run of cards finishes level however much is in each
+
+Use when: How items of different heights meet across the rail. The default is what keeps a run of cards reading as a run
+Never for: Giving the rail a height. Every value here arranges items within the height the tallest of them establishes; none of them adds any
+
+### snap — `boolean` (default `false`)
+
+Use when: Each stop lands an item against the leading edge rather than wherever the gesture ended. For a rail of items of one size that the reader steps through — cards, slides, a set of positions
+Never for: A rail being scanned rather than stepped through. Snapping takes the scroll away from the reader at every item, which is help when each item is a destination and a fight when they are looking for one of them. It is also wrong for items of different widths, where the stops are unevenly spaced and the rail feels broken rather than assisted
+
+### label — `string` **Required.**
+
+Use when: Always. The rail is a focusable region, so it is announced when a reader arrives at it — and without a name it announces "group" and nothing else, telling them something is there but not what. Name the set rather than the component: "Markets", "Recent trades", not "Carousel"
+Never for: Repeating a heading the reader has just met. Where a visible heading already names the set, this says the same thing twice in a row — the announcement is the heading, then the group with the same words. Name what distinguishes this rail from the others on the view
+
+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 rail of feature cards on a phone, where a grid would become a long column** — `gap="lg"` `snap`
+  Cards of a size are what snapping is for: each stop lands a card against the leading edge rather than halfway through one, and the set stays one card tall however many there are
+- **A row of partner logos wider than the page's measure** — `gap="xl"`
+  Marks rather than cards, so the air between them is what keeps them from reading as one strip. No snapping — nothing here is a destination
+- **Testimonials, read one at a time** — `gap="lg"` `snap` `align="start"`
+  Each quote is a position, so the rail should stop at one. Items keep their own height because a short quote stretched to match a long one has a band of empty card under it
+- **The categories of an index, wider than the region holding them** — `gap="sm"`
+  The step the token names for sibling controls. The reader is scanning for one rather than stepping through them all, which is the case snapping is wrong for
+
+## 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: `group`
+- `Tab` — Moves onto the rail itself, which takes a stop of its own because a region that scrolls and holds nothing focusable is otherwise unreachable. Where the items are focusable too, this is one stop before them rather than instead of them
+- `ArrowRight` — Scrolls the rail toward the trailing edge while it holds focus. The browser's own behaviour for a focused scroll container, which is the point of giving it a tab stop rather than building a keyboard model of its own
+- `ArrowLeft` — The same step the other way
+- `Home` — Back to the start of the rail
+- `End` — To the end of the rail
+- the rail has an accessible name, which is what `label` is for. It is announced as a group the moment a reader tabs onto it, and a group with no name tells them only that something is there
+- the rail is reachable by keyboard whether or not anything inside it is. A scroll container with no focusable child gets no tab stop from the browser, and the content past the edge is then unreachable by any means but a pointer
+- the order the items are written in is the order they are read in, and the order they are scrolled through. Nothing here reorders anything, and a rail whose visual order and DOM order disagree is scrolled in one order and tabbed in another
+- nothing the reader must act on sits past the edge. What is off screen is found only by someone who knows to look for it, so a rail is for sets where the first few are enough and the rest are more of the same
+- a rail of things of a kind is marked as one somewhere other than here. The group role says a region exists and names it; it does not say the items in it are a list or how many there are
+
+## 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.
+- **A component is written along the reading axis, not along the page's left and right** — Every measure, inset and placement in this package names an axis rather than a side: inline-size and block-size, padding-inline and padding-block, inset-inline-start and inset-block-end, margin-inline: auto, text-align: start. Written that way a component follows whichever direction the page is read in, and a band whose claim ranges to the leading edge with its subject on the trailing one is the same composition in Arabic as in English, mirrored, with nothing restated. Written as left and right it is the same pixels in both, which is a layout nobody designed for the second language.
+
+The enum values follow the same rule and for the same reason. A prop that names where a picture sits takes start and end, never left and right — FeatureSplit, FeatureBullets and FeatureScroll all declare mediaPosition that way, and the flex directions they generate flip on their own because row already means the reading order. A value called left would have to be re-read as right by every author working in a mirrored page, which is a translation this system should be doing rather than asking for.
+
+The guidance a contract carries is part of the component, so it follows too. Describing a claim as ranging left is describing one of the two languages, and it was written that way here for a while: three of the opening bands said so in their own intent. A reader in a mirrored page meets that sentence and has to decide whether the component is wrong or the sentence is, and neither answer is one documentation should force.
+
+Two things genuinely have no logical form and are not covered by this. A CSS gradient takes a physical direction — there is no to inline-end — so a pattern that must mirror has to be stated twice under a direction query, and one that is periodic and centred, like PageHeader's rule grid, does not need to. A glyph that points the way onward is the other: an arrow is a picture of a direction, and mirroring it belongs to the icon set rather than to the component holding it.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ Scroller for: Everything fits, or should be made to fit
+   A rail that never scrolls is a line drawn by a component that also added a tab stop, a group role and a name for a region the reader never has to move. Reach for this where the overflow is expected rather than possible
+   → use `Row` instead.
+
+❌ Scroller for: The set may break onto a second line and nothing is lost by it
+   Wrapping keeps everything on screen, which is better than scrolling whenever the order does not matter and the items are short. `wrap` is the prop, and a set of tags or filters is the case
+   → use `Row` instead.
+
+❌ Scroller for: The items should line up in columns as well
+   A field shows the whole set at once and lets the rows agree. It gives up the sequence to do it, so the question is which of the two the reader is actually there for
+   → use `Grid` instead.
+
+❌ Scroller for: The region scrolls down rather than across
+   Vertical overflow belongs to whatever surface holds it — a Drawer's body, a SideNav's middle band, a BottomSheet — each of which already scrolls its own content and knows what must stay put while it does. A rail is for the axis a page does not scroll on its own
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+## Example
+
+```tsx
+import { Scroller, Card, CardBody } from '@deriv-com/dds-marketing'
+
+<Scroller label="Markets" gap="lg" snap>
+  <Card>
+    <CardBody title="Forex" description="Major, minor and exotic pairs around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="Commodities" description="Metals, energies and agricultural contracts." />
+  </Card>
+  <Card>
+    <CardBody title="Stock indices" description="The world's benchmarks in one account." />
+  </Card>
+  <Card>
+    <CardBody title="Cryptocurrencies" description="The major coins, traded at weekends too." />
+  </Card>
+  <Card>
+    <CardBody title="Stocks" description="Shares in companies you already follow." />
+  </Card>
+  <Card>
+    <CardBody title="ETFs" description="Baskets that spread a position across a sector." />
+  </Card>
+</Scroller>
+```
+
+## In use
+
+### What it is for
+
+A set longer than the page's measure, keeping its order. On a phone it is what stops a field of cards becoming a column the reader has to scroll past.
+
+```tsx
+import { Card, CardBody, Scroller } from '@deriv-com/dds-marketing'
+
+// A rail of feature cards
+<Scroller label="Markets" gap="lg" snap>
+  <Card>
+    <CardBody title="Forex" description="Major, minor and exotic pairs around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="Commodities" description="Metals, energies and agricultural contracts." />
+  </Card>
+  <Card>
+    <CardBody title="Stock indices" description="The world's benchmarks in one account." />
+  </Card>
+  <Card>
+    <CardBody title="Cryptocurrencies" description="The major coins, traded at weekends too." />
+  </Card>
+  <Card>
+    <CardBody title="Stocks" description="Shares in companies you already follow." />
+  </Card>
+  <Card>
+    <CardBody title="ETFs" description="Baskets that spread a position across a sector." />
+  </Card>
+</Scroller>
+```
+
+### Every step along the rail
+
+A gap ends at the last item. Margins on the items would run past it and make the end of the rail scrollable emptiness, which is the failure this prop exists to prevent.
+
+```tsx
+import { FilterChip, Scroller } from '@deriv-com/dds-marketing'
+
+// none — marks that read as one object
+<Scroller label="Categories" gap="none">
+  <FilterChip label="Forex" />
+  <FilterChip label="Commodities" />
+  <FilterChip label="Stock indices" />
+  <FilterChip label="Cryptocurrencies" />
+  <FilterChip label="Stocks" />
+  <FilterChip label="ETFs" />
+  <FilterChip label="Synthetics" />
+  <FilterChip label="Bonds" />
+</Scroller>
+
+// xs — a rail read as one strip
+<Scroller label="Categories" gap="xs">
+  <FilterChip label="Forex" />
+  <FilterChip label="Commodities" />
+  <FilterChip label="Stock indices" />
+  <FilterChip label="Cryptocurrencies" />
+  <FilterChip label="Stocks" />
+  <FilterChip label="ETFs" />
+  <FilterChip label="Synthetics" />
+  <FilterChip label="Bonds" />
+</Scroller>
+
+// sm — chips and small marks
+<Scroller label="Categories" gap="sm">
+  <FilterChip label="Forex" />
+  <FilterChip label="Commodities" />
+  <FilterChip label="Stock indices" />
+  <FilterChip label="Cryptocurrencies" />
+  <FilterChip label="Stocks" />
+  <FilterChip label="ETFs" />
+  <FilterChip label="Synthetics" />
+  <FilterChip label="Bonds" />
+</Scroller>
+
+// md — peers that are not controls
+<Scroller label="Categories" gap="md">
+  <FilterChip label="Forex" />
+  <FilterChip label="Commodities" />
+  <FilterChip label="Stock indices" />
+  <FilterChip label="Cryptocurrencies" />
+  <FilterChip label="Stocks" />
+  <FilterChip label="ETFs" />
+  <FilterChip label="Synthetics" />
+  <FilterChip label="Bonds" />
+</Scroller>
+
+// lg — the default — a rail of cards
+<Scroller label="Categories" gap="lg">
+  <FilterChip label="Forex" />
+  <FilterChip label="Commodities" />
+  <FilterChip label="Stock indices" />
+  <FilterChip label="Cryptocurrencies" />
+  <FilterChip label="Stocks" />
+  <FilterChip label="ETFs" />
+  <FilterChip label="Synthetics" />
+  <FilterChip label="Bonds" />
+</Scroller>
+
+// xl — cells with a picture — tightens
+<Scroller label="Categories" gap="xl">
+  <FilterChip label="Forex" />
+  <FilterChip label="Commodities" />
+  <FilterChip label="Stock indices" />
+  <FilterChip label="Cryptocurrencies" />
+  <FilterChip label="Stocks" />
+  <FilterChip label="ETFs" />
+  <FilterChip label="Synthetics" />
+  <FilterChip label="Bonds" />
+</Scroller>
+
+// 2xl — one section to the next — tightens
+<Scroller label="Categories" gap="2xl">
+  <FilterChip label="Forex" />
+  <FilterChip label="Commodities" />
+  <FilterChip label="Stock indices" />
+  <FilterChip label="Cryptocurrencies" />
+  <FilterChip label="Stocks" />
+  <FilterChip label="ETFs" />
+  <FilterChip label="Synthetics" />
+  <FilterChip label="Bonds" />
+</Scroller>
+
+// 3xl — whole movements — tightens
+<Scroller label="Categories" gap="3xl">
+  <FilterChip label="Forex" />
+  <FilterChip label="Commodities" />
+  <FilterChip label="Stock indices" />
+  <FilterChip label="Cryptocurrencies" />
+  <FilterChip label="Stocks" />
+  <FilterChip label="ETFs" />
+  <FilterChip label="Synthetics" />
+  <FilterChip label="Bonds" />
+</Scroller>
+```
+
+### How items of different heights meet
+
+The default hands every item the height of the tallest, which keeps a run of cards reading as a run. The others let each keep its own.
+
+```tsx
+import { Card, CardBody, Scroller } from '@deriv-com/dds-marketing'
+
+// stretch — the default — items finish level
+<Scroller label="Markets" gap="lg" align="stretch">
+  <Card>
+    <CardBody title="Forex" description="Major pairs." />
+  </Card>
+  <Card>
+    <CardBody title="Commodities" description="Metals, energies and the agricultural contracts that settle monthly, with rollover handled for you." />
+  </Card>
+  <Card>
+    <CardBody title="Stock indices" description="The benchmarks." />
+  </Card>
+</Scroller>
+
+// start — items keep their height, at the top
+<Scroller label="Markets" gap="lg" align="start">
+  <Card>
+    <CardBody title="Forex" description="Major pairs." />
+  </Card>
+  <Card>
+    <CardBody title="Commodities" description="Metals, energies and the agricultural contracts that settle monthly, with rollover handled for you." />
+  </Card>
+  <Card>
+    <CardBody title="Stock indices" description="The benchmarks." />
+  </Card>
+</Scroller>
+
+// center — items keep their height, centred
+<Scroller label="Markets" gap="lg" align="center">
+  <Card>
+    <CardBody title="Forex" description="Major pairs." />
+  </Card>
+  <Card>
+    <CardBody title="Commodities" description="Metals, energies and the agricultural contracts that settle monthly, with rollover handled for you." />
+  </Card>
+  <Card>
+    <CardBody title="Stock indices" description="The benchmarks." />
+  </Card>
+</Scroller>
+
+// end — items keep their height, at the foot
+<Scroller label="Markets" gap="lg" align="end">
+  <Card>
+    <CardBody title="Forex" description="Major pairs." />
+  </Card>
+  <Card>
+    <CardBody title="Commodities" description="Metals, energies and the agricultural contracts that settle monthly, with rollover handled for you." />
+  </Card>
+  <Card>
+    <CardBody title="Stock indices" description="The benchmarks." />
+  </Card>
+</Scroller>
+```
+
+### Stepping, or scanning
+
+Snapping suits items of one size the reader steps through — cards, quotes, slides. On a set being scanned it takes the scroll away at every item.
+
+```tsx
+import { Card, CardBody, FilterChip, Scroller } from '@deriv-com/dds-marketing'
+
+// false — the default, the reader scrolls freely
+<Scroller label="Categories" gap="sm" snap={false}>
+  <FilterChip label="Forex" />
+  <FilterChip label="Commodities" />
+  <FilterChip label="Stock indices" />
+  <FilterChip label="Cryptocurrencies" />
+  <FilterChip label="Stocks" />
+  <FilterChip label="ETFs" />
+  <FilterChip label="Synthetics" />
+  <FilterChip label="Bonds" />
+</Scroller>
+
+// true — each stop lands a card at the edge
+<Scroller label="Markets" gap="lg" snap>
+  <Card>
+    <CardBody title="Forex" description="Major, minor and exotic pairs around the clock." />
+  </Card>
+  <Card>
+    <CardBody title="Commodities" description="Metals, energies and agricultural contracts." />
+  </Card>
+  <Card>
+    <CardBody title="Stock indices" description="The world's benchmarks in one account." />
+  </Card>
+  <Card>
+    <CardBody title="Cryptocurrencies" description="The major coins, traded at weekends too." />
+  </Card>
+  <Card>
+    <CardBody title="Stocks" description="Shares in companies you already follow." />
+  </Card>
+  <Card>
+    <CardBody title="ETFs" description="Baskets that spread a position across a sector." />
+  </Card>
+</Scroller>
+```