@deriv-com/dds-marketing 1.1.3 → 1.2.0

package/.llm/components/featurebullets.md

@@ -129,6 +129,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   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 page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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.

package/.llm/components/featurecards.md

@@ -30,7 +30,7 @@ One card is the reference design's single panel: it takes the whole row, and fro
 
 FeatureCards renders 8 elements. A token binding names the part it applies to.
 
-- `root` — `<section>`, class `dds-featurecards`. The section. It paints the ground and the ink to go with it — see `ground` — and asks its own width, so the grid folds on the section's measure rather than the window's.
+- `root` — `<section>`, class `dds-featurecards`. The section. It paints the ground and the ink to go with it — see `ground` — and asks its own width, so the grid folds on the section's measure rather than the window's. Given `background`, it draws the page's one patterned band: a Background as its first layer, under everything it holds, in the tone of its ground.
 - `inner` — `<div>`, class `dds-featurecards__inner`. The measure and the gutter, the same column every band holds its content in, and the step from the heading to the grid: space.heading.content.
 - `header` — `<div>`, class `dds-featurecards__header`. The heading, the line under it and the way on. Ranged to the start on a phone and centred from the fold, PageHeader's rule and its reason. It sets no gap: each part's own margin is the step, so a header without a line closes up rather than leaving its gap behind.
 - `title` — `<h2>`, class `dds-featurecards__title`. What the cards are. `h2` because a section sits under the page's own heading; the cards' titles come below it in the outline.
@@ -52,7 +52,7 @@ Apply these classes from the generated `featureCardsParts` constant rather than
 ### 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 — and the ground a reader is already on
-- `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 one to reach for first when two sections need telling apart. A light card — surface-light — turns white on it, color.bg.surface-card-light-raised, because its own gray.50 is the band's and would vanish into it. A dark card — accent-strong — is lifted to color.bg.surface-card-strong-raised, a step lighter in dark mode, where the band is within a shade of its gray.900. A plain surface card is raised off it the same way, to color.bg.surface-card-raised, because the recessed fill is the band's gray too. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section — in dark mode the tint alone took on whatever it was set against, and on a light surface it was light ink on white.
+- `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 one to reach for first when two sections need telling apart. A light card — surface-light — turns white on it, color.bg.surface-card-light-raised, because its own gray.50 is the band's and would vanish into it. A dark card — accent-strong — is lifted to color.bg.surface-card-strong-raised, a step lighter in dark mode, where the band is within a shade of its slate.900. A plain surface card is raised off it the same way, to color.bg.surface-card-raised, because the recessed fill is the band's gray too. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section — in dark mode the tint alone took on whatever it was set against, and on a light surface it was light ink on white.
 - `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 coloured cards keep their own grounds on it; a neutral card — surface or surface-raised — turns to Card's inverse fill and white ink, and a plain card takes the white ink alone, because their own would be dark ink on near-black; an eyebrow inside any of them takes the band's quieter ink
 
 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. Two in a row is a deliberate pair rather than an accident, and the section above knows nothing about the one below it, so the page is the only thing that can decide.
@@ -62,6 +62,17 @@ Never for: Marking importance. Every section on a page painted dark is a page wi
 
 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 — the one place on a page where the brand colour is the point rather than decoration — and a feature section wearing it is a page with two calls to action, one of which does nothing. It is `color.bg.brand-strong` that this offers: the dark brand ground, which is a band breaking a page rather than a band asking for something.
 
+### background — `halftone` | `aurora` | `mesh` | `grid` | `rings`
+
+- `halftone` — A field of coral dots that grow towards a soft glow at the band's foot and settle to a fine screen away from it.
+- `aurora` — Curtains of the brand's light rising from the band's foot and swaying slowly.
+- `mesh` — The band in the brand's reds folded into one another like a liquid — the loudest of the five, for a dark band.
+- `grid` — Hairlines a pitch apart rising from a soft bloom at the band's foot — the quietest, and the one to reach for first.
+- `rings` — Hairline circles spreading out from the middle of the band's foot.
+
+Use when: The page's one patterned band, between its hero and its closing call to action — a band a reader should stop at. The pattern is drawn by Background as the section's first layer, under its content and over nothing, in the tone of the ground: the light pattern on `page`, the same on the grey of `subtle`, the dark one on `strong`. Every pattern rises from the band's foot, which this block leaves open under its content. Leave it out and the band is its flat ground, as most bands on a page are.
+Never for: More than one band on a page, or a band that is already the hero or the call to action — those carry their own patterns. One pattern is what makes a band the one a reader remembers; two make neither, and a page of them is noise. Never wrap this block in a Background instead: it paints its own ground over whatever is behind it, so the pattern would be hidden, and the pattern belongs under the content, not around it.
+
 ### title — `string` **Required.**
 
 Use when: Always. What the cards are, in the fewest words that name them — "Why trade with Deriv", "Markets you can trade".
@@ -103,6 +114,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   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 page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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.
@@ -353,3 +370,26 @@ import { ClockThreeRegularIcon, FileShieldRegularIcon, GlobeRegularIcon, LockReg
   </Card>
 </FeatureCards>
 ```
