@deriv-com/dds-marketing 1.0.2 → 1.1.1

package/.llm/components/featurecardscarousel.md

@@ -0,0 +1,311 @@
+<!-- GENERATED from feature-cards-carousel.contract.json. Do not edit. -->
+
+# FeatureCardsCarousel
+
+A feature band that sets its cards in a row a reader moves along rather than a grid: a heading and a line over a row of the page's own cards, the next one's edge showing past the last in view, with dots saying where the reader is and two arrows stepping it a card at a time. One card is the focus at a time and the rest wait at the edge, so each gets a screen's attention without the page paying a screen of scrolling for it.
+
+The reference design's FeatureCardsCarousel. Each card is the page's own Card or CardButton with a CardBody inside, as in FeatureCards — its fill, its picture, its words and where it leads are the card's; this decides the heading, the row and the way along it, and nothing about a card.
+
+## Use when
+
+- A "what you get" band of five or six authored cards, each a benefit with a line and a picture, too many for one row of a grid, where one card in focus with a peek of the next is the point. Three or four cards are FeatureCards, which shows the whole set at once
+- A platform or product page whose feature cards are too many for one row of a grid and too equal to be a sequence
+
+## Do not use
+
+- Three or four cards — the set a grid shows in one row → `FeatureCards`
+- The cards are read in order, one leading to the next → `FeatureScroll`
+- Two or three promotions on the brand's coral, one at a time → `CtaBannerSlider`
+- Live prices, market data or anything on a feed. A card is authored copy that holds still while a reader reads it
+- A static set flattened into a carousel to save height. Fewer than three cards is a FeatureCards grid; a carousel of two is a grid with a hidden half
+- Reviews or quotes. A rated review is TestimonialRow's and a chosen quote TestimonialSlider's, each with the attribution this does not draw
+
+## Anatomy
+
+FeatureCardsCarousel renders 11 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-featurecardscarousel`. The section. It paints the ground and the ink to go with it — see `ground` — and asks its own width, which the row's breakout and a card's width are measured against. A region named by its heading.
+- `inner` — `<div>`, class `dds-featurecardscarousel__inner`. The measure and the gutter, the same column every band holds its content in, and the step from the heading to the row: space.heading.content.
+- `header` — `<div>`, class `dds-featurecardscarousel__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-featurecardscarousel__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.
+- `description` — `<p>`, class `dds-featurecardscarousel__description`. The line under the heading, at the description measure. Rendered only when `description` is set.
+- `carousel` — `<div>`, class `dds-featurecardscarousel__carousel`. The row and the footer under it, held together at space.gap.xl — closer than the section's own step from the heading, so the controls read as belonging to the row.
+- `track` — `<div>`, class `dds-featurecardscarousel__track`. The row: the cards side by side at space.grid.gutter, scrolling across with a stop at each card. It runs out to the band's edges while its first card lines up with the heading — a gutter on the row itself that scrolls away with it, so a card is cut off by the band rather than by the column. A named group with a tab stop of its own, Scroller's rule, so a keyboard can reach the cards a pointer scrolls to. No scrollbar: the dots and arrows under it are the standing sign that it moves.
+- `item` — `<div>`, class `dds-featurecardscarousel__item`. One place in the row, holding one card. Most of the column on a phone — 85% — so the next card's edge shows past it; size.feature-cards-carousel.card from the fold, held to the column, so the row shows the next card's edge at full width. A grid of its own so the card stretches to it and every card is as tall as the tallest. On a painted ground it is also where a card is re-coloured for it, as in FeatureCards — see `ground`.
+- `footer` — `<div>`, class `dds-featurecardscarousel__footer`. The way along the row, back in the column under it: the dots at the start and the arrows at the end, the reference design's arrangement at every width. Drawn only for two cards or more, and hidden while the row holds every card and has nowhere to go.
+- `nav` — `<div>`, class `dds-featurecardscarousel__nav`. Two ButtonIcons in their secondary variant, stepping the row back and on by one stop. On the dark band they take the inverse tone, which keeps the tint and turns it white. Set at the end of the footer, after the dots.
+- `nav-slot` — `<span>`, class `dds-featurecardscarousel__nav-slot`. Where one arrow stands. At either end of the row the arrow that has nowhere to go stays in its slot, receded to opacity.disabled and inert — so both directions show from the first render, the pair keeps its width and does not shift as the reader scrolls, and a keyboard never lands on a control that does nothing. ButtonIcon has no disabled state, by its own ruling, which is why this is its slot's job.
+
+Apply these classes from the generated `featureCardsCarouselParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `Card`, `CardButton`
+- Never contains: `FeatureCards`, `FeatureCardsCarousel`, `LandingHero`, `ProductHero`, `PageHeader`, `Footer`, `Navbar` — in children or in any prop that takes a node
+- Holds at least 1 and at most 8
+
+## 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 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.
+- `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.
+
+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 dark is a page with no emphasis left, and a reader stops reading the grounds as meaning anything. Alternating for its own sake is the same mistake more slowly.
+
+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.
+
+### title — `string` **Required.**
+
+Use when: Always. What the cards are, in the fewest words that name them — "What you get", "Built for every trader".
+Never for: A sentence. The line under it is for the sentence.
+
+### description — `string`
+
+Use when: A line saying what the set has in common, when the title alone does not.
+Never for: A paragraph, or a summary of every card. The cards say what they are; this only says why they are together.
+
+### autoplay — `boolean` (default `false`)
+
+Use when: Whether the row moves on to the next stop on its own, holding each for motion.duration.dwell and returning to the start after the last. Off by default, so a row nobody configured stays still. On, it holds while the pointer is over the band or focus is inside it, never moves for a reader who asked for less motion, and stops for good once the reader presses anything in it — a card, an arrow, a dot — or swipes the row: the WAI carousel pattern's rule that a reader who has touched it is reading, not watching. That gives a reader a way to stop it, which WCAG 2.2.2 asks for, but not a visible one, as in CtaBannerSlider: a page that needs 2.2.2 met plainly should leave it off.
+Never for: A row whose cards carry more than a reader takes in during motion.duration.dwell. Several cards are in view at once, so a moving row is moving cards out from under a reader who may be reading the second one.
+
+### label — `string` (default `Features`)
+
+Use when: The name the row is announced by. The row is a scrolling region a keyboard has to be able to reach, so it carries a tab stop and a name of its own — Scroller's rule, as in TestimonialRow. Its own name rather than the section's, so a screen reader moving into it hears what it is. Translate it with the page.
+
+### previousLabel — `string` (default `Previous cards`)
+
+Use when: The accessible name of the arrow stepping the row back. A glyph announces nothing, so this is the whole of the control's name. Translate it with the page, and keep it parallel to nextLabel.
+
+### nextLabel — `string` (default `Next cards`)
+
+Use when: The accessible name of the arrow stepping the row on, for the reason previousLabel exists.
+
+### controlsLabel — `string` (default `Positions`)
+
+Use when: The name the dots are announced by, as a group inside the band. Its own name rather than the row's, so a screen reader moving into the dots hears what they are. Translate it with the page, like label.
+
+### stopLabel — `string` (default `Position`)
+
+Use when: The word each dot is announced by, before its number — "Position 2". A dot is a place the row stops, not a card: at full width the last few cards share the last stop, so there are fewer dots than cards. Translate it with the page, as controlsLabel is.
+
+## 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 row, then through the cards a reader can press, then to the dots and the arrows that have somewhere to go.
+- `Enter` — On a card that links, follows it. On a dot, moves the row to that stop; on an arrow, steps it by one.
+- `ArrowLeft` — On the focused row: scrolls it the way the key points — the browser's own scrolling, made reachable by the row's tab stop.
+- `ArrowRight` — On the focused row: scrolls it the way the key points, the mirror of ArrowLeft.
+- accessible name from title, so the section is a named region a reader can jump to and skip
+- The row is a named group with a tab stop of its own, so a keyboard can reach and scroll it whether or not any card links.
+- The cards' order in the markup is their order along the row, so a reader tabbing through meets them as a sighted reader scrolls to them.
+- An arrow with nowhere to go is drawn receded and inert rather than left a control that does nothing.
+- Under autoplay, a hold while the pointer is over the band 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 the row.
+
+## 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
+
+❌ FeatureCardsCarousel for: Three or four cards — the set a grid shows in one row
+   A grid shows the whole set at once; a row hides most of it behind a swipe, which is a cost a set that small does not need to pay
+   → use `FeatureCards` instead.
+
+❌ FeatureCardsCarousel for: The cards are read in order, one leading to the next
+   A sequence wants a screen per stop with its picture pinned beside it; a row lets the reader jump in anywhere
+   → use `FeatureScroll` instead.
+
+❌ FeatureCardsCarousel for: Two or three promotions on the brand's coral, one at a time
+   A promotion is a headline and an action on a full-bleed band, not a card in a row
+   → use `CtaBannerSlider` instead.
+
+## Example
+
+```tsx
+import { FeatureCardsCarousel, Card, CardBody } from '@deriv-com/dds-marketing'
+
+<FeatureCardsCarousel title="What you get" description="Everything you need to trade crypto in one place — the assets, the tools and the transfers you expect from a broker.">
+  <Card variant="accent">
+    <CardBody title="Top cryptos, ready to trade" description="Buy, hold and sell the assets that move the market — BTC, ETH, SOL and more, paired with USDT or USDC." src="/sample-card-image.svg" alt="" />
+  </Card>
+  <Card variant="accent-strong">
+    <CardBody title="Full exchange, whenever you're ready" description="Start with one-tap buys. When you want more, there are charts, a live order book and limit orders." src="/sample-card-image.svg" alt="" />
+  </Card>
+  <Card variant="accent-strong">
+    <CardBody title="Long or short, your call" description="Trade perpetual futures on 12 major pairs, with take profit and stop loss set when you open." src="/sample-card-image.svg" alt="" overMedia />
+  </Card>
+  <Card variant="surface-light">
+    <CardBody title="Send and receive crypto" description="Deposits are free and Deriv charges no withdrawal fees. You only pay the network charge." src="/sample-card-image.svg" alt="" />
+  </Card>
+  <Card variant="accent-strong">
+    <CardBody title="Crypto, plus everything else" description="Trade crypto alongside the CFDs, options and forex Deriv is known for. One login, nothing to juggle." src="/sample-card-image.svg" alt="" />
+  </Card>
+</FeatureCardsCarousel>
+```
+
+## In use
+
+Most rows below hold the same set, written once here:
+
+```tsx
+import { Card, CardBody } from '@deriv-com/dds-marketing'
+
+const cards = (
+  <>
+    <Card variant="accent">
+  <CardBody title="Top cryptos, ready to trade" description="Buy, hold and sell the assets that move the market — BTC, ETH, SOL and more, paired with USDT or USDC." src="/sample-card-image.svg" alt="" />
+</Card>
+    <Card variant="accent-strong">
+  <CardBody title="Full exchange, whenever you're ready" description="Start with one-tap buys. When you want more, there are charts, a live order book and limit orders." src="/sample-card-image.svg" alt="" />
+</Card>
+    <Card variant="accent-strong">
+  <CardBody title="Long or short, your call" description="Trade perpetual futures on 12 major pairs, with take profit and stop loss set when you open." src="/sample-card-image.svg" alt="" overMedia />
+</Card>
+    <Card variant="surface-light">
+  <CardBody title="Send and receive crypto" description="Deposits are free and Deriv charges no withdrawal fees. You only pay the network charge." src="/sample-card-image.svg" alt="" />
+</Card>
+    <Card variant="accent-strong">
+  <CardBody title="Crypto, plus everything else" description="Trade crypto alongside the CFDs, options and forex Deriv is known for. One login, nothing to juggle." src="/sample-card-image.svg" alt="" />
+</Card>
+  </>
+)
+```
+
+### Five cards, one in focus
+
+The reference design's band: coral, dark and light cards, the next one's edge past the last in view. The third lays its words over its picture, CardBody's overMedia.
+
+```tsx
+import { FeatureCardsCarousel } from '@deriv-com/dds-marketing'
+
+// Five cards, one over its picture
+<FeatureCardsCarousel title="What you get" description="Everything you need to trade crypto in one place — the assets, the tools and the transfers you expect from a broker.">{cards}</FeatureCardsCarousel>
+```
+
+### Cards that lead somewhere
+
+A card with a way on carries it as CardBody's link — inherit ink on the coloured cards, so it reads on coral and on dark.
+
+```tsx
+import { Card, CardBody, FeatureCardsCarousel, Link } from '@deriv-com/dds-marketing'
+
+// Each card with a link
+<FeatureCardsCarousel title="Built for every trader">
+  <Card variant="accent-strong">
+    <CardBody title="Trade on any device" description="Desktop, web and mobile, all from one account." src="/sample-card-image.svg" alt="" link={<Link href="/platforms" tone="inherit">Learn more</Link>} />
+  </Card>
+  <Card variant="surface-light">
+    <CardBody title="250+ markets" description="Forex, stocks, commodities and more, side by side." src="/sample-card-image.svg" alt="" link={<Link href="/markets">Learn more</Link>} />
+  </Card>
+  <Card variant="accent">
+    <CardBody title="Start in minutes" description="Open an account with as little as $5." src="/sample-card-image.svg" alt="" link={<Link href="/signup" tone="inherit">Learn more</Link>} />
+  </Card>
+  <Card variant="accent-strong">
+    <CardBody title="Copy the best" description="Follow traders whose results you can see, and stop whenever you like." src="/sample-card-image.svg" alt="" link={<Link href="/copy-trading" tone="inherit">Learn more</Link>} />
+  </Card>
+</FeatureCardsCarousel>
+```
+
+### On the grey band and the dark one
+
+The same cards on the other two grounds. The light card turns white on the grey band; on the dark band the dots take the band's ink and the arrows turn white.
+
+```tsx
+import { FeatureCardsCarousel } from '@deriv-com/dds-marketing'
+
+// ground="subtle"
+<FeatureCardsCarousel title="What you get" description="Everything you need to trade crypto in one place — the assets, the tools and the transfers you expect from a broker." ground="subtle">{cards}</FeatureCardsCarousel>
+
+// ground="strong"
+<FeatureCardsCarousel title="What you get" description="Everything you need to trade crypto in one place — the assets, the tools and the transfers you expect from a broker." ground="strong">{cards}</FeatureCardsCarousel>
+```
+
+### Moving on its own
+
+autoplay steps the row a stop at a time and returns to the start after the last. It holds under the pointer or focus, never moves for a reader who asked for less motion, and stops for good on a press.
+
+```tsx
+import { FeatureCardsCarousel } from '@deriv-com/dds-marketing'
+
+// autoplay
+<FeatureCardsCarousel title="What you get" description="Everything you need to trade crypto in one place — the assets, the tools and the transfers you expect from a broker." autoplay>{cards}</FeatureCardsCarousel>
+```

