@deriv-com/dds-marketing 1.0.2 → 1.1.0

package/.llm/components/testimonialrow.md

@@ -94,6 +94,11 @@ Use when: The accessible name of the arrow stepping the row back. A glyph announ
 
 Use when: The accessible name of the arrow stepping the row on, for the reason previousLabel exists.
 
+### externalLabel — `string` (default `(opens in a new tab)`)
+
+Use when: Said after the summary link and every linked review, because both open on a service the page does not own, in a new tab, and a reader should know before they press — TeamGrid's and ResourceBanner's words for the same thing. Translate it with the page.
+Never for: Visible text. It is added to the link's name for assistive technology and never drawn.
+
 ## 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.

package/.llm/components/testimonialslider.md

@@ -89,6 +89,19 @@ Use when: The name the dots are announced by. Its own name rather than the secti
 
 Use when: The word each dot is announced by, before its number — 'Slide 2'. Translate it with the page, as controlsLabel is; a page that translates only the group's name still has every dot announced in English.
 
+### roleDescription — `string` (default `carousel`)
+
+Use when: What a screen reader calls the set while it rotates — announced in place of a region, as the word for this kind of thing. Translate it with the page: it is read out as given, so an untranslated one announces an English word on every page in every language.
+
+### slideRoleDescription — `string` (default `slide`)
+
+Use when: What a screen reader calls each item while the set rotates, for the reason roleDescription exists. Translate it with the page.
+
+### positionLabel — `callback`
+
+Use when: The accessible name of each item while the set rotates, given its place in the set counting from one — so a reader hears where they are. Without it each is named "2 of 5"; pass it to translate that with the page, in that language's own order and digits.
+Never for: Visible text. It names the item to assistive technology and is never drawn.
+
 ## 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.
@@ -98,7 +111,7 @@ Guaranteed by the component. Write none of it by hand: the ids these attributes
 - `Enter` — On a dot, moves to that quote
 - accessible name from title, so the section is a named region a reader can jump to and skip
 - Each quote is a figure holding a blockquote and its figcaption, so the words and the person they are attributed to are announced together.
-- Every quote out of view is inert and hidden from assistive technology, and the one in view is named by its position — '2 / 3'.
+- Every quote out of view is inert and hidden from assistive technology, and the one in view is named by its position — '2 of 3'.
 - Under autoplay, a hold while the pointer is over the section or focus is inside it, no movement for a reader who asked for less motion, and a stop for good once the reader presses anything in it or swipes it — CtaBannerSlider's rules, shared through use-rotation.
 - The corner pictures are decorative: an empty alt and hidden from assistive technology, so the quotes are announced without them.
 

package/.llm/components/textarea.md

@@ -134,6 +134,19 @@ Never for: Varying within one form. Whichever is chosen is a decision for the wh
 Use when: Most fields on the form are required, so the few that are not are worth marking instead
 Never for: Marking every optional field on a form where most are optional — a marker on almost every label is noise, and the useful signal is whichever state is the exception
 
+### requiredLabel — `string` (default `required`)
+
+Use when: The word drawn beside the label when requiredMark is text. Translate it with the page: the mark exists to say what it means in the reader's own language, which an English default does not.
+
+### optionalLabel — `string` (default `optional`)
+
+Use when: The word drawn beside the label of an optional field. Translate it with the page, as requiredLabel is.
+
+### labelTooltipLabel — `string`
+
+Use when: The accessible name of the button that opens labelTooltip. Without it the button is named "About" and the label; pass it to translate that with the page.
+Never for: Visible text. It names the button to assistive technology and is never drawn.
+
 Also accepts everything from `TextareaHTMLAttributes<HTMLTextAreaElement>`.
 
 ## States

package/.llm/components/textinput.md

@@ -189,6 +189,19 @@ Never for: Carrying the requirement on its own. The mark is decorative either wa
 Use when: Most of the form is required and one field is not. Marking the exception is what tells the reader anything
 Never for: Every field on a form where nothing is required. Marking all of them says the same as marking none, and costs a word on each
 
+### requiredLabel — `string` (default `required`)
+
+Use when: The word drawn beside the label when requiredMark is text. Translate it with the page: the mark exists to say what it means in the reader's own language, which an English default does not.
+
+### optionalLabel — `string` (default `optional`)
+
+Use when: The word drawn beside the label of an optional field. Translate it with the page, as requiredLabel is.
+
+### labelTooltipLabel — `string`
+
+Use when: The accessible name of the button that opens labelTooltip. Without it the button is named "About" and the label; pass it to translate that with the page.
+Never for: Visible text. It names the button to assistive technology and is never drawn.
+
 Also accepts everything from `InputHTMLAttributes<HTMLInputElement>`.
 
 ## States

