@deriv-com/dds-marketing 1.0.2 → 1.1.1

package/.llm/components/downloadbanner.md

@@ -0,0 +1,283 @@
+<!-- GENERATED from download-banner.contract.json. Do not edit. -->
+
+# DownloadBanner
+
+A section promoting the app's downloads: a card holding a heading and the stores' own badges, each a link to the product in that store. From the fold a QR code sits beside the heading, with a line telling the reader to scan it, so a reader on a desktop can take the app to their phone; on a phone the code is gone — the reader is already holding the device it would open on — and the badges sit two to a row under the heading.
+
+The badges are the stores' own artwork, chosen from the platform each record names rather than drawn by the page, and each is named by the words it carries. The QR code is the page's image, never generated here.
+
+Two ways to draw the card: the standard one in the ground's fill, and the featured one — the brand's coral card with a Background pattern, the aurora or the mesh, inside it.
+
+## Use when
+
+- Promoting an app across the stores and platforms it ships on — App Store, Google Play, AppGallery, a desktop download, the web
+- A trading platform's page, near its end, once the product has been explained and the next thing a reader wants is to get it
+
+## Do not use
+
+- One download, or the web alone → `Button`
+- A promotion that has to argue for the download in a headline and a sentence → `CtaBanner`
+- Two download sections on one page — the second repeats the first's destinations and makes neither the place to go
+- A badge for a platform the product does not ship on, or a QR code that reaches somewhere other than the badges do
+
+## Anatomy
+
+DownloadBanner renders 17 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-downloadbanner`. The section. It paints the ground and the ink to go with it — see `ground` — and asks its own width, so the card folds on the section's measure rather than the window's. A region named by its heading.
+- `inner` — `<div>`, class `dds-downloadbanner__inner`. The measure and the gutter, the same column every band holds its content in.
+- `card` — `<div>`, class `dds-downloadbanner__card`. The card holding everything, its fill following the ground — see `ground`. The heading over the badges on a phone and from the fold; from 64rem the two side by side, the heading at the start and the badges at the end. The step between them is space.heading.content whichever way they sit: a heading and the content it introduces, turned on its side.
+- `lead` — `<div>`, class `dds-downloadbanner__lead`. The QR code and the words beside it, in a row. On a phone the code is not drawn and this is the words alone.
+- `qr-tile` — `<div>`, class `dds-downloadbanner__qr-tile`. The QR code's tile: a white square with a margin round the code, so it scans on the card. The standard card only; the featured card draws no code. Drawn from the fold and never on a phone, as the code is. Rendered only when `qr` is set.
+- `qr` — `<img>`, class `dds-downloadbanner__qr`. The QR code, square, filling its tile with its corners rounded. A code that is not square is cropped to the square rather than letterboxed in it. Rendered only when `qr` is set.
+- `text` — `<div>`, class `dds-downloadbanner__text`. The scan line, the heading and the small print, read down. It sets no gap: each part's own margin is the step, so a group without the scan line or the small print closes up rather than leaving its gap behind.
+- `qr-label` — `<p>`, class `dds-downloadbanner__qr-label`. The line telling the reader to scan the code, over the heading the way an eyebrow sits over a title. Shown with the code and gone with it, because on a phone there is nothing to scan. Rendered only when `qr` is set.
+- `eyebrow` — `<p>`, class `dds-downloadbanner__eyebrow`. The app's name, small above the heading on the featured card. Rendered only when `eyebrow` is set.
+- `title` — `<h2>`, class `dds-downloadbanner__title`. Where the app can be had. `h2` because a section sits under the page's own heading, drawn at font.h3 — a heading that labels the badges rather than a headline over the page.
+- `description` — `<p>`, class `dds-downloadbanner__description`. The line under the heading, at the body step and the description measure. Rendered only when `description` is set.
+- `disclaimer` — `<p>`, class `dds-downloadbanner__disclaimer`. The small print, under the heading in the quieter ink. Rendered only when `disclaimer` is set.
+- `badges` — `<ul>`, class `dds-downloadbanner__badges`. The badges, a list. Two to a row on a phone, each filling its column; from the fold a row that wraps, each badge its own width, ranged to the start and to the end once it sits beside the heading. The space between them is space.actions.gap — they are the section's actions. On a phone they are two to a row rather than stacked one to a row at full width, the one place this section departs from the rule that a section's actions stack on a phone: store badges are a set of equal chips read as one choice of store, and a column of seven full-width black bars would read as seven different actions — the reference design's phone grid.
+- `badge` — `<li>`, class `dds-downloadbanner__badge`. One badge's place in the list.
+- `badge-link` — `<a>`, class `dds-downloadbanner__badge-link`. The badge itself: a chip of one size for every store — size.download-banner.badge wide and size.control.lg tall, on color.bg.store-badge, the black the stores' own artwork is drawn on — with that artwork centred in it at whatever size fits. The artwork differs in shape from store to store, so at one height it came out at a different width for each, and a row of them was ragged; in a chip of one size, with a ground the same black as the artwork's own, every badge is the same size and the artwork is still the store's, untouched. Lifts and brightens a little under the pointer.
+- `mark` — `<svg>`, class `dds-downloadbanner__mark`. The store's own badge artwork, filling the chip and kept to its proportions — the SVG's own fit centres it, and its black ground meets the chip's.
+- `media` — `<div>`, class `dds-downloadbanner__media`. The app's image on the featured card: at the card's end from the fold, rising out of the card's top edge and resting on its bottom one; under the badges on a phone. The image is the page's, drawn at its own proportions and never wider than its column. Its top corners round at radius.container and it clips what it holds to them, so the app rises out of the card with the corners a picture standing on an edge has elsewhere — ProductHero's and FeatureStack's; its foot stays square, flush on the card's edge. Rendered only when `media` is set.
+
+Apply these classes from the generated `downloadBannerParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `DownloadBanner`, `CtaBanner`, `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. The card is the recessed gray that sets it off — the reference design's light-2
+- `subtle` — The grey band, with the card white on it — the reference design's light. 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, with the card at color.bg.surface-card-strong and white words on it — the reference design's dark. For a download section a reader should arrive at; the badges are black and keep their own edge on it
+
+Use when: Which of the page's grounds the section paints, and with it the card's fill: the recessed surface on the page, the raised white on the grey band, and the strong card on the dark band — TestimonialRow's three and the reference design's light, light-2 and dark. The ink follows the ground and is not a second decision.
+Never for: Marking importance. Every section on a page painted a ground is a page with no emphasis left.
+
+### variant — `standard` | `featured` (default `standard`)
+
+- `standard` — The default: the card in the ground's own fill, quiet beside the sections around it — the reference design's banner.
+- `featured` — The page promoting an app: the brand's coral card laid out as a split — the app's name, the heading, a line and the badges with the QR code beside them on one side, the app's own image on the other, rising out of the card's top edge — with a Background pattern inside it, the aurora unless `pattern` says otherwise. White words on it; the badges keep their own black and the code its white tile. Coral in both themes and on every ground. A known exception: the line under the heading and the small print are white on the coral at about 3.4:1, under the 4.5:1 body text asks for — the package's ground rule keeps the coral to a headline and an action. Recorded rather than recoloured, as CtaBanner's band is; keep the line short, or use the standard card where the copy has to be read.
+
+Use when: How much the banner asks for. The standard card sits with the page; the featured card is the page's moment for the app, and one per page.
+Never for: More than one featured banner on a page, or one beside another patterned band. The pattern is what makes the band the one a reader remembers.
+
+### pattern — `aurora` | `mesh`
+
+- `aurora` — Curtains of light rising from the card's foot, white and deep red on the coral, swaying slowly. The quieter of the two, and what a featured card draws when no pattern is named.
+- `mesh` — Soft pools of the brand's reds run together across the whole card — the design system's own front page. The richer of the two.
+
+Use when: Which pattern the featured card draws. Absent, the aurora.
+Never for: A standard card. It has no pattern to choose, and the type refuses one.
+
+### media — `node`
+
+Accepts: *
+Use when: The featured card only: the app itself — a screenshot of it in a phone, the page's own image. It stands at the card's end, rising out of the card's top edge and resting on its bottom one, so the card reads as the app being held out to the reader. On a phone it sits under the badges.
+Never for: A picture that is not the app. A banner promoting an app shows the app. On a standard card it is not drawn.
+
+### eyebrow — `string`
+
+Use when: The featured card only: the app's name, or what kind of app it is, small above the heading — "Deriv GO", "Mobile app".
+Never for: A second heading. The heading says what the reader gets; this names the app. On a standard card it is not drawn.
+
+### title — `string` **Required.**
+
+Use when: Always. Where the app can be had, in a few words — "Trade on the go", "Available on". The section's heading at every width: under the scan line beside the code from the fold, and alone over the badges on a phone.
+Never for: The instruction to scan. That is the QR code's `label`, and it goes with the code where the code goes.
+
+### description — `string`
+
+Use when: A line under the heading saying what the app gives a reader — "Trade on the go with the same account, markets and tools." One sentence.
+Never for: Small print. Versions and availability belong in the `disclaimer`.
+
+### badges — `data` `DownloadBannerBadge[]` **Required.**
+
+Use when: Always. The stores and downloads the app is in, in the order a reader should meet them — mobile stores first, then desktop, then the web. Each names its `platform`, which picks the store's own artwork, and the `href` that reaches the product in it. An empty list draws no badges.
+Never for: A platform the product does not ship on, or a badge whose link does not reach the product in that store.
+
+### qr — `data` `DownloadBannerQr`
+
+Use when: A QR code reaching the same app the badges do, so a reader at a desktop can take it to their phone. The page's image, with the words it is read as and the line telling the reader to scan it. Drawn from the fold and never on a phone, where the reader is already holding the device it would open on, and only on the standard card: the featured card promotes an app with its image, and the badges are its one way in. Leave it out and the heading stands alone at every width.
+Never for: A destination the badges do not reach. A code is the one link a reader cannot read before following it.
+
+### disclaimer — `string`
+
+Use when: One line of small print under the heading — which versions the desktop app runs on, or where the app is not offered.
+Never for: A sentence of promotion. Anything a reader is meant to be persuaded by is not small print.
+
+## 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 badges in the order they were handed in. Nothing in the section is a composite widget.
+- accessible name from title, so the section is a named region a screen reader can jump to and skip
+- Each badge is a link named by the words its artwork carries, or by the record's label, so what is heard and what a speech-input user says match what is seen. The artwork is hidden from assistive technology.
+- The QR code is an image named by the alt the page gives it, and never the only way to a destination: every place it reaches, a badge reaches too.
+
+## 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
+
+❌ DownloadBanner for: One download, or the web alone
+   A single destination is a Button. A row of one badge in a card is a section built for a choice the reader does not have.
+   → use `Button` instead.
+
+❌ DownloadBanner for: A promotion that has to argue for the download in a headline and a sentence
+   This has a heading, a line under it at most, and the badges. A message the reader has to be persuaded by is a CtaBanner, whose action can be the download.
+   → use `CtaBanner` instead.
+
+❌ variant=standard + pattern is set
+   A standard card draws no pattern, so a pattern named on it is a choice that does nothing. Make the card featured, or leave the pattern out.
+
+## Example
+
+```tsx
+import { DownloadBanner } from '@deriv-com/dds-marketing'
+
+<DownloadBanner title="Trade on the go" qr={{"src":"/sample-card-image.svg","alt":"QR code to download the Deriv app","label":"Scan to download the Deriv app"}} badges={[{"platform":"app-store","href":"https://apps.apple.com/app/deriv-go"},{"platform":"google-play","href":"https://play.google.com/store/apps/details?id=com.deriv.go"},{"platform":"app-gallery","href":"https://appgallery.huawei.com/app/deriv-go"},{"platform":"mac-app-store","href":"https://apps.apple.com/app/deriv-mt5"},{"platform":"windows-exe","href":"/downloads/deriv-mt5-setup.exe"},{"platform":"linux","href":"/downloads/deriv-mt5.deb"},{"platform":"web","href":"https://app.deriv.com"}]} description="The same account, markets and tools, on every device you trade from." />
+```
+
+## In use
+
+### Featured
+
+An app being promoted: its name, the heading and the badges under them, the app's image rising out of the coral card.
+
+```tsx
+import { AspectRatio, DownloadBanner } from '@deriv-com/dds-marketing'
+
+// On the page
+<DownloadBanner title="Trade on the go" badges={[{"platform":"app-store","href":"https://apps.apple.com/app/deriv-go"},{"platform":"google-play","href":"https://play.google.com/store/apps/details?id=com.deriv.go"},{"platform":"app-gallery","href":"https://appgallery.huawei.com/app/deriv-go"}]} description="The same account, markets and tools, on every device you trade from." variant="featured" pattern="aurora" eyebrow="Deriv GO" media={<AspectRatio ratio="portrait" />} />
+
+// On the grey band
+<DownloadBanner title="Trade on the go" badges={[{"platform":"app-store","href":"https://apps.apple.com/app/deriv-go"},{"platform":"google-play","href":"https://play.google.com/store/apps/details?id=com.deriv.go"},{"platform":"app-gallery","href":"https://appgallery.huawei.com/app/deriv-go"}]} description="The same account, markets and tools, on every device you trade from." variant="featured" ground="subtle" pattern="aurora" eyebrow="Deriv GO" media={<AspectRatio ratio="portrait" />} />
+
+// On the dark band
+<DownloadBanner title="Trade on the go" badges={[{"platform":"app-store","href":"https://apps.apple.com/app/deriv-go"},{"platform":"google-play","href":"https://play.google.com/store/apps/details?id=com.deriv.go"},{"platform":"app-gallery","href":"https://appgallery.huawei.com/app/deriv-go"}]} description="The same account, markets and tools, on every device you trade from." variant="featured" ground="strong" pattern="aurora" eyebrow="Deriv GO" media={<AspectRatio ratio="portrait" />} />
+```
+
+### Featured, with the mesh
+
+The same card with the mesh instead of the aurora: soft pools of the brand's reds run together across it — the front page's hero.
+
+```tsx
+import { AspectRatio, DownloadBanner } from '@deriv-com/dds-marketing'
+
+// pattern="mesh"
+<DownloadBanner title="Trade on the go" badges={[{"platform":"app-store","href":"https://apps.apple.com/app/deriv-go"},{"platform":"google-play","href":"https://play.google.com/store/apps/details?id=com.deriv.go"},{"platform":"app-gallery","href":"https://appgallery.huawei.com/app/deriv-go"}]} description="The same account, markets and tools, on every device you trade from." variant="featured" pattern="mesh" eyebrow="Deriv GO" media={<AspectRatio ratio="portrait" />} />
+
+// pattern="mesh" on the dark band
+<DownloadBanner title="Trade on the go" badges={[{"platform":"app-store","href":"https://apps.apple.com/app/deriv-go"},{"platform":"google-play","href":"https://play.google.com/store/apps/details?id=com.deriv.go"},{"platform":"app-gallery","href":"https://appgallery.huawei.com/app/deriv-go"}]} description="The same account, markets and tools, on every device you trade from." variant="featured" pattern="mesh" ground="strong" eyebrow="Deriv GO" media={<AspectRatio ratio="portrait" />} />
+```
+
+### Grounds
+
+The page's three grounds, and the card's fill on each. The badges are the stores' own black artwork and keep their edge on every one.
+
+```tsx
+import { DownloadBanner } from '@deriv-com/dds-marketing'
+
+// page — the recessed card on white
+<DownloadBanner ground="page" title="Trade on the go" qr={{"src":"/sample-card-image.svg","alt":"QR code to download the Deriv app","label":"Scan to download the Deriv app"}} badges={[{"platform":"app-store","href":"https://apps.apple.com/app/deriv-go"},{"platform":"google-play","href":"https://play.google.com/store/apps/details?id=com.deriv.go"},{"platform":"app-gallery","href":"https://appgallery.huawei.com/app/deriv-go"}]} />
+
+// subtle — a white card on the grey band
+<DownloadBanner ground="subtle" title="Trade on the go" qr={{"src":"/sample-card-image.svg","alt":"QR code to download the Deriv app","label":"Scan to download the Deriv app"}} badges={[{"platform":"app-store","href":"https://apps.apple.com/app/deriv-go"},{"platform":"google-play","href":"https://play.google.com/store/apps/details?id=com.deriv.go"},{"platform":"app-gallery","href":"https://appgallery.huawei.com/app/deriv-go"}]} />
+
+// strong — the dark band
+<DownloadBanner ground="strong" title="Trade on the go" qr={{"src":"/sample-card-image.svg","alt":"QR code to download the Deriv app","label":"Scan to download the Deriv app"}} badges={[{"platform":"app-store","href":"https://apps.apple.com/app/deriv-go"},{"platform":"google-play","href":"https://play.google.com/store/apps/details?id=com.deriv.go"},{"platform":"app-gallery","href":"https://appgallery.huawei.com/app/deriv-go"}]} />
+```
+
+### What a page offers
+
+Only the platforms the product ships on. Without a QR code the heading stands alone; small print says what a download needs.
+
+```tsx
+import { DownloadBanner } from '@deriv-com/dds-marketing'
+
+// Mobile stores, no QR code
+<DownloadBanner title="Available on" badges={[{"platform":"app-store","href":"https://apps.apple.com/app/deriv-go"},{"platform":"google-play","href":"https://play.google.com/store/apps/details?id=com.deriv.go"},{"platform":"app-gallery","href":"https://appgallery.huawei.com/app/deriv-go"}]} />
+
+// Desktop downloads, with small print
+<DownloadBanner title="Deriv MT5 on your desktop" qr={{"src":"/sample-card-image.svg","alt":"QR code to download Deriv MT5","label":"Scan to download"}} badges={[{"platform":"windows-exe","href":"/downloads/deriv-mt5-setup.exe"},{"platform":"macos-dmg","href":"/downloads/deriv-mt5.dmg"},{"platform":"linux","href":"/downloads/deriv-mt5.deb"}]} disclaimer="Runs on Windows 10 or later, macOS 11 or later, and Ubuntu 20.04 or later." />
+```

package/.llm/components/featurecards.md

@@ -10,7 +10,7 @@ One card is the reference design's single panel: it takes the whole row, and fro
 
 ## Use when
 
-- Three or four things a product does, each a heading and a sentence, read side by side and compared at a glance
+- Three or four things a product does, each a card with a heading, a line and a picture under them, read side by side and compared at a glance — the first choice for a set of three. The picture is CardBody's `src`, drawn below the words by default
 - A set of destinations — markets, platforms, tools — each a card a reader presses to go there
 - One feature that deserves the whole row in a card of its own — the words beside a large picture, carded on the section's ground
 
@@ -32,7 +32,7 @@ FeatureCards renders 8 elements. A token binding names the part it applies to.
 - `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.
 - `description` — `<p>`, class `dds-featurecards__description`. The line under the heading, at the description measure. Rendered only when `description` is set.
 - `link` — `<div>`, class `dds-featurecards__link`. The way on to the page the set belongs to. Rendered only when `link` is set.
