@deriv-com/dds-marketing 0.2.0 → 1.0.0

package/.llm/components/featurecards.md

@@ -0,0 +1,313 @@
+<!-- GENERATED from feature-cards.contract.json. Do not edit. -->
+
+# FeatureCards
+
+A section that opens with a heading and sets a grid of cards under it — the shape a marketing page uses for “why choose us” and “what you get”. Each card is the page's own Card or CardButton with a CardBody inside; this decides the heading, the column and how many cards sit on a row, and nothing about a card.
+
+One column on a phone, two from the fold, and three at full width — four when there are exactly four and two when there are two, so a set is one full row rather than a row and an orphan, or a row with a gap in it.
+
+One card is the reference design's single panel: it takes the whole row, and from the fold its words and its picture sit side by side — words at the start, the picture at the end and held to aspect.portrait — rather than one above the other across a card three times wider than a card is meant to be.
+
+## Use when
+
+- Three or four things a product does, each a heading and a sentence, read side by side and compared at a glance
+- 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
+
+## Do not use
+
+- Each item is one line, and the list is the argument → `FeatureBullets`
+- One claim beside a picture, with no card around it → `FeatureSplit`
+- The items are read in order, one leading to the next → `FeatureScroll`
+- More than eight cards. Past two rows a grid stops being compared and starts being scanned, and that is a page of its own
+- The page's opening band. This sits under the page's heading, never in place of it
+
+## Anatomy
+
+FeatureCards renders 8 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-featurecards`. The section. It paints the ground and the ink to go with it — see `ground` — and asks its own width, so the grid folds on the section's measure rather than the window's.
+- `inner` — `<div>`, class `dds-featurecards__inner`. The measure and the gutter, the same column every band holds its content in, and the step from the heading to the grid: space.heading.content.
+- `header` — `<div>`, class `dds-featurecards__header`. The heading, the line under it and the way on. Ranged to the start on a phone and centred from the fold, PageHeader's rule and its reason. It sets no gap: each part's own margin is the step, so a header without a line closes up rather than leaving its gap behind.
+- `title` — `<h2>`, class `dds-featurecards__title`. What the cards are. `h2` because a section sits under the page's own heading; the cards' titles come below it in the outline.
+- `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.
+- `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.
+
+## Composition
+
+- Can contain: `Card`, `CardButton`
+- Never contains: `FeatureCards`, `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 — "Why trade with Deriv", "Markets you can trade".
+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.
+
+### link — `node`
+
+Accepts: Link
+Use when: A way on to the page the whole set belongs to — "See all markets". A standalone Link, under the line.
+Never for: A button. The cards are the actions here, and a Button over them would be a second, louder one.
+
+## 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 link and then the cards a reader can press, in reading order — row by row, start to end.
+- accessible name from title, so the section is a named region a screen reader can jump to and skip
+- The cards' order in the markup is their reading order. The grid places them in rows and never reorders them, so a reader tabbing through meets them as a sighted reader scans them.
+
+## Rules
+
+- **On a phone a section's actions stack and each fills the width, including when there is only one** — On a phone a page's actions stack, and each one fills the width. Not most of it, and not the width its label happens to need — the whole column.
+
+Two side by side is what this replaces. On the narrowest screen each gets half a column minus the gap, which is rarely enough for a real label: the words wrap inside the pills, the two buttons come out different heights, and the pair reads as a broken row rather than as a choice. Stacked, each has the whole width and neither has to shorten its words to fit.
+
+A single action fills too, and that is the part worth saying, because it is the one that looks unnecessary. A lone button has the room to sit at its natural width and still should not: a full-width control is the phone's convention for the thing the screen is asking you to do, and a pill hugging its label reads as one option among others that are not there. It also makes the target predictable — the whole width, wherever the thumb lands — which a centred pill does not.
+
+Filling is the row's job rather than the button's. A button has no width of its own and is not given one; the row it sits in becomes a column and stretches its children, so nothing about the control changes and the same button is full width here and its own size on a desktop.
+
+This is the phone's breakpoint, size.breakpoint.md, and not the wider one that decides whether a heading is centred. Those are different questions and they break at different widths: a heading stops being centred when the measure is the screen, while a button stops being full width much sooner than that — stretched across a tablet it is a long way from its own label, and a label centred in a metre of pill is harder to hit than one in a pill the size of the words.
+
+What this is not about is every row of controls. A set of filter chips, a pagination strip, a toolbar, a link sitting after a sentence — none of these is the page asking for something, and stacking them to full width would turn a strip the eye skims into a list it has to read. The test is whether the row is the call to action the section was written for.
+  Guidance only — cannot be checked automatically.
+- **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, Input and Switch simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+- **A component is written along the reading axis, not along the page's left and right** — Every measure, inset and placement in this package names an axis rather than a side: inline-size and block-size, padding-inline and padding-block, inset-inline-start and inset-block-end, margin-inline: auto, text-align: start. Written that way a component follows whichever direction the page is read in, and a band whose claim ranges to the leading edge with its subject on the trailing one is the same composition in Arabic as in English, mirrored, with nothing restated. Written as left and right it is the same pixels in both, which is a layout nobody designed for the second language.
+
+The enum values follow the same rule and for the same reason. A prop that names where a picture sits takes start and end, never left and right — FeatureSplit, FeatureBullets and FeatureScroll all declare mediaPosition that way, and the flex directions they generate flip on their own because row already means the reading order. A value called left would have to be re-read as right by every author working in a mirrored page, which is a translation this system should be doing rather than asking for.
+
+The guidance a contract carries is part of the component, so it follows too. Describing a claim as ranging left is describing one of the two languages, and it was written that way here for a while: three of the opening bands said so in their own intent. A reader in a mirrored page meets that sentence and has to decide whether the component is wrong or the sentence is, and neither answer is one documentation should force.
+
+Two things genuinely have no logical form and are not covered by this. A CSS gradient takes a physical direction — there is no to inline-end — so a pattern that must mirror has to be stated twice under a direction query, and one that is periodic and centred, like PageHeader's rule grid, does not need to. A glyph that points the way onward is the other: an arrow is a picture of a direction, and mirroring it belongs to the icon set rather than to the component holding it.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ FeatureCards for: Each item is one line, and the list is the argument
+   A line per inclusion is counted, not compared; a card per line is a grid of headings with nothing under them
+   → use `FeatureBullets` instead.
+
+❌ FeatureCards for: One claim beside a picture, with no card around it
+   FeatureSplit sets the words and the picture straight on the section. One card here is the boxed version — the same split held in a card — and a page uses whichever its neighbours are: cards beside cards, open sections beside open ones
+   → use `FeatureSplit` instead.
+
+❌ FeatureCards for: The items are read in order, one leading to the next
+   A grid is read in any order; a sequence wants a screen per stop
+   → use `FeatureScroll` instead.
+
+## Example
+
+```tsx
+import { FeatureCards, Card, Link, CardBody } from '@deriv-com/dds-marketing'
+
+<FeatureCards title="Why trade with Deriv" description="Everything you need to trade the markets, in one account." link={<Link href="/why-deriv">Learn more</Link>}>
+  <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="" />
+  </Card>
+  <Card variant="surface-light">
+    <CardBody title="250+ markets" description="Forex, stocks, commodities and more, side by side." link={<Link href="/markets">Learn more</Link>} src="/sample-card-image.svg" alt="" />
+  </Card>
+  <Card variant="accent">
+    <CardBody title="Start in minutes" description="Open an account with as little as $5." link={<Link href="/signup" tone="inherit">Learn more</Link>} src="/sample-card-image.svg" alt="" />
+  </Card>
+</FeatureCards>
+```
+
+## In use
+
+Most rows below hold the same set, written once here:
+
+```tsx
+import { Card, CardBody, Link } from '@deriv-com/dds-marketing'
+
+const cards = (
+  <>
+    <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="" />
+</Card>
+    <Card variant="surface-light">
+  <CardBody title="250+ markets" description="Forex, stocks, commodities and more, side by side." link={<Link href="/markets">Learn more</Link>} src="/sample-card-image.svg" alt="" />
+</Card>
+    <Card variant="accent">
+  <CardBody title="Start in minutes" description="Open an account with as little as $5." link={<Link href="/signup" tone="inherit">Learn more</Link>} src="/sample-card-image.svg" alt="" />
+</Card>
+  </>
+)
+```
+
+### A dark, a light and a coral card
+
+The set the reference design leads with: each card a ground of its own, a line, a way on and a picture. The light one is surface-light so it stays light in dark mode beside the dark one.
+
+```tsx
+import { FeatureCards } from '@deriv-com/dds-marketing'
+
+// accent-strong, surface-light, accent
+<FeatureCards title="Why trade with Deriv">{cards}</FeatureCards>
+```
+
+### How many share a row
+
+One card takes the row with its words beside its picture; two share it; three to a row at full width; four when there are exactly four.
+
+```tsx
+import { Card, CardBody, FeatureCards, Link } from '@deriv-com/dds-marketing'
+
+// One card, words beside the picture
+<FeatureCards title="Trade on any device">
+  <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="" />
+  </Card>
+</FeatureCards>
+
+// Two cards, two thirds of 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="" />
+  </Card>
+  <Card variant="surface-light">
+    <CardBody title="250+ markets" description="Forex, stocks, commodities and more, side by side." link={<Link href="/markets">Learn more</Link>} src="/sample-card-image.svg" alt="" />
+  </Card>
+</FeatureCards>
+
+// Three cards
+<FeatureCards title="Why trade with Deriv">
+  <Card>
+    <CardBody title="Tight spreads" description="Competitive pricing on every market." />
+  </Card>
+  <Card>
+    <CardBody title="Fast execution" description="Orders filled in milliseconds." />
+  </Card>
+  <Card>
+    <CardBody title="Always open" description="Derived indices that never close." />
+  </Card>
+</FeatureCards>
+
+// Four cards, one row
+<FeatureCards title="Our principles">
+  <Card>
+    <CardBody title="Be reliable" description="Contracts settled fairly and payments processed promptly." />
+  </Card>
+  <Card>
+    <CardBody title="Be fair" description="Every customer treated equitably, with no hidden costs." />
+  </Card>
+  <Card>
+    <CardBody title="Be transparent" description="Plain terms, and clear about the risks of trading." />
+  </Card>
+  <Card>
+    <CardBody title="Be responsible" description="No hard selling and no promises of returns." />
+  </Card>
+</FeatureCards>
+```
+
+### What the header carries
+
+The heading alone, or with a line under it and a way on to the page the set belongs to.
+
+```tsx
+import { CardBody, CardButton, FeatureCards, Link } from '@deriv-com/dds-marketing'
+
+// Title, line and link
+<FeatureCards title="Markets you can trade" description="Forex, stocks, commodities and more, from one account." link={<Link href="/markets">See all markets</Link>}>
+  <CardButton href="/markets/forex">
+    <CardBody title="Forex" description="The world's most liquid market." />
+  </CardButton>
+  <CardButton href="/markets/stocks">
+    <CardBody title="Stocks" description="The global names you already know." />
+  </CardButton>
+  <CardButton href="/markets/commodities">
+    <CardBody title="Commodities" description="Gold, silver, oil and gas." />
+  </CardButton>
+</FeatureCards>
+```
+
+### On the grey band and the dark one
+
+ground="subtle" tells a section apart from the one above; ground="strong" stops the page. A light card turns white on the grey band; the coloured cards keep their own grounds on either.
+
+```tsx
+import { FeatureCards } from '@deriv-com/dds-marketing'
+
+// Subtle ground, the dark, light and coral set
+<FeatureCards ground="subtle" title="Why trade with Deriv">{cards}</FeatureCards>
+
+// Strong ground, the same set
+<FeatureCards ground="strong" title="Why trade with Deriv">{cards}</FeatureCards>
+```