+
+### The page's one patterned band
+
+One band per page, between the hero and the closing call to action, its pattern drawn under the content in the tone of its ground.
+
+```tsx
+import { FeatureCards, Link } from '@deriv-com/dds-marketing'
+
+// grid on page
+<FeatureCards title="Why trade with Deriv" description="Everything you need to trade the markets, in one account." link={<Link href="/why-deriv">Learn more</Link>} background="grid" ground="page">{cards}</FeatureCards>
+
+// rings on subtle
+<FeatureCards title="Why trade with Deriv" description="Everything you need to trade the markets, in one account." link={<Link href="/why-deriv">Learn more</Link>} background="rings" ground="subtle">{cards}</FeatureCards>
+
+// halftone on strong
+<FeatureCards title="Why trade with Deriv" description="Everything you need to trade the markets, in one account." link={<Link href="/why-deriv">Learn more</Link>} background="halftone" ground="strong">{cards}</FeatureCards>
+
+// aurora on strong
+<FeatureCards title="Why trade with Deriv" description="Everything you need to trade the markets, in one account." link={<Link href="/why-deriv">Learn more</Link>} background="aurora" ground="strong">{cards}</FeatureCards>
+
+// mesh on strong
+<FeatureCards title="Why trade with Deriv" description="Everything you need to trade the markets, in one account." link={<Link href="/why-deriv">Learn more</Link>} background="mesh" ground="strong">{cards}</FeatureCards>
+```

package/.llm/components/featurecardscarousel.md

@@ -53,7 +53,7 @@ Apply these classes from the generated `featureCardsCarouselParts` constant rath
 ### 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 — and the ground a reader is already on