package/.llm/components/textscroll.md

@@ -0,0 +1,187 @@
+<!-- GENERATED from text-scroll.contract.json. Do not edit. -->
+
+# TextScroll
+
+A full-width section holding one large statement — a mission, a brand message — whose words brighten one after another as the reader scrolls past, from dimmed to full strength, so the sentence is read at the pace the page is moved.
+
+The reference design's TextScroll. The reveal is scrubbed by the scroll itself rather than timed: each word runs down the section's own view timeline a step behind the one before it, forward as the reader scrolls down and back again as they scroll up, and stands still while the page does. The sentence is in the page's first HTML as one paragraph of real words and spaces, so a reader with no script, a browser with no scroll timeline and a reader who asked for less movement all get the whole statement at full strength from the start; the dim is only ever something the scroll applies.
+
+## Use when
+
+- A mission or vision statement, on an About or Who we are page
+- One emphatic brand message between two heavier sections, where a moment of copy on its own gives the page room to breathe
+- A campaign or partner programme's manifesto, in one sentence or two short ones
+
+## Do not use
+
+- The statement needs a heading over it, a line under it or a way onward → `FeatureSplit`
+- The message asks the reader to do something → `CtaBanner`
+- Long-form copy, or more than one paragraph. Past about three hundred characters the reveal outlasts the section's pass and the last words are still dim as it leaves
+- Copy that must be legible the moment it is on screen — a disclaimer, a legal line, a price. Words below the reveal's front are dimmed until the reader scrolls to them
+- Two of these back to back. A second reveal straight after the first is the same moment twice, and the page loses the pause the first one made
+
+## Anatomy
+
+TextScroll renders 4 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-textscroll`. The section. It paints the ground and the ink to go with it — see `ground` — asks its own width, so the statement turns to the centre on the section's measure rather than the window's, and carries the view timeline every word runs down. Not a named region: the statement is its only content, and naming the region by it would read the sentence twice to a reader arriving in it. It clips with `overflow: clip` if it ever clips, never `hidden`, which would make it a scroll container and freeze the timeline.
+- `inner` — `<div>`, class `dds-textscroll__inner`. The measure and the gutter, the same column every band holds its content in, with the section's air above and below.
+- `text` — `<p>`, class `dds-textscroll__text`. The statement, at the h4 step — the reference design's size, and a size rather than a level: it is a paragraph, because it is something the page says rather than the name of what follows. Ranged to the start on a phone and centred from the fold, held to the hero heading's measure so a centred line is not read from a different edge every time. One paragraph of real words with a real space between each, so assistive technology, find-in-page and a copy all get the sentence as written. On a phone it takes the h3 step instead — 32px there against h4's 24 — because the statement has the screen's width to itself; from the fold it is h4, the reference's size.
+- `word` — `<span>`, class `dds-textscroll__word`. One word of the statement, in the band's ink, and inline — the sentence wraps as the words of one paragraph, never as a row of boxes. Under a scroll timeline it starts at opacity.track — the dimmed share of the same ink a track recedes to behind what travels over it — and comes up to full strength over its own stretch of the section's pass, a step behind the word before it. At full strength wherever there is no timeline to run it, and never hidden from assistive technology.
+
+Apply these classes from the generated `textScrollParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `TextScroll`, `LandingHero`, `ProductHero`, `PageHeader`, `Footer`, `Navbar` — in children or in any prop that takes a node
+
+## Props
+
+### ground — `page` | `subtle` | `strong` (default `page`)
+
+- `page` — The default, and the page's own white. A statement between two sections that need nothing to separate them
+- `subtle` — The grey band, for a statement that should read as a section of its own without changing the page's voice. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section
+- `strong` — `color.bg.brand-strong`, the dark band, for the statement a page is built around — the mission on an About page. The words turn white and dim toward the band
+
+Use when: Which of the page's three grounds this section paints, the axis every block shares: a statement that wants to be seen as a band takes one of the other two, and the page decides the rhythm. The words take the band's own ink and dim toward its ground, so the reveal reads the same on all three.
+Never for: Marking importance. Every section on a page painted a ground is a page with no emphasis left. And never the brand's own coral, which is not offered: a paragraph on it misses the contrast running copy needs.
+
+### text — `string` **Required.**
+
+Use when: Always. The statement, as plain text — one sentence or two short ones, under about three hundred characters. Split into words on its whitespace, so a run of spaces or a line break is one space in what is drawn. Written so it reads well a word at a time, because that is how the reveal delivers it: "We believe trading should be accessible to everyone, everywhere, with the tools and the trust to do it well."
+Never for: Markup, emphasis or a link. The words are drawn as text and nothing in the string is interpreted; a statement that needs a word set apart or a way onward is a FeatureSplit.
+
+## 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.
+
+- `Tab` — Moves past the section. Nothing in it is operable — the statement is read, not used — so there is nothing here to land on.
+- The statement is one paragraph of real text with a space between each word, so assistive technology, find-in-page and a copy read it as the sentence it is. No word is hidden from assistive technology and none is drawn by a pseudo-element.
+- Every word is at full strength wherever the scroll is not driving it — before any script, in a browser with no scroll timeline, and for a reader who asked for less movement, who sees the whole statement still from the start.
+
+## 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, CardButton and TextInput 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
+
+❌ TextScroll for: The statement needs a heading over it, a line under it or a way onward
+   A claim with an explanation and a link is a split; this is one statement and nothing else
+   → use `FeatureSplit` instead.
+
+❌ TextScroll for: The message asks the reader to do something
+   A call to action needs a button, and a sentence still dim when a reader arrives is the wrong place for an ask
+   → use `CtaBanner` instead.
+
+## Example
+
+```tsx
+import { TextScroll } from '@deriv-com/dds-marketing'
+
+<TextScroll text="We believe trading should be accessible to everyone, everywhere, with the tools and the trust to do it well." />
+```
+
+## In use
+
+### Grounds
+
+The same statement on the page, the grey band and the dark band. The words take the band's ink and dim toward its ground.
+
+```tsx
+import { TextScroll } from '@deriv-com/dds-marketing'
+
+// On the page
+<TextScroll text="We believe trading should be accessible to everyone, everywhere, with the tools and the trust to do it well." />
+
+// On the grey band
+<TextScroll ground="subtle" text="We believe trading should be accessible to everyone, everywhere, with the tools and the trust to do it well." />
+
+// On the dark band
+<TextScroll ground="strong" text="We believe trading should be accessible to everyone, everywhere, with the tools and the trust to do it well." />
+```
+
+### Length
+
+A short line brightens a word at a time across the pass; a two-sentence statement near the limit spreads the same pass over more words.
+
+```tsx
+import { TextScroll } from '@deriv-com/dds-marketing'
+
+// One short sentence
+<TextScroll text="Trading made simple, for everyone." />
+
+// Two sentences, near the limit
+<TextScroll ground="strong" text="We're a trading platform that gives everyone, everywhere the power to trade the world's markets. Since 1999 we've built the tools, the technology and the team to make trading accessible, transparent and fair." />
+```

