@deriv-com/dds-marketing 0.1.0 → 0.2.0

package/.llm/components/filterchip.md

@@ -0,0 +1,314 @@
+<!-- GENERATED from filter-chip.contract.json. Do not edit. -->
+
+# FilterChip
+
+A token the reader turns on and off in place, standing for one narrowing of the set shown beside it. On a marketing site that set is an index — articles, help topics, market pages, an events list — and the chips are the topics it can be cut down to. It is a button that stays where it is and reports whether it applies, which is what separates it from a control that takes the reader somewhere. Reach for one where a handful of narrowings sit above the list they narrow and any number of them may be on at once.
+
+## Use when
+
+- An index is long enough to be worth cutting down and its categories are few enough to show in full — a blog filtered by topic, a help centre filtered by product, a market list filtered by asset class
+- The choice is small enough that a form control would be more machinery than it deserves — turning one topic on is not a question worth a checkbox and a label
+- What is chosen has to stay visible while the reader reads what it did, so the narrowing and the list it produced can be read together
+
+## Do not use
+
+- The token stands for a narrowing already applied, which the reader drops rather than turns off → `RemovableChip`
+- The thing named cannot be acted on and is there to be read — a tag on an article, a status on a card → `Badge`
+- The chips are really the navigation of the page, and pressing one changes what the page is → `Tab`
+- Pressing it goes somewhere — a category page with its own address → `Link`
+- An action. It is pressed to say a thing applies, and nothing else — one that submits or navigates is a button wearing a token's shape, and a reader cannot tell which they have until they press it
+- A set so long it wraps into several rows. Chips are read as a group at a glance, and past a handful the reading costs more than a list would
+- Carrying the chosen state in hue alone. Two colours of the same lightness are no difference to a reader who cannot separate them, which is why the chosen ground travels the whole way from the page's ground to the darkest one this package has rather than to a tint of the same weight
+
+## Anatomy
+
+FilterChip renders 4 elements. A token binding names the part it applies to.
+
+- `root` — `<button>`, class `dds-filterchip`. The chip, and it is the button. That is the whole reason this is its own component: a token that is pressed to toggle should be the thing that is pressed, so the state it reports sits on the element carrying the role rather than on a child of it. It declares a minimum width of its own: the chip is as wide as the word inside it, and a one-word topic is a smaller target than a two-word one for no reason the reader could guess. Unavailability is a state rather than an axis of its own: the root is the button, so the browser answers :disabled on it directly and the attribute takes the chip out of the tab order at the same time. Its padding steps with the size on two inset roles, each one step tighter than the pill padding a Button of the same height takes. The two ends are not equal once something follows the words: the trailing inset is what the cap leaves around whatever is in that slot, so a mark with a ground of its own reads as centred in the end of the pill rather than pushed off it. A badge is the tallest thing the slot holds and takes the tightest inset; a bare glyph is shorter and takes a step more; nothing at all leaves the words at their own inset. The escape hatch takes the glyph step rather than the badge one, because the component cannot see what is in it and the two ways of being wrong are not equal — a mark with a ground of its own sitting a few pixels loose is something a reader never notices, where one without a ground pulled in tight reads as clipped by the curve. This is the same arrangement RemovableChip makes for its cross, arrived at for the same reason. That step is what separates a chip from a button once they share a ramp: the label no longer starts where the curve stops, so the token reads as denser than the control beside it rather than as a smaller copy of it. It takes this package's control ramp rather than a scale of its own — there is one ramp here, its small step was written for a field in a filter row, and a second scale existing only for chips would be a distinction no marketing page is dense enough to need.
+- `icon` — `<span>`, class `dds-filterchip__icon`. A glyph before the words, naming what kind of thing is being narrowed by. Its own part because a glyph arrives as somebody else's element and needs a box of its own to sit in. The box centres what it holds on both axes: a bare svg is inline, and left to the baseline it sits on the line the words sit on, riding high in a box whose height was set for it. Its colour comes from the words beside it, and so does its measure: it steps when the type steps rather than when the height does, so it never outgrows the words it introduces. It leads and stays put: a chip that is chosen shows the same glyph it showed before, so the row does not change width as chips are pressed. Rendered only when `leadingIcon` is set.
+- `label` — `<span>`, class `dds-filterchip__label`. What the chip narrows by. It truncates rather than wrapping, because a chip is one line in a row of them and one that grew two lines tall would push every sibling out of alignment. It keeps the label weight at every size and in both states: a chip row has no single current member, any number may be on, and the ground already says which. Dropping the weight of the unchosen would dim most of the row to mark the rest, and muted text at the body weight is what this system uses for controls that cannot be pressed at all. The type steps with the height, so the words hold their proportion of the chip at either step.
+- `trailing` — `<span>`, class `dds-filterchip__trailing`. One thing after the words, and at most one. Which thing is decided by `content` rather than by which node was handed in, so a badge left on a chip that has moved to an icon renders nothing instead of two marks fighting for the space. Named for where it is rather than for what is in it. It takes the words' colour exactly, in both states, so a glyph in it reads at the label's weight rather than as an afterthought behind it, and a Badge inside brings its own, which is correct: a count is not a decoration of the label, it is a fact of its own. Rendered only when `content` is set.
+
+Apply these classes from the generated `filterChipParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `Button`, `FilterChip`, `RemovableChip`, `Link`, `TextInput` — in children or in any prop that takes a node
+
+## Props
+
+### selected — `boolean` (default `false`)
+
+Use when: The narrowing currently applies. It is the consumer's to hold, because the list and the chip are one fact — a chip keeping its own copy is how the two come to disagree
+Never for: Marking something as important, or as the default. Chosen means the reader chose it, and one that arrives already on implies an act nobody took
+
+### size — `sm` | `md` (default `sm`)
+
+- `sm` — The default. A step under the button or field it stands beside rather than level with it, which is what keeps a row of narrowings from reading as a row of calls to action
+- `md` — A touch-first layout, or a filter row in a hero band where the chips carry more weight. It still sits a step under a large button, which is the cost of a chip that cannot be mistaken for one — where the target matters more than the distinction, the control wanted is a button
+
+Use when: How dense the row is, matched to whatever it sits beside. It is the chip that takes the size, and everything inside follows — the height, the words and the glyphs all follow, so a row cannot end up with type from one size and marks from another.
+Never for: Marking one chip in a row as more important. They are a set of equals and a row of mismatched heights reads as a mistake before it reads as emphasis
+
+### content — `none` | `icon` | `badge` | `custom` (default `none`)
+
+- `none` — Nothing after the words. Most chips, and the one to reach for unless something earns the space in a row read at a glance
+- `icon` — A glyph qualifying the narrowing rather than naming it — a mark that a topic is new, or that it came from somewhere else. It says something about the filter, where the leading glyph says what kind of filter it is
+- `badge` — How many entries the narrowing would leave, which is the fact a reader wants before they press. A count beside the words turns a guess into a decision, and it is the reason this slot is worth having on a chip at all
+- `custom` — The row needs a mark neither of the named kinds is. Reach for it last: the named kinds are what the documentation and the Figma library can describe, and anything here is a shape only this page knows about — which is also why the chip insets it as though it were a bare glyph rather than a badge, having no way to measure it.
+
+Use when: What the chip carries after its words, where it carries anything. It names the kind rather than being inferred from which node arrived, so exactly one thing can be in the slot and a leftover prop is inert rather than fighting for the space
+Never for: Repeating the label, or naming the narrowing twice. The slot qualifies what the words already said; a chip whose trailing mark restates them has spent the space for nothing
+
+### label — `string` **Required.**
+
+Use when: Always, and required on that account — it is the whole of what the chip says. Short enough to read at a glance: a token carrying a sentence has stopped being one
+Never for: Describing what pressing it does. The chip names the narrowing, and what happens is that the narrowing applies
+
+### leadingIcon — `node`
+
+Accepts: QuillSystemIcon
+Use when: A glyph makes the kind of narrowing faster to recognise than its name alone. It sits before the words and never replaces them. Pass the glyph itself rather than one already wrapped in an Icon: the chip wraps it at icon.size.xs at sm and icon.size.sm at md.
+Never for: Decoration, or a second copy of what the word says. A row where every chip carries a mark that adds nothing reads more slowly than plain words would
+
+### trailingIcon — `node` **Required when content=icon.**
+
+Accepts: QuillSystemIcon
+Use when: The glyph shown when content is icon. Sized and coloured with the chip rather than on its own terms, so a row of them reads as one set.
+Never for: Filling the slot on its own. `content` decides what is shown, so this is inert until it names icon — which is what stops two marks arriving at once when a chip changes its mind about what it carries
+
+### badge — `node` **Required when content=badge.**
+
+Accepts: Badge
+Use when: The count shown when content is badge. A Badge rather than bare type, so the number reads as a fact of its own rather than as part of the label — and so it carries its own colour, which the chip does not decide
+Never for: Filling the slot on its own. `content` decides what is shown, so this is inert until it names badge
+
+### custom — `node` **Required when content=custom.**
+
+Accepts: *
+Use when: Whatever is shown when content is custom. Nothing here is described by the documentation or the library, which is the cost of the escape hatch
+Never for: Filling the slot on its own. `content` decides what is shown, so this is inert until it names custom
+
+### onSelect — `callback`
+
+Use when: What hears the press. It reports what the chip is about to become rather than that it was pressed, so a consumer writes the value back without working out which way it went
+Never for: Reading the event. The signature is the new state because that is the decision the reader made; a handler reaching for the event recomputes what it was handed
+
+Also accepts everything from `ButtonHTMLAttributes<HTMLButtonElement>`.
+
+## Choosing a variant
+
+Placement in, props out. When one of these describes what you are building, take
+its props — do not re-derive them from the variant descriptions above.
+
+- **Topics above a blog or article index** — `selected`
+  The row is the state of the query, readable at a glance and changeable in place. Each topic is turned off where it stands, without returning to a control somewhere else on the page
+- **A filter row that mixes kinds — some narrowings toggle, some are already applied** — `selected`
+  This is the one that toggles in place, and it sits beside a RemovableChip standing for something already applied. They are two components because the reader does two different things to them, and one row because both narrow the same index — which is why they share a height, a corner and a type
+
+## States
+
+States you set. Everything else is driven by the browser.
+
+- `disabled` — The chip cannot be acted on — a narrowing that would leave the index empty, or one that does not apply to what is on screen. It dims and leaves the tab order
+  Avoid when: The reader could act on it if they knew what to change. This says the choice is closed and nothing about why, so a reason belongs in the prose around the set
+
+## 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: `button`
+- `Tab` — One stop, because there is one thing to do. A chip that also offered a way to remove itself would need two, which is the component next door
+- `Enter` — Turns the narrowing on or off
+- `Space` — The same as Enter, which a button answers by being one
+- selection reaches a screen reader through aria-pressed, which is the only channel that does not depend on seeing the chip at all. On screen it is the ground: not a tint but the full step from the page's own ground to the darkest this package has, so the difference survives greyscale and a reader who cannot separate hues. A step in border-width was tried in its place and is not the answer — it widens the chip and shifts every one after it along the row on each press.
+- an accessible name drawn from label, so the chip announces what it narrows by
+- a disabled chip leaves the tab order rather than being announced and refused. There is one control here and nothing to explain, so the native attribute is the honest one
+
+## 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.
+
+## Anti-examples
+
+❌ FilterChip for: The token stands for a narrowing already applied, which the reader drops rather than turns off
+   Removing a thing and un-choosing it are different acts with different outcomes: one takes the token off the screen, the other leaves it there saying no. A chip offering a cross where the reader expected a toggle loses them the thing entirely
+   → use `RemovableChip` instead.
+
+❌ FilterChip for: The thing named cannot be acted on and is there to be read — a tag on an article, a status on a card
+   Readers learn that chips can be pressed, so one that answers no press is a control that is not one. Badge says the same word and promises nothing
+   → use `Badge` instead.
+
+❌ FilterChip for: The chips are really the navigation of the page, and pressing one changes what the page is
+   A strip of tabs says exactly one is current and gives the set one tab stop. A row of chips says any number may be on, and using it for navigation promises a combination the page cannot render
+   → use `Tab` instead.
+
+❌ FilterChip for: Pressing it goes somewhere — a category page with its own address
+   A narrowing that has a URL is a place, and a place should be an anchor: crawlable, openable in a new tab, and returned to by the back button. A button that navigates is none of those, and on a marketing page being crawlable is usually why the index exists
+   → use `Link` instead.
+
+❌ content=icon + trailingIcon missing or empty
+   content is icon and there is nothing to show, which renders a gap where something was promised
+
+❌ content=badge + badge missing or empty
+   content is badge and there is nothing to show, which renders a gap where something was promised
+
+❌ content=custom + custom missing or empty
+   content is custom and there is nothing to show, which renders a gap where something was promised
+
+## Example
+
+```tsx
+import { FilterChip } from '@deriv-com/dds-marketing'
+
+<FilterChip label="Market news" selected />
+```
+
+## In use
+
+### On and off
+
+The chosen ground travels the whole way to the darkest this package has, rather than to a tint. That is what keeps it readable in greyscale.
+
+```tsx
+import { FilterChip } from '@deriv-com/dds-marketing'
+
+// Off — on offer, not yet applied
+<FilterChip label="Platforms" />
+
+// On — the narrowing applies
+<FilterChip label="Market news" selected />
+```
+
+### A row, read as one thing
+
+Any number may be on at once, and the row is the state of the query — which is what separates it from a strip of tabs, where exactly one is current.
+
+```tsx
+import { FilterChip } from '@deriv-com/dds-marketing'
+
+// Applied
+<FilterChip label="Trading" selected />
+
+// On offer
+<FilterChip label="Platforms" />
+
+// Applied
+<FilterChip label="Market news" selected />
+
+// On offer
+<FilterChip label="Education" />
+
+// On offer
+<FilterChip label="Company" />
+```
+
+### What it carries
+
+The leading glyph says what kind of narrowing this is and stays put when chosen. The trailing slot says what is true of it.
+
+```tsx
+import { Badge, FilterChip } from '@deriv-com/dds-marketing'
+import { ArrowUpRightRegularIcon, ChartCandlestickRegularIcon } from '@deriv-com/quill-icons-web'
+
+// A count — the fact a reader wants before pressing
+<FilterChip label="Education" content="badge" badge={<Badge label="24" variant="neutral" />} />
+
+// Both slots — kind before, fact after
+<FilterChip label="Trading" selected content="badge" leadingIcon={<ChartCandlestickRegularIcon />} badge={<Badge label="18" variant="neutral" />} />
+
+// A glyph qualifying it — a topic that opens elsewhere
+<FilterChip label="Partners" content="icon" trailingIcon={<ArrowUpRightRegularIcon />} />
+
+// The escape hatch, for a mark neither named kind is
+<FilterChip label="Trending" content="custom" custom="🔥" />
+```
+
+### Unavailable
+
+A narrowing that would leave the index empty. It dims and leaves the tab order — and says nothing about why, so a reason belongs in the prose around the set.
+
+```tsx
+import { FilterChip } from '@deriv-com/dds-marketing'
+
+// Nothing under this topic just now
+<FilterChip label="Careers" disabled />
+```
+
+### Sizes
+
+Both steps sit on this package's control ramp. The chip takes the size and everything inside follows — the height, the words and the glyphs.
+
+```tsx
+import { FilterChip } from '@deriv-com/dds-marketing'
+
+// sm — the default, a step under the button beside it
+<FilterChip label="Market news" size="sm" />
+
+// md — a touch-first layout, or a hero filter row
+<FilterChip label="Market news" size="md" />
+```