-- `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 one to reach for first when two sections need telling apart. A light card — surface-light — turns white on it, color.bg.surface-card-light-raised, because its own gray.50 is the band's and would vanish into it. A dark card — accent-strong — is lifted to color.bg.surface-card-strong-raised, a step lighter in dark mode, where the band is within a shade of its gray.900. A plain surface card is raised off it the same way, to color.bg.surface-card-raised, because the recessed fill is the band's gray too. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section — in dark mode the tint alone took on whatever it was set against, and on a light surface it was light ink on white.
+- `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 one to reach for first when two sections need telling apart. A light card — surface-light — turns white on it, color.bg.surface-card-light-raised, because its own gray.50 is the band's and would vanish into it. A dark card — accent-strong — is lifted to color.bg.surface-card-strong-raised, a step lighter in dark mode, where the band is within a shade of its slate.900. A plain surface card is raised off it the same way, to color.bg.surface-card-raised, because the recessed fill is the band's gray too. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section — in dark mode the tint alone took on whatever it was set against, and on a light surface it was light ink on white.
 - `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 coloured cards keep their own grounds on it; a neutral card — surface or surface-raised — turns to Card's inverse fill and white ink, and a plain card takes the white ink alone, because their own would be dark ink on near-black; an eyebrow inside any of them takes the band's quieter ink
 
 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. Two in a row is a deliberate pair rather than an accident, and the section above knows nothing about the one below it, so the page is the only thing that can decide.
@@ -129,6 +129,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   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 page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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.

package/.llm/components/featurescroll.md

@@ -158,6 +158,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   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 page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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.

package/.llm/components/featuresplit.md

@@ -122,6 +122,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   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 page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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.

package/.llm/components/featurestack.md

@@ -102,6 +102,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   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 page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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.

package/.llm/components/featuretabs.md

@@ -0,0 +1,369 @@
+<!-- GENERATED from feature-tabs.contract.json. Do not edit. -->
+
+# FeatureTabs
+
+A section that shows one version of something at a time behind tabs — a heading, a strip of tabs, and the content of the one selected.
+
+## Why it is built this way
+
+Some sections show several versions of one thing that a reader takes one at a time: a product's trade types, a platform on each device, the accounts on offer. This is that section — the reference design's OptionsTypes, made general.
+
+The section owns what every version shares: the heading, the tab strip and which tab is showing, the footnote and the ground. What each tab shows is composed by the page — usually a Grid of plain Cards, each a flush CardBody with its picture above a title, a line and a Link — one child per name in `labels`, so a tab can hold whatever its version needs without a component for each shape. Only the tab showing is in the page, so a video or an animation in another is not playing behind it.
+
+## Use when
+
+- Several versions of one thing a reader takes one at a time — a product's trade types, a platform's apps, the account types
+- A section whose versions each need a picture, a line and a way onward, and only one is worth showing at once
+
+## Do not use
+
+- One claim and one picture, with nothing to list → `FeatureSplit`
+- Two or three plans or account types compared feature by feature → `ComparisonCards`
+- Showing the same section's content for a monthly or a yearly price → `TabList`
+- Content a reader needs all of. Only one tab is on the page at a time, and most readers never open the others
+- Small print the reader must see. The footnote is the last thing read
+- More than six tabs. A strip longer than that scrolls, and a reader stops reading it
+
+## Anatomy
+
+FeatureTabs renders 8 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-featuretabs`. The section, a region named by its heading, on the ground `ground` paints with the ink that goes with it.
+- `inner` — `<div>`, class `dds-featuretabs__inner`. The measure and the gutter, the same column every band holds its content in, and the step from the heading to the tabs' content: space.heading.content.
+- `header` — `<div>`, class `dds-featuretabs__header`. The heading, the line under it and the tabs. At the start on a phone, as every block's heading is there; centred over the content they choose from 48rem.
+- `title` — `<h2>`, class `dds-featuretabs__title`. What the versions are of — "Types of digital options", "Our platforms". `h2` because the section sits under the page's own heading; what each tab shows takes its headings from `h3`.
+- `description` — `<p>`, class `dds-featuretabs__description`. The line under the heading, at font.body.md. Rendered only when `description` is set.
+- `tabs` — `<div>`, class `dds-featuretabs__tabs`. The TabList of `labels`, named after the section's heading. Empty when there is one tab, since a strip of one tab chooses nothing.
+- `panel` — `<div>`, class `dds-featuretabs__panel`. The child for the selected tab, as the page composed it. The others are out of the page rather than hidden in it, so a picture playing in one stops when the reader turns to the next.
+- `footnote` — `<p>`, class `dds-featuretabs__footnote`. Small print every tab shares, in the muted ink — "Trade types may vary by platform and device.". At the start on a phone, centred from 48rem with the heading. Rendered only when `footnote` is set.
+
+Apply these classes from the generated `featureTabsParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: any content
+- Never contains: `FeatureTabs`, `TabList`, `LandingHero`, `ProductHero`, `PageHeader`, `Footer`, `Navbar` — in children or in any prop that takes a node
+- Holds at least 1
+
+## 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 — and the ground a reader is already on
+- `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's slate FAQ. 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. 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 tab strip turns round with it: white names, a rule in the band's own veil and a focus ring drawn for the dark, fixed like the band
+
+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. Two in a row is a deliberate pair rather than an accident, and 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, which is what the painted-ground-carries-its-ink rule exists to stop a page getting wrong.
+Never for: Marking importance. Every section on a page painted a ground is a page with no emphasis left.
+
+### title — `string` **Required.**
+
+Use when: Always. What the versions are of, in a few words — "Types of digital options". It names the section and the tabs
+Never for: A sentence. The line under it says more
+
+### description — `string`
+
+Use when: A line under the heading saying what the tabs have in common
+Never for: Describing one tab. Each says that in its own description
+
+### labels — `data` `string[]` **Required.**
+
+Use when: Always. The tabs' names, in a word or two each, in the order of the children they choose between — the first names the first child. A name without a child is not drawn
+Never for: Sentences. A tab is read at a glance; what it shows says the rest
+
+### footnote — `string`
+
+Use when: Small print every tab shares — that what is offered varies by platform or device
+Never for: A risk warning. Small print is the last thing a reader reads, and the one place a warning must never be
+
+## 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 through the tabs, then into the content showing
+- the section is a region named by its heading
+- with two or more tabs, they are a TabList named by the section's heading, and the content showing is the child the selected tab names
+
+## 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 page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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
+
+❌ FeatureTabs for: One claim and one picture, with nothing to list
+   FeatureSplit is one point beside one picture; this is versions and where each leads
+   → use `FeatureSplit` instead.
+
+❌ FeatureTabs for: Two or three plans or account types compared feature by feature
+   A comparison sets the versions side by side; this shows them one at a time
+   → use `ComparisonCards` instead.
+
+❌ FeatureTabs for: Showing the same section's content for a monthly or a yearly price
+   A TabList over the page's own content switches what the page shows; this is a section of its own
+   → use `TabList` instead.
+
+## Example
+
+```tsx
+import { FeatureTabs, Grid, Card, CardBody, Link } from '@deriv-com/dds-marketing'
+
+<FeatureTabs title="Explore what you can do" description="Three ways to get started, each with everything you need." labels={["Plan","Build","Review"]} footnote="Features may vary by region and device.">
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Set your goals" description="Decide what you want to reach and by when." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/goals" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Compare your options" description="See what each choice could mean before you commit." src="/sample-stop-teal.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/options" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Know your limits" description="Set the amount you are comfortable with from the start." src="/sample-stop-purple.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/limits" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Start small" description="Try your plan with a little before you go further." src="/sample-stop-amber.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/start" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Watch it work" description="Tools that show you what is happening as you go." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/watch" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Adjust as you go" description="Change course whenever the picture changes." src="/sample-stop-teal.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/adjust" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Look back" description="See what worked and what did not." src="/sample-stop-purple.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/history" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Spot patterns" description="Find what your best results have in common." src="/sample-stop-amber.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/patterns" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Plan the next step" description="Take what you learned into your next plan." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/next" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+</FeatureTabs>
+```
+
+## In use
+
+### Grounds
+
+The section on each of the page's three grounds.
+
+```tsx
+import { Card, CardBody, FeatureTabs, Grid, Link } from '@deriv-com/dds-marketing'
+
+// Page
+<FeatureTabs title="Explore what you can do" ground="page" labels={["Plan","Build","Review"]}>
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Set your goals" description="Decide what you want to reach and by when." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/goals" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Compare your options" description="See what each choice could mean before you commit." src="/sample-stop-teal.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/options" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Know your limits" description="Set the amount you are comfortable with from the start." src="/sample-stop-purple.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/limits" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Start small" description="Try your plan with a little before you go further." src="/sample-stop-amber.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/start" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Watch it work" description="Tools that show you what is happening as you go." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/watch" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Adjust as you go" description="Change course whenever the picture changes." src="/sample-stop-teal.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/adjust" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Look back" description="See what worked and what did not." src="/sample-stop-purple.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/history" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Spot patterns" description="Find what your best results have in common." src="/sample-stop-amber.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/patterns" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Plan the next step" description="Take what you learned into your next plan." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/next" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+</FeatureTabs>
+
+// Subtle
+<FeatureTabs title="Explore what you can do" ground="subtle" labels={["Plan","Build","Review"]}>
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Set your goals" description="Decide what you want to reach and by when." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/goals" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Compare your options" description="See what each choice could mean before you commit." src="/sample-stop-teal.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/options" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Know your limits" description="Set the amount you are comfortable with from the start." src="/sample-stop-purple.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/limits" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Start small" description="Try your plan with a little before you go further." src="/sample-stop-amber.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/start" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Watch it work" description="Tools that show you what is happening as you go." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/watch" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Adjust as you go" description="Change course whenever the picture changes." src="/sample-stop-teal.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/adjust" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Look back" description="See what worked and what did not." src="/sample-stop-purple.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/history" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Spot patterns" description="Find what your best results have in common." src="/sample-stop-amber.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/patterns" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Plan the next step" description="Take what you learned into your next plan." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/next" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+</FeatureTabs>
+
+// Strong
+<FeatureTabs title="Explore what you can do" ground="strong" labels={["Plan","Build","Review"]} footnote="Features may vary by region and device.">
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Set your goals" description="Decide what you want to reach and by when." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/goals" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Compare your options" description="See what each choice could mean before you commit." src="/sample-stop-teal.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/options" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Know your limits" description="Set the amount you are comfortable with from the start." src="/sample-stop-purple.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/limits" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Start small" description="Try your plan with a little before you go further." src="/sample-stop-amber.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/start" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Watch it work" description="Tools that show you what is happening as you go." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/watch" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Adjust as you go" description="Change course whenever the picture changes." src="/sample-stop-teal.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/build/adjust" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Look back" description="See what worked and what did not." src="/sample-stop-purple.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/history" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Spot patterns" description="Find what your best results have in common." src="/sample-stop-amber.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/patterns" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Plan the next step" description="Take what you learned into your next plan." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/review/next" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+</FeatureTabs>
+```
+
+### One tab
+
+One version on its own: no strip, just the content.
+
+```tsx
+import { Card, CardBody, FeatureTabs, Grid, Link } from '@deriv-com/dds-marketing'
+
+// Lone tab
+<FeatureTabs title="All in one place" labels={["Overview"]}>
+  <Grid columns="3" gap="gutter">
+    <Card variant="plain">
+      <CardBody title="Set your goals" description="Decide what you want to reach and by when." src="/sample-stop-blue.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/goals" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Compare your options" description="See what each choice could mean before you commit." src="/sample-stop-teal.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/options" tone="inherit">Learn more</Link>} />
+    </Card>
+    <Card variant="plain">
+      <CardBody title="Know your limits" description="Set the amount you are comfortable with from the start." src="/sample-stop-purple.svg" alt="" mediaPosition="above" flush aspect={1.5} link={<Link href="/plan/limits" tone="inherit">Learn more</Link>} />
+    </Card>
+  </Grid>
+</FeatureTabs>
+```

package/.llm/components/filterchip.md

@@ -146,6 +146,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   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 page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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.