-- `grid` — `<div>`, class `dds-featurecards__grid`. The cards. One column on a phone, two from the fold, three at full width, four when there are exactly four and two when there are exactly two — read from the children rather than asked of the page, because the count is already in the markup. Every card in a row is as tall as the tallest, which is what a grid row does and what lets their edges line up. The space between cards, across and down, is the page grid's own gutter, space.grid.gutter, at every width — the same measure every other grid on the page keeps. A single card takes the row on its own and lays its body out as a row from the fold. At full width one card or two hold to two thirds of the row, centred — two of the three columns — so a pair is as wide as a pair is in any set.
+- `grid` — `<div>`, class `dds-featurecards__grid`. The cards. One column on a phone, two from the fold, three at full width, four when there are exactly four and two when there are exactly two — read from the children rather than asked of the page, because the count is already in the markup. Every card in a row is as tall as the tallest, which is what a grid row does and what lets their edges line up. The space between cards, across and down, is the page grid's own gutter, space.grid.gutter, at every width — the same measure every other grid on the page keeps. A single card takes the row on its own and lays its body out as a row from the fold. At full width a single card holds to two thirds of the row, centred — two of the three columns — and a pair fills the row, half each, reaching the same edges as three or four.
 - `item` — `<div>`, class `dds-featurecards__item`. One cell of the grid, holding one card. The cell is what arrives — the card inside it is the page's own and keeps its own transitions, which an arrival set on the card would have overwritten. A grid of its own so the card stretches to the cell, and every card in a row is as tall as the tallest. On a painted ground it is also where a card is re-coloured for it — a light card white on the subtle band, a neutral card inverse on the strong one: see `ground`.
 
 Apply these classes from the generated `featureCardsParts` constant rather than writing the strings by hand.