package/.llm/components/featuresplit.md

@@ -19,6 +19,7 @@ It sits on the page's own ground by default; `ground` paints the grey or the dar
 - The point is several things the reader gets, each one line long → `FeatureBullets`
 - There are three or four points and each needs its own picture → `FeatureCards`
 - The section opens the page → `ProductHero`
+- The picture is the section's weight, wide or tall enough to stand under the words rather than beside them → `FeatureStack`
 - A list. Two sentences separated by a full stop is not a list, and a reader scanning for several things will miss the second — that is what FeatureBullets is for
 - The page's opening or closing band. This is a section in the middle of a page and carries no navigation of its own
 - A call to action. The way onward here is a link to somewhere that says more, not the thing the page wants a reader to do
@@ -190,6 +191,10 @@ Two things genuinely have no logical form and are not covered by this. A CSS gra
    A page's opening band is a claim, not a supporting point
    → use `ProductHero` instead.
 
+❌ FeatureSplit for: The picture is the section's weight, wide or tall enough to stand under the words rather than beside them
+   The same feature stacked: the words centred over a large picture that stands on the band's edge, where a split would hold the picture to half the width
+   → use `FeatureStack` instead.
+
 ## Example
 
 ```tsx

package/.llm/components/featurestack.md

@@ -0,0 +1,227 @@
+<!-- GENERATED from feature-stack.contract.json. Do not edit. -->
+
+# FeatureStack
+
+A section that leads with a statement and ends on a picture: a heading, a line under it where the heading needs one, a link on to more where the page has one, and a large illustration — a globe, a map, a product shot — standing on the band's foot. FeatureSplit stacked: where a split sets the words beside the picture, this sets them over it. From the fold the words are centred over the picture; on a phone they start at the edge and the picture takes the column.
+
+The reference design's PartnersPayout layout, taken down to its frame. The figures the reference drew between the heading and the picture are the page's content and not the block's: a page that wants figures puts them in its own section, or in the copy.
+
+## Use when
+
+- A statement with a picture that carries it — a global reach shown on a globe, a platform shown on a device — where the picture is the section's weight and the words introduce it
+- Closing a page or a stretch of one on an image, with a way on for the reader who wants more
+
+## Do not use
+
+- The picture belongs beside the words, the two read side by side → `FeatureSplit`
+- The section is a set of figures read as a set → `Stats`
+- The section asks the reader to do one thing, now → `CtaBanner`
+- A picture with words in it. The words are the heading and the line; a picture saying them again cannot be read by a screen reader, translated or selected
+- A photograph a reader needs to see whole. The picture stands on the band's foot at its own proportions up to size.feature-stack.media, and is a scene rather than a document
+
+## Anatomy
+
+FeatureStack renders 8 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-featurestack`. 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. A region named by its heading.
+- `inner` — `<div>`, class `dds-featurestack__inner`. The measure and the gutter, the same column every band holds its content in. The step from the words to the picture is space.heading.content.
+- `header` — `<div>`, class `dds-featurestack__header`. The heading, the line under it and the link, FeatureCards' header and its arrangement: ranged to the start on a phone and centred from the fold, over the picture.
+- `title` — `<h2>`, class `dds-featurestack__title`. The statement. `h2` because a section sits under the page's own heading.
+- `description` — `<p>`, class `dds-featurestack__description`. The line under the heading — the period, or the unit — at the description measure. Rendered only when `description` is set.
+- `link` — `<div>`, class `dds-featurestack__link`. The way on, a standalone Link under the line, at space.heading.description-actions. Starts at the edge on a phone and is centred from the fold, with the words. Rendered only when `link` is set.
+- `media` — `<div>`, class `dds-featurestack__media`. The picture, centred, standing on the section's foot — it reaches down through the section's bottom padding so the band ends on it, the reference design's globe. What arrives last.
+  
+  It takes the picture's own shape. The picture shows at its own proportions — square, landscape or portrait as the page made it — and the frame wraps it, as wide as that shape allows up to the column and size.feature-stack.media. What the screen decides is only how tall it may grow: on a phone no taller than aspect.portrait of the column's width, from the fold no taller than aspect.landscape of its widest. A picture taller than that is drawn smaller, never cropped. Its top corners are rounded at radius.container, the corner the package's large cards take, and clip what it holds; its bottom corners stay square, where the picture meets the band's edge.
+- `image` — `<img>`, class `dds-featurestack__image`. The picture, drawn from `image` at its own proportions: as wide as its shape allows up to the frame, and no taller than the screen's limit. Lazily loaded, since it is the last thing in the section.
+
+Apply these classes from the generated `featureStackParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `FeatureStack`, `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
+- `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, and the reference design's ground for this layout. The heading and the line under it turn white; an illustration made for a dark ground sits best here
+
+Use when: Which of the page's three grounds this section paints, FeatureCards' axis and its reason: the page builds its rhythm from these, and the ink follows the ground in the same value. The cards follow it too — each ground takes the page's own Card in the variant made for it.
+Never for: Marking importance. Every section on a page painted a ground is a page with no emphasis left. And never the coral `color.bg.brand`, which belongs to the band that asks a reader to act.
+
+### title — `string` **Required.**
+
+Use when: Always. The statement the section makes, in a few words — "Trusted in 190+ countries", "One account, every device".
+Never for: A sentence of explanation. That is the line under it.
+
+### description — `string`
+
+Use when: A short line under the heading that says what the statement means for the reader, or what the picture shows.
+Never for: A paragraph. One line or two; anything longer is the page's own copy.
+
+### link — `node`
+
+Accepts: Link
+Use when: A way on for the reader who wants more — "Learn more", "See where we operate". A standalone Link, under the line, the way FeatureCards takes one.
+Never for: A button. The section is a statement and a picture; a Button would make it a banner, and CtaBanner is that.
+
+### image — `data` `BlockImage` **Required.**
+
+Use when: Always. The picture the section ends on — a globe, a map, a product shot — which the block draws at its own proportions: a square picture stays square, a tall one stays tall, held to the screen's limit. Use one at least as wide as the column, twice that for sharp screens, and give its width and height so the block reserves its shape before it loads. `alt` empty when the heading already says what it shows; otherwise describe it.
+Never for: Artwork with words in it, or a chart. What a reader has to read belongs in the heading and the line, where a screen reader and a translation reach it.
+
+## 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, where there is one, and on past the section. Nothing else in it is operable, unless the page puts something operable in the illustration.
+- accessible name from title, so the section is a named region a screen reader can jump to and skip
+- An illustration that only illustrates is marked decorative; one that carries meaning the heading does not is described.
+
+## 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
+
+❌ FeatureStack for: The picture belongs beside the words, the two read side by side
+   FeatureSplit is the same feature read across, the words beside the picture; this is it stacked, the words over a picture that stands on the band's edge
+   → use `FeatureSplit` instead.
+
+❌ FeatureStack for: The section is a set of figures read as a set
+   Figures are the content there; here the picture is, and figures under the heading would be the page's own composition rather than this block's
+   → use `Stats` instead.
+
+❌ FeatureStack for: The section asks the reader to do one thing, now
+   A banner is built around its action; this section's link is a way on, not the point of it
+   → use `CtaBanner` instead.
+
+## Example
+
+```tsx
+import { FeatureStack, Link } from '@deriv-com/dds-marketing'
+
+<FeatureStack title="Section title goes here" description="The line under the heading that says what the picture shows." link={<Link href="/">Learn more</Link>} image={{"src":"/sample-card-image.svg","alt":"","width":800,"height":600}} />
+```
+
+## In use
+
+### The picture keeps its shape
+
+A plain image shows at its own proportions; the screen only limits how tall it grows — portrait of the column on a phone, landscape from the fold.
+
+```tsx
+import { FeatureStack, Link } from '@deriv-com/dds-marketing'
+
+// A landscape picture
+<FeatureStack title="Section title goes here" description="The line under the heading that says what the picture shows." link={<Link href="/">Learn more</Link>} image={{"src":"/sample-card-image.svg","alt":"","width":800,"height":600}} />
+
+// A square picture
+<FeatureStack title="Section title goes here" description="The line under the heading that says what the picture shows." link={<Link href="/">Learn more</Link>} image={{"src":"/sample-aspect-art.svg","alt":"","width":1200,"height":1200}} />
+
+// A tall picture, held to the limit
+<FeatureStack title="Section title goes here" description="The line under the heading that says what the picture shows." link={<Link href="/">Learn more</Link>} image={{"src":"/sample-tall-image.svg","alt":"","width":600,"height":900}} />
+```
+
+### The ground it sits on
+
+The three grounds a section can take. The words take the ground's ink; the picture stands on the band's foot on each.
+
+```tsx
+import { FeatureStack, Link } from '@deriv-com/dds-marketing'
+
+// On the page itself
+<FeatureStack title="Section title goes here" description="The line under the heading that says what the picture shows." link={<Link href="/">Learn more</Link>} ground="page" image={{"src":"/sample-card-image.svg","alt":"","width":800,"height":600}} />
+
+// On the grey band
+<FeatureStack title="Section title goes here" description="The line under the heading that says what the picture shows." link={<Link href="/">Learn more</Link>} ground="subtle" image={{"src":"/sample-card-image.svg","alt":"","width":800,"height":600}} />
+
+// On the dark band
+<FeatureStack title="Section title goes here" description="The line under the heading that says what the picture shows." link={<Link href="/" tone="inherit">Learn more</Link>} ground="strong" image={{"src":"/sample-card-image.svg","alt":"","width":800,"height":600}} />
+```
+
+### Without a link
+
+The link is optional. Without one the words end on the line under the heading, and the picture follows.
+
+```tsx
+import { FeatureStack } from '@deriv-com/dds-marketing'
+
+// Heading, line and picture
+<FeatureStack title="Section title goes here" description="The line under the heading that says what the picture shows." image={{"src":"/sample-card-image.svg","alt":"","width":800,"height":600}} />
+```