package/.llm/components/tiers.md

@@ -0,0 +1,227 @@
+<!-- GENERATED from tiers.contract.json. Do not edit. -->
+
+# Tiers
+
+A partnership-tier section: a centred heading over an ordered row of tiers, each a medal, a name and the stage it stands for, a card stating what the tier gives, and the bar a partner clears to reach it — with an optional way on under the row.
+
+It shows how rewards grow with performance, Bronze to Platinum, and the order is the argument: each tier is a step up from the one before it. The tiers are a real ordered list, so the count and each tier's place reach a screen reader too. At full width they share one row and a rule runs through the medals, joining them into one track; below that they fall to two columns and then one, where each tier's words start at the edge.
+
+It sits on the page's own ground by default; `ground` paints the grey or the dark band where the section needs setting apart from the ones around it.
+
+## Use when
+
+- A partner, affiliate or introducing-broker programme explains its tiers and what each one earns
+- Rewards grow with performance in two to four steps — commission bonuses, loyalty levels, a VIP ladder — and each step has a bar to clear
+- A partner landing page needs the progression shown at a glance, with a link on to the programme's full terms
+
+## Do not use
+
+- The items have no order — they are things a product includes, or reasons to choose it → `FeatureCards`
+- The items are things a reader does, one after another, to get started → `Steps`
+- Plans a reader chooses between, each with the same rows of terms → `ComparisonCards`
+- More than four tiers. The row holds four at full width and the track through the medals has nowhere to go past that; a longer ladder wants a table
+- Plans or prices a reader picks between. A tier is reached, not bought, and a row that reads as a progression tells a reader the cheaper plan is a step on the way to the dearer one
+- A tier promised without its bar. A benefit with no stated qualification on anything above the entry tier is a claim the page cannot stand behind
+
+## Anatomy
+
+Tiers renders 19 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-tiers`. The section. It paints the ground and the ink to go with it — see `ground` — and asks its own width, so the row folds on the section's measure rather than the window's.
+- `inner` — `<div>`, class `dds-tiers__inner`. The measure and the gutter, the same column every band holds its content in, and the step from the heading to the tiers: space.heading.content.
+- `header` — `<div>`, class `dds-tiers__header`. The heading and the line under it. Ranged to the start on a phone and centred from the fold, over the row it introduces. It sets no gap: the title's own margin is the step, so a header without a line closes up rather than leaving its gap behind.
+- `title` — `<h2>`, class `dds-tiers__title`. What the tiers add up to. `h2` because a section sits under the page's own heading; the tiers' names come below it in the outline.
+- `description` — `<p>`, class `dds-tiers__description`. The line under the heading, at the description measure. Rendered only when `description` is set.
+- `list` — `<ol>`, class `dds-tiers__list`. The tiers, as an ordered list — a screen reader announces how many there are and where each sits, which is the progression the section exists to say. One column on a phone, two from the fold, and at full width one row holding them all, as many columns as there are tiers. The space between tiers, across and down, is the page grid's gutter.
+- `tier` — `<li>`, class `dds-tiers__tier`. One tier: its medal, its name and stage, the card saying what it gives, and the bar that reaches it. Its words start at the edge on a phone and are centred from the fold, under the medal. The tiers arrive one after another as the section comes up, lowest first, so the ladder is climbed as it appears.
+- `medal-row` — `<div>`, class `dds-tiers__medal-row`. The medal and the track either side of it. At full width the row reaches half a gutter past the tier on each side, so one tier's track meets the next one's and the rule runs through every medal as one line.
+- `line-start` — `<span>`, class `dds-tiers__line-start`. The track leading into the medal. Decoration, hidden from assistive technology, and drawn only at full width, where every tier shares one row — stacked or in two columns there is no line for it to be part of. The first tier's is left blank so the track starts at the first medal rather than at the page's edge.
+- `medal` — `<img>`, class `dds-tiers__medal`. The tier's medal, a square with rounded corners at every source shape: the picture fills it and is cropped to it, so a landscape or a tall source still gives a row of matching tiles. Decoration with empty alternative text: the name under it is the heading, and a medal announced by the same word says it twice.
+- `line-end` — `<span>`, class `dds-tiers__line-end`. The track leading out of the medal to the next one. Decoration, hidden from assistive technology, and drawn only at full width. The last tier's is left blank so the track stops at the last medal.
+- `heading` — `<div>`, class `dds-tiers__heading`. The tier's name and its stage. One line on a phone, the stage after the name, and stacked from the fold, the stage under the name — the reference design's two arrangements.
+- `name` — `<h3>`, class `dds-tiers__name`. The tier's name. `h3` under the section's `h2`, so a reader moving by heading walks the tiers one at a time.
+- `stage` — `<p>`, class `dds-tiers__stage`. The stage the tier stands for, in the ground's quieter ink.
+- `benefit` — `<div>`, class `dds-tiers__benefit`. Inside the page's own Card: the card's inset and the benefit's headline and sentence, held together at a card's title-to-description step. The Card grows to the tallest in the row, so the cards end level and the qualifications under them start on one line.
+- `benefit-title` — `<p>`, class `dds-tiers__benefit-title`. What the tier gives, as a headline. A paragraph rather than a heading: the tier's name is the heading, and this is what is under it.
+- `benefit-description` — `<p>`, class `dds-tiers__benefit-description`. What the benefit means, in a sentence.
+- `qualification` — `<p>`, class `dds-tiers__qualification`. What it takes to reach the tier, under its card. A line break in it is kept, so the measure and the amount sit on lines of their own. Drawn only for a tier that has one — the entry tier has nothing to clear.
+- `footer` — `<div>`, class `dds-tiers__footer`. The way on, under the row. At the start on a phone and centred from the fold, under the centred heading. It adds no step of its own: the gap from the tiers is the inner column's, the one between a heading and what it introduces. Rendered only when `link` is set.
+
+Apply these classes from the generated `tiersParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `Tiers`, `Steps`, `FeatureCards`, `LandingHero`, `ProductHero`, `PageHeader`, `Footer`, `Navbar`, `Table`, `Accordion` — in children or in any prop that takes a node
+
+## Props
+
+### ground — `page` | `subtle` | `strong` (default `page`)
+
+- `page` — The default, and the page's own white. A section that has nothing to separate itself from what is above it — most of them. The benefit cards are Card's recessed grey on it.
+- `subtle` — A quiet step off the page, for a band that wants to read as its own section without changing the page's voice. The reference design paints this section grey, and a page following it closely takes this. The benefit cards turn white on it, color.bg.surface-card-raised, because their recessed grey is the band's own and would vanish into it.
+- `strong` — `color.bg.brand-strong`, the dark band. It stops the page rather than dividing it, so it is for a section a reader should arrive at — and one per page is usually one more than enough. The benefit cards turn round to the inverse surface and white ink, and the track between the medals to the band's own quiet rule.
+
+Use when: Which of the page's three grounds this section paints. A marketing page is white, and a band that wants to be seen as a band takes one of the other two — so this is how a page builds its rhythm: white, white, grey, white, dark. The section above knows nothing about the one below it, so the page is the only thing that can decide.
+
+The ink follows the ground and is not a second decision: a dark band carries white type because this sets both halves in one value, and the cards and the track change with it.
+Never for: Marking importance. Every section on a page painted dark is a page with no emphasis left. And never the brand's own coral, `color.bg.brand`, which is not offered here: that ground belongs to the band that asks a reader to do something, and a tier section wearing it is a page with two calls to action, one of which does nothing.
+
+### title — `string` **Required.**
+
+Use when: Always. What the tiers add up to, in the fewest words that say it — 'Growing rewards as you scale'.
+Never for: A sentence. The line under it is for the sentence.
+
+### description — `string`
+
+Use when: A line saying how the tiers work, when the title alone does not — 'Our tiered partnership model rewards performance.'
+Never for: A paragraph, or a summary of every tier. The tiers say what they give; this only says why they are a ladder.
+
+### tiers — `data` `TiersItem[]` **Required.**
+
+Use when: Always. The tiers, lowest first — two to four, four for a partnership programme. Each is a one-word `name`, a one-verb `stage`, a `medal` picture, a `benefit` headline and the sentence under it, and — on every tier above the entry one — the `qualification` that reaches it, with a line break before the amount. The order of the list is the order of the ladder, so reordering it reorders the tiers.
+Never for: Tiers in any order but lowest to highest. The track through the medals reads start to end, and a ladder drawn out of order is one a reader climbs the wrong way.
+
+### link — `node`
+
+Accepts: Link
+Use when: A way on to the programme's full terms — 'Learn more about partner tiers'. A standalone Link, under the row.
+Never for: A button, or the sign-up itself. The section explains the ladder; asking a reader to join is the job of the band that does nothing else.
+
+## 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: `region`
+- `Tab` — Moves to the link under the row, if there is one. Nothing else in the section is operable — the tiers are read, not used.
+- accessible name from title, so the section is a named region a screen reader can jump to and skip
+- The tiers are an ordered list, so a screen reader announces how many there are and each one's place in the progression. A row of divs reads as a set of equals and loses the order, which is what the section is for
+- Each tier's name is a heading one level under the section's, so a reader moving by heading walks the tiers one at a time
+- The medal is decoration with empty alternative text, and the track through the medals is hidden from assistive technology. The name is what identifies a tier; a medal announced by the same word says it twice, and a line has nothing to say
+
+## 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, CardButton and TextInput 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
+
+❌ Tiers for: The items have no order — they are things a product includes, or reasons to choose it
+   A grid of cards is compared in any order; a row of tiers is climbed, and the track through the medals says so
+   → use `FeatureCards` instead.
+
+❌ Tiers for: The items are things a reader does, one after another, to get started
+   A numbered how-to list beside a picture. Tiers are levels a partner reaches rather than actions they take
+   → use `Steps` instead.
+
+❌ Tiers for: Plans a reader chooses between, each with the same rows of terms
+   Options laid against one another row by row; tiers are not chosen, they are earned in order
+   → use `ComparisonCards` instead.
+
+## Example
+
+```tsx
+import { Tiers, Link } from '@deriv-com/dds-marketing'
+
+<Tiers ground="subtle" title="Growing rewards as you scale" description="Our tiered partnership model rewards performance. As you grow, you unlock higher bonuses." tiers={[{"name":"Bronze","stage":"Launch","medal":"/sample-stop-amber.svg","benefit":"Full access from day one","description":"Every partner tool, report and marketing asset, from the day you join."},{"name":"Silver","stage":"Grow","medal":"/sample-stop-teal.svg","benefit":"Commission + 4% bonus","description":"An extra 4% on top of your commission, paid every month.","qualification":"3-month average commission:\n$500+"},{"name":"Gold","stage":"Scale","medal":"/sample-stop-brand.svg","benefit":"Commission + 6% bonus","description":"Your monthly bonus grows to 6% to match your performance.","qualification":"3-month average commission:\n$1,000+"},{"name":"Platinum","stage":"Lead","medal":"/sample-stop-purple.svg","benefit":"Commission + 8% bonus","description":"A further quarterly bonus and invitations to our annual partner events.","qualification":"3-month average commission:\n$5,000+"}]} link={<Link href="/partners/tiers">Learn more about partner tiers</Link>} />
+```
+
+## In use
+
+### Four tiers and three
+
+A partnership ladder in four tiers, one row with a track through the medals; three tiers take three columns. The entry tier has no bar to clear.
+
+```tsx
+import { Link, Tiers } from '@deriv-com/dds-marketing'
+
+// Four tiers, with a way on
+<Tiers title="Growing rewards as you scale" description="Our tiered partnership model rewards performance. As you grow, you unlock higher bonuses." tiers={[{"name":"Bronze","stage":"Launch","medal":"/sample-stop-amber.svg","benefit":"Full access from day one","description":"Every partner tool, report and marketing asset, from the day you join."},{"name":"Silver","stage":"Grow","medal":"/sample-stop-teal.svg","benefit":"Commission + 4% bonus","description":"An extra 4% on top of your commission, paid every month.","qualification":"3-month average commission:\n$500+"},{"name":"Gold","stage":"Scale","medal":"/sample-stop-brand.svg","benefit":"Commission + 6% bonus","description":"Your monthly bonus grows to 6% to match your performance.","qualification":"3-month average commission:\n$1,000+"},{"name":"Platinum","stage":"Lead","medal":"/sample-stop-purple.svg","benefit":"Commission + 8% bonus","description":"A further quarterly bonus and invitations to our annual partner events.","qualification":"3-month average commission:\n$5,000+"}]} link={<Link href="/partners/tiers">Learn more about partner tiers</Link>} />
+
+// Three tiers, no line or link
+<Tiers title="Earn more as your clients trade" tiers={[{"name":"Bronze","stage":"Launch","medal":"/sample-stop-amber.svg","benefit":"Up to $10 per lot","description":"Earn on every lot your referred clients trade on CFDs."},{"name":"Silver","stage":"Grow","medal":"/sample-stop-teal.svg","benefit":"Up to $12 per lot","description":"A higher rate per lot once your clients trade more.","qualification":"Monthly volume:\n500 lots+"},{"name":"Gold","stage":"Scale","medal":"/sample-stop-brand.svg","benefit":"Up to $15 per lot","description":"Our highest rate, and a dedicated partner manager.","qualification":"Monthly volume:\n2,000 lots+"}]} />
+```
+
+### On the grey band and the dark one
+
+ground="subtle" sets the section apart and turns the cards white; ground="strong" stops the page and turns the cards and the track round.
+
+```tsx
+import { Link, Tiers } from '@deriv-com/dds-marketing'
+
+// Subtle ground
+<Tiers ground="subtle" title="Growing rewards as you scale" tiers={[{"name":"Bronze","stage":"Launch","medal":"/sample-stop-amber.svg","benefit":"Full access from day one","description":"Every partner tool, report and marketing asset, from the day you join."},{"name":"Silver","stage":"Grow","medal":"/sample-stop-teal.svg","benefit":"Commission + 4% bonus","description":"An extra 4% on top of your commission, paid every month.","qualification":"3-month average commission:\n$500+"},{"name":"Gold","stage":"Scale","medal":"/sample-stop-brand.svg","benefit":"Commission + 6% bonus","description":"Your monthly bonus grows to 6% to match your performance.","qualification":"3-month average commission:\n$1,000+"},{"name":"Platinum","stage":"Lead","medal":"/sample-stop-purple.svg","benefit":"Commission + 8% bonus","description":"A further quarterly bonus and invitations to our annual partner events.","qualification":"3-month average commission:\n$5,000+"}]} />
+
+// Strong ground
+<Tiers ground="strong" title="Growing rewards as you scale" description="Our tiered partnership model rewards performance. As you grow, you unlock higher bonuses." tiers={[{"name":"Bronze","stage":"Launch","medal":"/sample-stop-amber.svg","benefit":"Full access from day one","description":"Every partner tool, report and marketing asset, from the day you join."},{"name":"Silver","stage":"Grow","medal":"/sample-stop-teal.svg","benefit":"Commission + 4% bonus","description":"An extra 4% on top of your commission, paid every month.","qualification":"3-month average commission:\n$500+"},{"name":"Gold","stage":"Scale","medal":"/sample-stop-brand.svg","benefit":"Commission + 6% bonus","description":"Your monthly bonus grows to 6% to match your performance.","qualification":"3-month average commission:\n$1,000+"},{"name":"Platinum","stage":"Lead","medal":"/sample-stop-purple.svg","benefit":"Commission + 8% bonus","description":"A further quarterly bonus and invitations to our annual partner events.","qualification":"3-month average commission:\n$5,000+"}]} link={<Link href="/partners/tiers" tone="inherit">Learn more about partner tiers</Link>} />
+```