@@ -237,7 +237,7 @@ import { Card, CardBody, FeatureCards, Link } from '@deriv-com/dds-marketing'
   </Card>
 </FeatureCards>
 
-// Two cards, two thirds of the row
+// Two cards, filling the row
 <FeatureCards title="Two ways to trade">
   <Card variant="accent-strong">
     <CardBody title="Trade on any device" description="Desktop, web and mobile, all from one account." link={<Link href="/platforms" tone="inherit">Learn more</Link>} src="/sample-card-image.svg" alt="" />
@@ -311,3 +311,41 @@ import { FeatureCards } from '@deriv-com/dds-marketing'
 // Strong ground, the same set
 <FeatureCards ground="strong" title="Why trade with Deriv">{cards}</FeatureCards>
 ```
+
+### Icon-led cards
+
+The reference's FeatureCardsIcon: every card a light Card whose CardBody leads with a mark rather than a picture. A mark on every card or on none.
+
+```tsx
+import { Card, CardBody, FeatureCards, Link } from '@deriv-com/dds-marketing'
+import { ClockThreeRegularIcon, FileShieldRegularIcon, GlobeRegularIcon, LockRegularIcon } from '@deriv-com/quill-icons-web'
+
+// Three cards, a mark on each
+<FeatureCards ground="subtle" title="Why choose Deriv" description="Trusted by traders since 1999, with the safeguards to show for it.">
+  <Card variant="surface-light">
+    <CardBody mark={<FileShieldRegularIcon />} title="Regulated and licensed" description="Licensed in several jurisdictions, audited every year." link={<Link href="/regulatory">Learn more</Link>} />
+  </Card>
+  <Card variant="surface-light">
+    <CardBody mark={<LockRegularIcon />} title="Your funds kept separate" description="Client money held apart from the company's own." link={<Link href="/security">Learn more</Link>} />
+  </Card>
+  <Card variant="surface-light">
+    <CardBody mark={<ClockThreeRegularIcon />} title="Support around the clock" description="Real people on chat, every day of the year." link={<Link href="/contact-us">Learn more</Link>} />
+  </Card>
+</FeatureCards>
+
+// Four cards, one row at full width
+<FeatureCards ground="subtle" title="Why choose Deriv" description="Trusted by traders since 1999, with the safeguards to show for it.">
+  <Card variant="surface-light">
+    <CardBody mark={<FileShieldRegularIcon />} title="Regulated and licensed" description="Licensed in several jurisdictions, audited every year." link={<Link href="/regulatory">Learn more</Link>} />
+  </Card>
+  <Card variant="surface-light">
+    <CardBody mark={<LockRegularIcon />} title="Your funds kept separate" description="Client money held apart from the company's own." link={<Link href="/security">Learn more</Link>} />
+  </Card>
+  <Card variant="surface-light">
+    <CardBody mark={<ClockThreeRegularIcon />} title="Support around the clock" description="Real people on chat, every day of the year." link={<Link href="/contact-us">Learn more</Link>} />
+  </Card>
+  <Card variant="surface-light">
+    <CardBody mark={<GlobeRegularIcon />} title="Trade from 190+ countries" description="One account, wherever you trade from." link={<Link href="/who-we-are">Learn more</Link>} />
+  </Card>
+</FeatureCards>
+```