@deriv-com/dds-marketing 0.1.0 → 1.0.0

package/.llm/components/button.md

@@ -0,0 +1,295 @@
+<!-- GENERATED from button.contract.json. Do not edit. -->
+
+# Button
+
+Drives a visitor toward a conversion goal — a signup page, a pricing page, a demo booking — or performs the one action a section asks for, such as sending a newsletter form or opening a video. An `<a>` when given an href and a `<button>` when not, so a CTA that goes somewhere gets the browser's navigation and one that acts in place answers Space and does what the page says.
+
+## Use when
+
+- The call to action on a marketing page — the one step you want a visitor to take next
+- Moving a visitor along a funnel: hero to signup, pricing to checkout, feature page to demo booking
+- A destination prominent enough that it has to read as a control rather than as words in a sentence
+
+## Do not use
+
+- The action belongs to an application surface — a trade form, a settings panel, a confirmation that removes something → nothing here does this
+- The words belong inside a sentence or a paragraph of body copy → `Link`
+- The control is a glyph alone, with no words → `ButtonIcon`
+
+## Anatomy
+
+Button renders 3 elements. A token binding names the part it applies to.
+
+- `root` — `<button>`, class `dds-button`. The control. An `<a>` when given an href and a `<button>` when not, the shape CardButton and ButtonIcon already take: an anchor keeps cmd-click and middle-click, shows its destination and gets its pending state from the browser chrome, and a button answers Space and does what the page says. Two components for that would be two names for one press. It carries the variant and the size, so the fill, the padding and the type step all follow one decision. It is inline-flex rather than flex — a CTA is as wide as its words plus its inset, and a block-level control in a hero would stretch to the section it sits in. It resets the font and the block padding a `<button>` brings from the user agent, so the two elements render one pill. Its own structural keywords are the contract's top-level staticCss, which is where the root's belong.
+- `label` — `<span>`, class `dds-button__label`. The words, and the accessible name of the control. Always rendered — a CTA whose label is optional is a CTA that ships unnamed, and here the words are also the only thing that says where the visitor is going. A box of its own so the type step binds to the words rather than to the root, which would inherit it down onto the glyph beside them.
+- `icon` — `<svg>`, class `dds-button__icon`. The box the mark sits in, and the mark is a Quill glyph rather than a shape this component draws. A part of its own because the size tokens have to land on the element that renders — the same reason Breadcrumb's separator-icon is a part. Its weight is the icon system's: Quill ships every glyph light, regular and solid, chosen at the import site. Takes the label's colour through currentColor, so one mark is correct on a brand fill and on an inverse one alike. It never shrinks: a CTA short of room would drop the mark before its words. On hover it slides one gap step forward. Rendered only when `showIcon` is set.
+
+Apply these classes from the generated `buttonParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `text`
+- Never contains: `Button` — in children or in any prop that takes a node
+
+## Props
+
+### variant — `primary` | `secondary` | `inverse` (default `primary`)
+
+- `primary` — The step the page was built to produce. Carries the brand fill, which is what makes it findable at a glance and what makes it meaningless once there are two — a section offering two brand fills has said nothing about either.
+- `secondary` — A real destination that is not the one being pushed — compare plans, read the docs, talk to sales. The lightest tint the ramp offers, color.bg.subtle, the same fill product's secondary carries, so a CTA and its alternative read as one family across both packages. Hover and press are layered over the fill as a background-image rather than replacing it, which is how product darkens a tint that has no hover partner of its own. On the dark band, tone="inverse" keeps the fill and turns it white.
+- `inverse` — A section that paints its own ground — a brand-coloured hero, a photo band, a dark takeover. There the brand fill is invisible against the fill behind it and a neutral edge is the wrong ink, so the only thing that reads is a solid at the far end of the neutral ramp: pure black in light, pure white in dark. It outranks everything near it, which is what makes it right there and wrong anywhere else.
+
+Use when: Deciding how much of the section a destination claims. Primary is the default and the one to spend deliberately.
+Never for: Ranking every link on a page against every other. Three tiers is the whole vocabulary here on purpose — a set of unjustified tiers is what the previous Button was deleted for. And never inverse on the ordinary page ground: against it the fill carries roughly six times the contrast of the brand, so the primary beside it stops reading as the primary and one-primary-per-view is broken without a second primary anywhere in sight.
+
+### size — `sm` | `md` | `lg` (default `lg`)
+
+- `sm` — A dense band where the button is one control among several — a filter row, a utility bar, an action beside body copy. size.control.sm tall against space.control.sm on the sides, half of it as at every step. The label holds at font.label.sm, md's own 14px: the label ramp has no step below it, so what separates these two is the box. Desktop only — at thirty-two it is below what a finger reliably hits.
+- `md` — The default, and everything that is not a hero — navigation bars, pricing rows, feature sections, footer bands. size.control.md tall against space.control.md on the sides, which is half of it, and font.label.sm — the 14px step, so the label matches product's default button rather than running a size above it.
+- `lg` — A hero, or a full-width conversion band that is the only control in view. size.control.lg tall against space.control.lg on the sides, again half the height, so the label starts where the pill's curve stops. font.label.md at 16px, product's own large-button measure. One per page, usually: a page of lg CTAs has no hero.
+
+Use when: Matching the control to the density of the band it sits in, which on a marketing page is set by the section rather than by the button.
+
+### tone — `default` | `inverse` | `brand` (default `default`)
+
+- `default` — The page's own ground, which sets the ink this component was drawn against — every button on a white page
+- `inverse` — The control stands on the dark band, color.bg.brand-strong — a hero, a navigation bar at the top of one, a footer — which is the same near-black in light and dark. The secondary keeps its filled shape: a six-percent white tint with hover and press layered over it, and the label in color.fg.on-brand-strong. Every value is fixed, because the band is.
+- `brand` — The control stands on the coral band, color.bg.brand — CtaBanner and CtaBannerSlider — which is the same coral in light and dark, so nothing on it switches either. variant="inverse" is a near-black pill with a white label in both themes, rather than turning white in dark beside a white secondary; the secondary is the same six-percent white tint it is on the dark band. Hover, press and the focus ring are the dark band's fixed values.
+
+### href — `string`
+
+Use when: The press goes somewhere with a URL of its own — the ordinary case for a call to action on a marketing page. It makes this an anchor rather than a button, which is what gives a visitor cmd-click, a visible destination and a copyable link. `target` and `rel` are not props: the component is typed against AnchorHTMLAttributes, so they are already in reach and land on the anchor.
+Never for: A placeholder while the destination is undecided — a # or an empty string is a control that looks live, takes focus and goes nowhere. Nor javascript: or a handler dressed as a URL: leave href out and pass onClick, and this renders a button that does the work in place.
+
+### showIcon — `boolean` (default `false`)
+
+Use when: Where the destination continues a sequence rather than being simply somewhere else to go — the hero CTA that starts a signup, the button at the foot of a step. Named for the part it renders rather than for the mark inside it: which glyph that is belongs to the component, the way showClose and showTitle name their parts elsewhere. Today it is a forward arrow, and it slides on hover.
+Never for: Every button in a section. The mark says "this continues" and is worth something only while it points at the one control that does; on four at once it is decoration and the reader stops reading it.
+
+Also accepts everything from `AnchorHTMLAttributes<HTMLAnchorElement>`.
+
+## 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.
+
+- **The hero call to action at the top of a landing page — the one step the page exists to produce** — `variant="primary"` `size="lg"`
+  A hero is read at a distance and often on a page with no other control, so the CTA carries the brand fill at the largest step the scale offers. lg is the only place font.label.lg is bound, and its role description names hero CTA buttons as the case it was cut for.
+- **A call to action in a sticky navigation bar, a pricing row or a footer band** — `variant="primary"` `size="md"`, not `size="lg"`
+  These bands are sized by the page rather than by the button, and lg stands a step taller by size.control.lg — taller than the copy beside it in a nav bar or a pricing row, which is the one place a hero measure is wrong.
+- **The lesser of two destinations offered together — Compare plans beside Sign up** — `variant="secondary"` `size="md"`, not `variant="primary"`
+  Two brand fills side by side ask the visitor to choose between two things that look equally urgent, which is the one-primary-per-view rule. Secondary keeps the shape and the target size and gives up the fill, so the pair reads as a route and an alternative rather than as two demands.
+- **A call to action inside a section that paints its own ground — a brand-coloured hero, a photo band, a dark takeover** — `variant="inverse"` `size="lg"`, not `variant="primary"`
+  The brand fill is invisible against a brand ground and a neutral edge is the wrong ink over a photograph, so inverse is the only tier that reads there. It is also the one place its contrast is not a problem: it outranks the page's primary, and the page's primary is not in the band.
+- **A shaped call to action that begins a sequence rather than merely going somewhere — the hero button that opens a signup flow** — `variant="primary"` `size="lg"` `showIcon`
+  The mark means "this continues", which the pill does not say on its own. Worth one per section and no more: on every button at once it stops being read and becomes decoration.
+
+## 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`
+- `Enter` — press it. A button and an anchor both answer Enter, so this reads the same either way
+- `Space` — press it, where it is a button. An anchor does not answer Space, and that difference belongs to the element rather than to this component — a visitor who knows the difference is told which by how it was announced
+- accessible name
+- focus-visible ring
+- an href that resolves, wherever one is given — an anchor without a real destination is announced as a link and goes nowhere
+- a label that names the destination or the action rather than the gesture, because a page of controls read out of context as "click here" names nothing
+
+## 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.
+- **Destructive actions require a confirmation step** *(applies to a variant not built yet)* — An irreversible action taken by mis-click has no recovery path. The confirmation must name what will be lost, not merely ask whether the user is sure.
+  Guidance only — cannot be checked automatically.
+- **A navigation bar holds at most two buttons: one primary, and one secondary beside it** — The bar's actions are the conversion and the way back in for a reader who already has an account — sign up and log in. That is two things, and they rank: the one the site wants is primary and the other is secondary. A third button is a third thing the bar is asking for, and a row of three pills beside a mark and a set of destinations stops reading as a pair of actions and starts reading as a second navigation.
+
+A single button is the primary. Alone, there is nothing for a secondary to be quieter than, and a bar whose only action is the quiet one has hidden the thing it exists to offer. Two buttons are one primary and one secondary, never two of either: two primaries are two demands, and two secondaries leave the reader to guess which one the site meant.
+
+A switcher is not a button here — a DropdownMenu or a ButtonIcon for the language or the theme — and does not count against the two.
+
+Guidance rather than a count. The bar is drawn with a second copy of an action in compactAction for narrow widths, and a count of Buttons under Navbar cannot tell that slot from utilities or a ranked pair from two primaries. Navbar checks the pair itself, on what utilities is handed, and says so in the console.
+  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.
+- **At most one primary button per view** — Two primary actions compete for attention; the user cannot tell which one the system wants them to take.
+  Machine-checkable — `dds lint` will enforce this once built.
+- **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
+
+❌ Button for: The action belongs to an application surface — a trade form, a settings panel, a confirmation that removes something
+   That is @deriv-com/dds-product's Button, which carries the loading state, the destructive tier and the density an application needs. This one stops at the three tiers a marketing page ranks its calls to action by.
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+❌ Button for: The words belong inside a sentence or a paragraph of body copy
+   A control shaped like a button interrupts prose, and a pill in the middle of a line breaks the line's rhythm. An inline destination is a Link, which takes its size and ink from the copy around it rather than this component shrunk down until it stops looking like a button.
+   → use `Link` instead.
+
+❌ Button for: The control is a glyph alone, with no words
+   This component's words are its accessible name, and there is nowhere else to put one — a glyph with no label beside it ships unnamed. ButtonIcon is that case, split out the way product split it out of its own Button: it carries a `label` prop that is never drawn, so the control is named for a screen reader without any words being set on the page. It takes the same three tiers and the same two steps as this component, so a glyph-alone control and a labelled CTA in one band rank against each other in one vocabulary.
+   → use `ButtonIcon` instead.
+
+❌ variant=primary + tone=brand
+   The primary is the coral fill, and tone="brand" says the button stands on the coral band: coral on coral is a button nobody can see. On the band the primary action is variant="inverse".
+
+## Example
+
+```tsx
+import { Button } from '@deriv-com/dds-marketing'
+
+<Button href="/signup">Create free demo account</Button>
+```
+
+## In use
+
+### The two page tiers
+
+What decides the tier is not how important the destination feels but how many the section already has. Primary means something only while it is the one.
+
+```tsx
+import { Button } from '@deriv-com/dds-marketing'
+
+// Primary — the step the page exists to produce
+<Button href="/signup">Create free demo account</Button>
+
+// Secondary — a destination that is not the one pushed
+<Button variant="secondary" href="/pricing">Compare plans</Button>
+```
+
+### The three sizes
+
+Set by the band the control sits in rather than by the button. lg is for a hero; sm for a dense desktop row; everything else is md.
+
+```tsx
+import { Button } from '@deriv-com/dds-marketing'
+
+// Small — a filter row or utility bar, desktop only
+<Button size="sm" href="/signup">Get started</Button>
+
+// Medium — navigation bars, pricing rows, footer bands
+<Button size="md" href="/signup">Get started</Button>
+
+// Large — a hero, usually the only control in view
+<Button size="lg" href="/signup">Create free demo account</Button>
+```
+
+### A route and its alternative
+
+Two destinations offered together. The tiers differ and the box does not, so the pair lines up whichever way round a section puts them.
+
+```tsx
+import { Button } from '@deriv-com/dds-marketing'
+
+// The route being pushed
+<Button href="/signup">Open a live account</Button>
+
+// The alternative, same height and same inset
+<Button variant="secondary" href="/demo">Try the demo first</Button>
+```
+
+### The band tier
+
+For a section that paints its own ground — a brand hero, a photo band, a dark takeover. It sits here on the page, which is the one ground it must never sit on: there it outranks the primary.
+
+```tsx
+import { Button } from '@deriv-com/dds-marketing'
+
+// Inverse — belongs on a band, not on the page
+<Button variant="inverse" href="/signup">Create free demo account</Button>
+```
+
+### The mark on a shaped tier
+
+Tertiary renders it always. A pill can ask for it where the destination continues a sequence rather than merely being somewhere else to go — one per section, or it stops being read.
+
+```tsx
+import { Button } from '@deriv-com/dds-marketing'
+
+// Primary, asking for the mark
+<Button showIcon href="/signup">Start your application</Button>
+```
+
+### On a ground the section painted
+
+tone="inverse" keeps the fill on a ground that runs against the mode. On the coral band, tone="brand" holds the near-black primary and the tinted secondary still in both themes.
+
+```tsx
+import { Button } from '@deriv-com/dds-marketing'
+
+// secondary — on the page's ground
+<Button href="/signup" variant="secondary">Create free demo account</Button>
+
+// secondary, tone="inverse" — a ground against the mode
+<Button href="/signup" variant="secondary" tone="inverse">Create free demo account</Button>
+
+// inverse, tone="brand" — on the coral band
+<Button href="/signup" variant="inverse" tone="brand">Open account</Button>
+```