@deriv-com/dds-marketing 0.1.0 → 0.2.0

package/.llm/components/dropdownmenu.md

@@ -0,0 +1,453 @@
+<!-- GENERATED from dropdown-menu.contract.json. Do not edit. -->
+
+# DropdownMenu
+
+A button that opens a short set of destinations. Pressing one goes somewhere and the menu shuts — it holds no value and reports no answer, so there is nothing about it to find on reopening.
+
+It is the host MenuItem was written against. A row whose role is menuitem means nothing to a screen reader outside an element whose role is menu, so until this landed MenuItem was a contract and a stylesheet waiting for one. What this adds is everything a row cannot know about itself: that there is a set, how long it is, which one the reader is on, and that Escape puts them back on the button they pressed.
+
+The trigger is drawn here by default rather than passed in, which is where this parts company with product's menu of the same name. There the trigger is a Button handed over, on the argument that Button is where a button is decided. Marketing's Button cannot take that job: it is an anchor with a required href — a link, always — and a link that opens a menu is a link that does not navigate. ButtonIcon renders a real button but takes no words, and a set of destinations is chosen by reading them. So there is no button-with-words in this package to hand in, and the trigger is this component's to draw. That argument still holds and is the reason the drawn trigger is the default. What it does not cover is a trigger with no words at all: A control with no words is exactly what the paragraph above rules out for a set of destinations, and exactly right for a set of page numbers, which are read by their shape rather than their wording. What gets passed is the caller's business — ButtonIcon, or a button they drew themselves, which is what Pagination's break turned out to need. So `trigger` exists for that case — Pagination's break between two runs of pages — and for no other. Pass nothing and this still draws the whole thing, chevron included.
+
+A marketing page reaches for a menu where a set of destinations is too long to sit in the navigation and too short to deserve a page — the languages a site is published in, the regions it operates in, the pages a long index skipped over. Not for a toolbar of operations: a page has nothing to operate on, which is the whole difference from the menus an application builds.
+
+## Use when
+
+- A set of destinations too long for the navigation bar and too short to be a page of its own — languages, regions, the parts of a long index
+- The set is short enough to read at a glance, where a visitor is choosing rather than searching
+
+## Do not use
+
+- The set reports a choice the visitor should find marked when they return → nothing here does this
+- The destinations belong in the page's navigation → nothing here does this
+- It is one destination rather than one of a set → nothing here does this
+- The set is long enough that a visitor would rather type than read → nothing here does this
+- Anything that destroys. Marketing has no destructive tone by decision — a page navigates a visitor toward a conversion and never deletes on their behalf
+- The page's main action. A menu is a set of supporting destinations, and the one step a page was built to produce is a Button in the open where it can be seen without a press
+- Carrying the words a visitor needs before choosing. A row is a short label; what a choice means belongs on the page, where it can be read without opening anything
+
+## Anatomy
+
+DropdownMenu renders 6 elements. A token binding names the part it applies to.
+
+- `root` — `<div>`, class `dds-dropdownmenu`. Holds the trigger and the surface, and nothing else. `position: relative`, which is what the surface is absolute against — so the menu is pinned to the button that opened it rather than to the page, and moves with it.
+  
+  Inline rather than a block, because a menu button sits in a row of other things: a navigation bar, a footer column, the end of a band. A block root would take the width of whatever contains it and put the trigger at the start of an empty line.
+- `trigger` — `<button>`, class `dds-dropdownmenu__trigger`. The button that opens it, drawn here unless one is handed in.
+  
+  That is the one structural difference from product's menu, and it is forced rather than chosen: this package's Button is an anchor with a required href, so it is a link and cannot be a trigger; ButtonIcon is a real button and has no words. A set of destinations is chosen by reading them, so the trigger needs words, and nothing in this package draws a button with words. Drawing one here is the only honest answer left — and it is confined to this component rather than offered as a new button, because the moment it takes a variant it is a second place a button is decided.
+  
+  It wears the secondary button's look — an outlined pill, no fill — and takes no variant to change it. A menu of supporting destinations is not the step a page was built to produce, so the brand fill would be the one thing on the band claiming to be the point, and `one-primary-per-view` is the rule that says why. One look, because there is one job.
+  
+  A real `<button>`, with `type="button"` set rather than left to the element's own default of submit: a language picker dropped into a newsletter band would otherwise send the form on the way to opening.
+  
+  Two sizes, sm and md, at `size.control.sm` and `size.control.md`, each with side padding at half its height, so the words start where the pill's curve stops at either measure. The step above them is not offered: it reads as a hero control, and a menu of supporting destinations is never that. The menu passes its size to every row it renders, which keeps the trigger and the set it opens reading as one control.
+  
+  The mark reaches for `icon.control.md` at sm and `icon.control.lg` at md, which looks off by a step and is. That ramp is still indexed to the control names as they were, each of its steps sitting four above the label it stands beside, and the control ramp is moving to sm/md ahead of it. The measures are right at both steps; the names realign when Button, ButtonIcon and the fields migrate, and this rebinds to sm/md then with nothing else changing.
+  
+  Absent when a `trigger` is passed, which the anatomy does not say and cannot: presentWhen marks a part absent until a prop is set, and this is the inverse — the part is drawn until one is. Declaring it conditional would generate a test asserting it is missing from the default, where it is the whole trigger.
+  
+  Plain, it gives up the edge and nothing else. The target is the same size, the ground under a pointer is the same, and the focus ring is untouched — a control that shed its outline and its focus ring together would be one a keyboard reader could no longer find. `border.width.none` against the `border-style: solid` above rather than a second border-style: one property carries the difference, and the style stays where it is so nothing has to be put back.
+  
+  And plain, it takes the ink around it rather than naming one. The variant's whole premise is that something else has already said what this is — which means something else has also decided what colour reads on it. `color.fg.default` is a near-black chosen for paper, and a switcher carrying it into a bar standing on a dark hero is the one thing in that bar nobody can read. Link and Button both give up their ink the same way and call it `tone="inherit"`; here it is not a second axis, because a plain control has already given up its edge and its ground and there is no version of it that should keep its own colour.
+  
+  Plain at the small step is the one place the two axes come apart. `size` sets the type and the height together, which is right for a control standing on its own — but a bar wants the smaller type in a finger-sized target, which is exactly what the destinations beside it are: `font.label.sm` in a box of `size.control.md`. Without this the switcher was eight pixels shorter than its neighbours and the difference was invisible until a pointer landed on it and drew a fill that did not match the row.
+  
+  It can open under the pointer as well as under a press, and the press is never replaced: Enter and Space reach it where no pointer exists, and a reader who uses both gets the same result from either. Only a mouse counts — a tap reports `touch` and a stylus `pen` — and only what hover opened may be closed by hover, so a menu opened from the keyboard is not shut by a pointer passing over it on its way elsewhere.
+- `icon` — `<svg>`, class `dds-dropdownmenu__icon`. The mark before the words, when there is one. Sized by this component rather than by whatever the glyph shipped with — every glyph in the icon package carries width and height attributes of 24, and the only thing that overrides a presentation attribute is a CSS length on the element carrying it. So the class lands on the `<svg>` itself, which is why this part is an svg and not a box around one: Button and ButtonIcon both record the same finding, and a wrapper left the mark at whatever size it was imported at.
+  
+  Decorative. The trigger's words say what the menu is, and a mark that had to be read would be a button whose name was a picture.
+  
+  Absent when a `trigger` is passed, which the anatomy does not say and cannot: presentWhen marks a part absent until a prop is set, and this is the inverse — the part is drawn until one is. Declaring it conditional would generate a test asserting it is missing from the default, where it is the whole trigger. Rendered only when `icon` is set.
+- `label` — `<span>`, class `dds-dropdownmenu__label`. The trigger's words, and the accessible name of the menu they open — the surface points here rather than repeating them.
+  
+  One line, never wrapped. A menu button sits in a row of other things and a trigger that grew to two lines would push that row apart; a label long enough to wrap is a label that wanted fewer words.
+  
+  Absent when a `trigger` is passed, which the anatomy does not say and cannot: presentWhen marks a part absent until a prop is set, and this is the inverse — the part is drawn until one is. Declaring it conditional would generate a test asserting it is missing from the default, where it is the whole trigger.
+- `chevron` — `<svg>`, class `dds-dropdownmenu__chevron`. The mark that says a set is there, turned over while it is on screen.
+  
+  Drawn on the trigger this component draws, and not a prop. Product makes it one because its trigger is passed in and some buttons should not get a chevron — an icon-only one, or one whose trailing slot the page already filled. That case now exists here too: Pagination's break hands in an icon-only control, which wants no chevron. It does not need a prop to say so. A passed trigger simply does not get one, there being no trailing slot on anything this package draws to put it in and no way to reach inside somebody else's control to add it. So the chevron belongs to the drawn trigger, where there is no slot to compete for and no button whose author meant something else. A prop offering to remove it would only offer to remove the visual form of `aria-expanded`, which is the one thing a page cannot draw for itself because it does not know when the menu is open.
+  
+  One glyph rotated rather than two glyphs swapped, which is the ruling product's own chevron records: a swap replaces the mark between two frames, so there is nothing to watch and it reads as a flicker under the press. A rotation is the same mark moving, and the movement is what says which way the set went. The angle is inline — a rotation is not a property any token here carries — and the transition is bound below, so the reduced-motion block the stylesheet generates still switches the movement off. An inline transition would outrank that rule and ignore the preference.
+  
+  Decorative: `aria-expanded` on the trigger carries the same fact where it can be read.
+  
+  Absent when a `trigger` is passed, which the anatomy does not say and cannot: presentWhen marks a part absent until a prop is set, and this is the inverse — the part is drawn until one is. Declaring it conditional would generate a test asserting it is missing from the default, where it is the whole trigger.
+  
+  It can be turned off, which Product's version has always allowed and this one did not. The case is narrow and real: a switcher drawn `plain` in a navigation bar, among sections that each carry a chevron of their own. There the mark stops distinguishing the control and starts repeating what is already said three times across the row — and the locale's own words plus a globe are the whole of what a reader needs. `aria-expanded` is untouched either way, so what is given up is the drawing and not the fact. Rendered only when `chevron` is set.
+- `surface` — `<ul>`, class `dds-dropdownmenu__surface`. The panel and the list at once. One element carries the fill, the corner, the shadow, the inset and the ceiling before it scrolls — there is no second element to hold an empty state, because a menu with no destinations is a menu nobody should have rendered.
+  
+  Announced as a menu, which is what makes the arrow keys mean what they mean and what tells a screen reader these are rows to take rather than text to read. Named by the trigger that opened it, so a visitor hears which menu they are in without the page passing a second string.
+  
+  Its corner is `radius.menu` against MenuItem's `radius.menu-item`, and the inset between them is `space.inset.2xs` — 16 less 4 is 12, so the two curves are concentric and the first and last rows land on the panel's inside edge. The panel does not take `radius.surface`: that is 24 here, a measure written for a card sitting in the page, and a corner that wide over a 4 inset leaves the row's own corner nowhere to nest — 24 less 4 is 20, which on a row of 40 is exactly half, a pill. Product meets the same arithmetic at 16 because 16 is what `radius.surface` means there. This is that geometry under marketing's names, which is why `radius.menu-item` is product's 12 unchanged. Its ceiling is `size.menu.max`, which is counted in rows rather than pixels: a row here is taller than product's, so holding product's own measure would show a row less. It deliberately does not land on a row boundary — a set cut clean at the last full row looks like the whole set.
+  
+  Absent when shut rather than hidden, so nothing beneath it is covered by something nobody can see and no destination is reachable by a visitor tabbing past a closed button.
+  
+  As wide as its longest row rather than as wide as the trigger, with the trigger's width as a floor. A menu is a different object from the button that opened it, and a destination reading "Bahasa Indonesia" cannot be cut to fit a button reading "Language". One edge is pinned and the other let go, and which one is the alignment axis.
+  
+  It always opens downwards. A menu near the foot of the page should open upwards instead, and nothing here does that yet — the same gap product's menu has, and for the same reason it is not a prop: which side there is room on is a fact about the viewport at that moment, which a page cannot assert and cannot keep true through a scroll. Measured and flipped, or not done at all.
+  
+  It fades and grows a little on arriving, from its top edge — the one it is pinned to, so it reads as coming out of the trigger rather than swelling from its own middle. Gone entirely for a visitor who has asked for less movement. There is no matching exit: the surface is removed rather than held for its own way out, which is the gap product's menu has too.
+  
+  Its inset does not follow the size. Both steps keep `space.inset.2xs`, because the inset is half of the concentric arithmetic above — moving it at either step would leave `radius.menu-item` describing a corner the rows no longer sit at, and a row's corner is the one measure here that answers to the surface rather than to the control ramp.
+  
+  It clears the trigger by `space.gap.sm`, which is the step NavbarMenu's own panel takes and was `space.gap.xs` here. Four pixels is enough to read as a gap when the trigger is the only thing above it and is not enough when the trigger is inside something: dropped into a navigation bar's pill, the panel hung four pixels below the control and the pill's own four pixels of padding put the panel's top edge exactly on the pill's bottom edge, so the two boxes met with no seam at all. At eight the two panels in that bar — a section's and a switcher's — clear the pill by the same four pixels, which is the point: a reader sees one bar with things hanging off it rather than two components that each chose an offset. Rendered only when `open` is set.
+
+Apply these classes from the generated `dropdownMenuParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `MenuItem`
+- Never contains: `Button`, `ButtonIcon`, `Card`, `CardButton`, `Link`, `TextInput` — in children or in any prop that takes a node
+
+## Props
+
+### variant — `outlined` | `plain` (default `outlined`)
+
+- `outlined` — The control stands on its own — a switcher in a toolbar, a filter above a table, anywhere a reader has to find it before they can use it. The edge is what says there is something here to press
+- `plain` — The control sits among others that have already said what they are — a locale beside a row of sections in a navigation bar, where every neighbour is words and a mark and an edge around one of them would make it the loudest thing in the set. It keeps the target, the ground it takes under a pointer and the ring it takes under focus, and gives up only the edge
+
+### size — `sm` | `md` (default `md`)
+
+- `sm` — Beside body copy rather than above it — a language picker in a navigation bar or a footer, where the trigger is one item in a row of links and should not outweigh them
+- `md` — The default, and nearly every other page. The same height as a default Button, so the two line up when they sit in the same band
+
+Use when: Match it to the controls it stands beside. Two steps and no third: this package's control ramp runs sm then md, and the step above them is being retired rather than offered here
+Never for: Making the menu itself bigger. This sizes the trigger and the rows in it; how wide the panel runs is its longest destination's business, and how tall it gets before scrolling is size.menu.max at either step
+
+### alignment — `start` | `end` (default `start`)
+
+- `start` — The menu's leading edge lines up with the trigger's. The default, because a visitor reads from that edge and the destinations begin where the button's own words began
+- `end` — Its trailing edge lines up instead, which is what a trigger near the end of a row needs — a footer's language picker aligned to the start would run off the screen
+
+### tone — `default` | `inverse` (default `default`)
+
+- `default` — The control is on a light ground, which is every surface this package paints by default
+- `inverse` — The control is on a ground that runs against the mode — a navigation bar standing on a dark hero. Only the tints move: the ink is the surrounding ink already under `variant="plain"`, and the words and the mark were never this component's to colour. NavbarItem and NavbarMenu take the same tone for the same reason, and a switcher among them that did not would be the one item in the row whose hover disappeared
+
+### label — `string` **Required.**
+
+Use when: Always — the words on the trigger, and the whole of what a visitor has to go on before they press it. "Language", "Region", "More pages". Required because a trigger drawn by this component has no children to fall back on, and a menu button reading nothing is a menu nobody opens.
+
+It names the menu as well as the button. The surface points at the trigger for its own accessible name rather than taking a second string, so the two cannot drift — product needs a separate one only because its trigger is opaque to it, and this one is not.
+Never for: A sentence. This sits in a row of other things and does not wrap — words long enough to need the room are words that belong on the page.
+
+### icon — `node`
+
+Accepts: QuillSystemIcon
+Use when: A mark before the trigger's words, where the set is read by shape as much as by reading — a globe beside "Language", a flag beside the region a visitor is already in
+Never for: The chevron, which this component draws itself and is not a slot. And saying what the menu holds when the words already do: a mark beside "Language" is recognised faster, a mark beside "Choose where you are reading from" is decoration in front of a sentence
+
+### chevron — `boolean` (default `true`)
+
+Use when: A chevron in the trigger, pointing down while the menu is shut and up while it is open. On by default because it is the visual form of aria-expanded — the same fact the attribute carries, drawn — and this component is the only thing that knows it. Product's DropdownMenu names the same prop for the same reason
+Never for: A trigger standing on its own. Without an edge or a chevron there is nothing left saying the control opens anything, and a reader finds out by pressing it. Turn it off only where the neighbours say it — a locale in a row of sections that each carry one, where a third chevron is the repetition rather than the signal
+
+### openOnHover — `boolean` (default `false`)
+
+Use when: The menu is one of several things on a bar that open, and the others open on hover — a switcher beside a row of navigation sections, where a reader who has learned that the sections open under the pointer meets one control that does not and reads it as broken. Off everywhere else: a filter above a table or a switcher in a toolbar is a deliberate act, and a menu that opened as the pointer crossed it on the way somewhere else is a menu in the way
+Never for: A menu whose rows do something on the spot rather than go somewhere. Hover is an accident as often as it is an intention, and a set opened by accident is one a reader can act on by accident
+
+### trigger — `node`
+
+Use when: A control this component should open rather than draw — one whose mark is the whole of it, with no words to read. A ButtonIcon is the obvious candidate and not the only one: Pagination's break between two runs of page numbers passes a button of its own, because it has to match the numbered targets either side of it and this package's ButtonIcon has no transparent form to do that with. Given one, `icon` and `label`'s words go unused: what is drawn is what was passed. What this component still supplies is the half a page gets wrong — that the control announces a menu and whether it is open, that Escape returns focus to it, and that the arrow keys move through the rows.
+Never for: Anything that is not a button. A menu opened by a div is a menu a keyboard cannot reach, and one opened by this package's Button is a link that does not navigate — Button is an anchor here, which is the reason this component drew its own trigger to begin with. Nor for a control with words on it, which is what the drawn trigger is already for and does better, the chevron included.
+
+### open — `boolean`
+
+Use when: The page holds whether the menu is open, and this component stops holding it. For the case where something outside has to shut it — a navigation bar that closes its menu when another one opens. Pair it with onOpenChange, or the menu is open forever
+Never for: Opening it on arrival. A menu that opens itself is a panel the visitor did not ask for, over content they came to read — and the browser scrolls whatever takes focus into view, so it moves the page as well
+
+### defaultOpen — `boolean`
+
+Use when: A specimen — a documentation page, the preview's own stage — where the menu has to be on screen to be looked at. This component still holds the state afterwards
+Never for: A real page. It is the same objection as open's, without even a prop the page could use to close it again
+
+### onOpenChange — `callback`
+
+Use when: Something outside has to know — a navigation bar shutting its other menus, a page that dims behind an open one. Required in practice alongside open, which is the only way a driven menu ever closes
+Never for: Running what the row does. That is the row's own onSelect, and a menu cannot tell you which one was pressed — it only knows that it shut
+
+Also accepts everything from `HTMLAttributes<HTMLDivElement>`.
+
+## 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: `menu`
+- `Enter or Space` — on the trigger, open the menu and put focus on the first destination
+- `ArrowDown` — on the trigger, the same; inside the menu, the next destination
+- `ArrowUp` — on the trigger, open it and put focus on the last — for a visitor reaching for the thing at the bottom; inside the menu, the previous one
+- `Home` — the first destination
+- `End` — the last destination
+- `Escape` — shut the menu and return focus to the trigger, which is where the visitor was and what they pressed
+- `Tab` — shut the menu and carry on out of it. Inside the menu Tab does not move between rows — the arrow keys do that, which is what the menu role promises
+- `a letter` — the next destination beginning with it, for a set read by eye and reached by hand
+- focus moves to the rows themselves rather than being described from the trigger. A menu's rows are things to take, and a visitor pressing Enter should be pressing the thing they are on — where a field keeping focus in its box does so because the box is what holds the answer
+- the trigger says a menu is there and whether it is open, through aria-haspopup and aria-expanded. The chevron is the same fact drawn, and neither stands in for the other — one is for a screen reader and one is for an eye
+- the surface is named by the trigger rather than by a string of its own, so what a visitor hears is what they read before pressing and the two cannot drift apart
+- shutting returns focus to the trigger. A menu that shuts and leaves focus where the surface was drops a keyboard visitor at the top of the document, several tabs from the button they pressed
+- a row that cannot be used stays in the menu and is announced as unavailable rather than being removed. A set that changes shape between openings is one a visitor has to learn twice
+- the menu is absent from the document when shut rather than hidden, so no destination is reachable by a visitor tabbing past a closed button
+- the trigger is a real button. A menu opened by a div is a menu a keyboard cannot reach, and one opened by a link is a link that does not navigate — which is why this package's own Button, an anchor with a required href, could not be the trigger
+
+## 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
+
+❌ DropdownMenu for: The set reports a choice the visitor should find marked when they return
+   Nothing here does this yet. Its rows are commands, so they hold no value and the menu cannot show which one is current — a language picker that forgets the language is a picker that has not picked. The trigger's own words are the closest this gets, and the page has to set them.
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+❌ DropdownMenu for: The destinations belong in the page's navigation
+   A menu is where a visitor goes when the navigation could not carry something, not a way to avoid writing one. Links in a nav are found; commands in a menu are looked for, and a visitor who does not open it never learns the set exists.
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+❌ DropdownMenu for: It is one destination rather than one of a set
+   Button. A menu holding a single row is a button wearing a panel, and it costs the visitor a press to discover that.
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+❌ DropdownMenu for: The set is long enough that a visitor would rather type than read
+   Nothing here filters, and a menu is read top to bottom. Past a couple of dozen rows a reader is searching rather than choosing, and this offers them nothing to search with — the first letter jumps, which is a shortcut for a set already known rather than a way to find one.
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+## Example
+
+```tsx
+import { DropdownMenu, MenuItem } from '@deriv-com/dds-marketing'
+import { GlobeRegularIcon } from '@deriv-com/quill-icons-web'
+
+<DropdownMenu label="Language" icon={<GlobeRegularIcon />}>
+  <MenuItem onSelect={() => { /* your handler */ }}>English</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Deutsch</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Français</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Bahasa Indonesia</MenuItem>
+</DropdownMenu>
+```
+
+## In use
+
+Most rows below hold the same set, written once here:
+
+```tsx
+import { MenuItem } from '@deriv-com/dds-marketing'
+
+const menuitems = (
+  <>
+    <MenuItem onSelect={() => { /* your handler */ }}>English</MenuItem>
+    <MenuItem onSelect={() => { /* your handler */ }}>Deutsch</MenuItem>
+    <MenuItem onSelect={() => { /* your handler */ }}>Français</MenuItem>
+    <MenuItem onSelect={() => { /* your handler */ }}>Bahasa Indonesia</MenuItem>
+  </>
+)
+```
+
+### Shut, and open
+
+A button until it is pressed. The chevron is this component's to draw — a page cannot know when the menu is open, and one it passed would point the same way forever.
+
+```tsx
+import { DropdownMenu, MenuItem } from '@deriv-com/dds-marketing'
+
+// Shut, which is a button and nothing more
+<DropdownMenu label="Language">
+  <MenuItem onSelect={() => { /* your handler */ }}>English</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Deutsch</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Français</MenuItem>
+</DropdownMenu>
+
+// Open, with the destinations it holds
+<DropdownMenu label="Language" defaultOpen>
+  <MenuItem onSelect={() => { /* your handler */ }}>English</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Deutsch</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Français</MenuItem>
+</DropdownMenu>
+```
+
+### Destinations, not operations
+
+What a marketing menu is for: the languages a site is published in, the regions it covers. A visitor is choosing where to go, not doing something to the page.
+
+```tsx
+import { DropdownMenu, MenuItem } from '@deriv-com/dds-marketing'
+import { GlobeRegularIcon } from '@deriv-com/quill-icons-web'
+
+// The languages a site is published in
+<DropdownMenu label="Language" icon={<GlobeRegularIcon />} defaultOpen>{menuitems}</DropdownMenu>
+
+// One not reachable yet, announced not removed
+<DropdownMenu label="Region" defaultOpen>
+  <MenuItem onSelect={() => { /* your handler */ }}>United Kingdom</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Singapore</MenuItem>
+  <MenuItem disabled onSelect={() => { /* your handler */ }}>Deutschland</MenuItem>
+</DropdownMenu>
+```
+
+### Which edge it opens from
+
+One edge is pinned to the trigger and the other let go, which is what lets the menu be wider than the button. End is for a trigger near the end of a row.
+
+```tsx
+import { DropdownMenu, MenuItem } from '@deriv-com/dds-marketing'
+
+// From the trigger's leading edge, which is the default
+<DropdownMenu label="Language" alignment="start" defaultOpen>
+  <MenuItem onSelect={() => { /* your handler */ }}>English</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Bahasa Indonesia</MenuItem>
+</DropdownMenu>
+
+// From its trailing edge, for a footer's last control
+<DropdownMenu label="Language" alignment="end" defaultOpen>
+  <MenuItem onSelect={() => { /* your handler */ }}>English</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Bahasa Indonesia</MenuItem>
+</DropdownMenu>
+```
+
+### As wide as its longest destination
+
+The trigger's width is a floor rather than a measure. A destination reading "Bahasa Indonesia" cannot be cut to fit a button reading "Language".
+
+```tsx
+import { DropdownMenu, MenuItem } from '@deriv-com/dds-marketing'
+
+// A short trigger, and a row far wider than it
+<DropdownMenu label="Language" defaultOpen>
+  <MenuItem onSelect={() => { /* your handler */ }}>English</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Bahasa Indonesia</MenuItem>
+</DropdownMenu>
+
+// And a wide trigger with short rows, held by the floor
+<DropdownMenu label="Choose your reading language" defaultOpen>
+  <MenuItem onSelect={() => { /* your handler */ }}>English</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Deutsch</MenuItem>
+</DropdownMenu>
+```
+
+### Two sizes
+
+The trigger follows the controls it stands beside, and the rows follow the trigger. Two steps and no third — the step above them is not offered here.
+
+```tsx
+import { DropdownMenu, MenuItem } from '@deriv-com/dds-marketing'
+
+// sm — beside a row of navigation links
+<DropdownMenu size="sm" label="Language" defaultOpen>
+  <MenuItem onSelect={() => { /* your handler */ }}>English</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Deutsch</MenuItem>
+</DropdownMenu>
+
+// md — the default, and nearly every page
+<DropdownMenu size="md" label="Language" defaultOpen>
+  <MenuItem onSelect={() => { /* your handler */ }}>English</MenuItem>
+  <MenuItem onSelect={() => { /* your handler */ }}>Deutsch</MenuItem>
+</DropdownMenu>
+```
+
+### With an edge, and without
+
+The edge is what finds a control standing on its own. Among neighbours that are already words and a mark, it is the thing that stands out instead.
+
+```tsx
+import { DropdownMenu } from '@deriv-com/dds-marketing'
+import { GlobeRegularIcon } from '@deriv-com/quill-icons-web'
+
+// outlined — on its own in a toolbar
+<DropdownMenu label="Language" icon={<GlobeRegularIcon />}>{menuitems}</DropdownMenu>
+
+// plain — among items that carry their own chevrons
+<DropdownMenu label="Language" icon={<GlobeRegularIcon />} variant="plain" size="sm" chevron={false}>{menuitems}</DropdownMenu>
+```
+
+### Which ground it is on
+
+Only the tints move. Under plain the ink is already whatever the surface set, so what is left to say is what a pointer and a focus ring should look like against it.
+
+```tsx
+import { DropdownMenu } from '@deriv-com/dds-marketing'
+import { GlobeRegularIcon } from '@deriv-com/quill-icons-web'
+
+// default — a light bar
+<DropdownMenu label="Language" icon={<GlobeRegularIcon />} variant="plain" size="sm" chevron={false}>{menuitems}</DropdownMenu>
+
+// inverse — a bar on a dark hero
+<DropdownMenu label="Language" icon={<GlobeRegularIcon />} variant="plain" size="sm" chevron={false} tone="inverse">{menuitems}</DropdownMenu>
+```
+
+### What opens it
+
+A press, always. A pointer as well where the menu sits among others that open the same way and one that did not would read as broken.
+
+```tsx
+import { DropdownMenu } from '@deriv-com/dds-marketing'
+import { GlobeRegularIcon } from '@deriv-com/quill-icons-web'
+
+// A press — a switcher standing on its own
+<DropdownMenu label="Language" icon={<GlobeRegularIcon />}>{menuitems}</DropdownMenu>
+
+// A press or a pointer — one of a row that opens
+<DropdownMenu label="Language" icon={<GlobeRegularIcon />} variant="plain" size="sm" chevron={false} openOnHover>{menuitems}</DropdownMenu>
+```