package/.llm/digest/awards.md

@@ -0,0 +1,45 @@
+<!-- GENERATED from awards.contract.json. Do not edit. -->
+
+# Awards
+
+A section of social proof that lists the industry awards a company has won, each a badge between two laurels: a laurel, the award's name and its issuer, and the same laurel mirrored. …
+
+`import { Awards } from '@deriv-com/dds-marketing'`
+
+## Reach for it when
+
+- Building credibility with the industry awards a company has won — a “Why choose us”, about-us or trust page
+- Six awards or more, enough that the phone's row reads as running on past the band's edge and the rows from the fold read as a field
+
+## Something else, when
+
+- One to three awards, or a few figures that make the case → **FeatureCards**
+- Partners, integrations or payment methods rather than awards → **LogoRows**
+- Reviews from customers rather than recognition from the industry → **TestimonialRow**
+
+## Never
+
+- An award the company has not won, or one restated in words the issuer did not use. Each badge is a claim made in the issuer's name
+- Awards a reader is meant to press through to. The badges are words, not links; a page that needs each to open a press release wants cards
+- The page's opening band. This sits under the page's heading, never in place of it
+
+## Props
+
+- **ground** `enum` · default "page" — Which of the page's three grounds this section paints, and with it the ink: the awards' words take the band's ink and the laurels its quieter one. The page's white is the reference design's ground for this section
+  - `page` — The default, and the reference design's: the page's own white, with the laurels in color.fg.muted
+  - `subtle` — The grey band, for a section that needs setting apart from the one above it. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section
+  - `strong` — `color.bg.brand-strong`, the dark band, for a section a reader should arrive at. The heading and the awards turn white and the laurels take color.fg.muted-inverse, the band's own quieter ink
+  - never: Marking importance. Every section on a page painted a ground is a page with no emphasis left, and a reader stops reading the grounds as meaning anything. And never the brand's own coral, `color.bg.brand`, which is not offered here. That ground belongs to the band that asks a reader to do something, and an awards section asks for nothing
+- **title** `string` · required — Always. What the badges are, in the fewest words that name them — "Our awards"
+  - never: An award, or a claim the awards are meant to prove. The badges are the evidence; the heading only says what they are
+- **awards** `data` · required — Always. The awards, in the order they are read — across each row from the fold, and along the one row on a phone. Newest first, usually: the year is what says a claim is current. Six or more, so the phone's row runs on past the band's edge. …
+  - never: An award listed twice to fill a row. A page passes each award once; the rows are the section's to arrange
+
+## Inside it
+
+- 6 components are refused inside it; the list and the reasons are in the long document.
+- Renders 10 parts: root, inner, header, title, list, award, laurel, copy, name, issuer.
+
+---
+
+The reasoning behind each of these, the parts this renders, its states and snippets that compile: `.llm/components/awards.md`.