@deriv-com/dds-marketing 0.2.0 → 1.0.0

package/.llm/components/pageheader.md

@@ -0,0 +1,231 @@
+<!-- GENERATED from page-header.contract.json. Do not edit. -->
+
+# PageHeader
+
+The band that opens a company or a legal page: the page's name, a line saying what it is, and nothing else.
+
+The third of three opening bands and the only one that is not a hero. It is capped rather than a screen tall, which is the whole difference — a reader arrives at Contact or Terms for the content, and a full-height band would be a wall in front of the first sentence.
+
+There is no photograph; there is nothing to show on a page of terms. What it paints instead is a faint rule grid, enough to say the band is deliberate rather than a gap.
+
+## Use when
+
+- A company, legal or support page needs its opening band — contact, about, terms, a regulatory notice
+- The page is read rather than acted on, so its opening should name it and then get out of the way
+- The steps between an eyebrow, a title and a description have to be the same on every such page
+
+## Do not use
+
+- The page is the front page, or a campaign page under it → `LandingHero`
+- The page is a product or a market page → `ProductHero`
+- The band closes the page rather than opening it → `Footer`
+- A landing or product page. Each tier has its own band, and the reason they are separate components is so that this cannot be overridden
+- Carrying a photograph or a product shot. This tier has no visual slot, which is a decision rather than an omission — a page of terms has nothing to show
+- The navigation above it or the trail beneath that. Both are the page's and neither is the band's
+
+## Anatomy
+
+PageHeader renders 8 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-pageheader`. The band. It paints the ground and the rule grid over it, and clips anything that overruns to its own edge. `container-type` is what its own rules ask their width against, so a band placed in a narrow region of a wide page folds on its own measure rather than the window's.
+- `inner` — `<div>`, class `dds-pageheader__inner`. The measure, and the gutter. It caps the content at the page's own maximum and holds the page inset, which is what keeps the band's text in the same column as the content under it. The full section step, space.section.default, the same air every band above and below it keeps — the band is at least size.band.compact tall, and the step is part of that height rather than added to it.
+- `content` — `<div>`, class `dds-pageheader__content`. The column the band is read down: the text, then what a reader can do about it. One step between them, because the move from reading to acting is the same move on every page. It takes the whole measure rather than hugging its longest line: `inner` is a flex row, so a column that declared no width would shrink to its text and sit at the leading edge — which centring inside it cannot correct, because the box being centred in is already the wrong shape.
+- `text` — `<div>`, class `dds-pageheader__text`. The eyebrow, the title and the description, in that order, held to a heading's measure rather than the page's. It sets no gap of its own: the step from an eyebrow to a title and the step from a title to a description are two different roles, and a single gap could only ever be one of them. Each part carries its own.
+- `eyebrow` — `<p>`, class `dds-pageheader__eyebrow`. The line above the title. Set at label weight rather than body, because it is a label — a reader takes it in without reading it, and at regular weight it reads as a first sentence the title then interrupts.
+  
+  Set in `font.eyebrow.lg`, which is sized against the heading under it rather than against body text. It took an interactive text role for a while and read as small print over a display title — the same sixteen pixels a button's label takes, under eighty. Rendered only when `eyebrow` is set.
+- `title` — `<h1>`, class `dds-pageheader__title`. The page's leading heading, and the band's accessible name. It renders as `h2` when `headingLevel` says so and is set identically either way. `text-wrap: balance` because a two-line title broken one-word-short reads as a mistake at this size, where at body size nobody would notice.
+- `description` — `<p>`, class `dds-pageheader__description`. The sentence under the title. Held to a readable measure rather than the band's — a line of sixteen-pixel text run across twelve hundred pixels is a line a reader loses their place in, and the measure role exists so no page has to guess where to stop it. Rendered only when `description` is set.
+- `actions` — `<div>`, class `dds-pageheader__actions`. What a reader can do. It wraps rather than scrolls, because two full-width buttons on a phone are two rows and a row that scrolled sideways would hide the second one. Rendered only when `actions` is set.
+
+Apply these classes from the generated `pageHeaderParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `PageHeader`, `LandingHero`, `ProductHero`, `Footer`, `Navbar`, `SubdomainNavbar`, `Table`, `Accordion`, `BottomSheet` — in children or in any prop that takes a node
+
+## Props
+
+### eyebrow — `string`
+
+Use when: A word or two placing the page before its title names it — a product family, a market, a campaign
+Never for: A second sentence. This is the line a reader takes in without reading; at the length of a clause it is a description in the wrong place and at the wrong weight
+
+### title — `string` **Required.**
+
+Use when: Always. The one thing the page is about, in the fewest words that still say it. It is the page's leading heading and the band's accessible name
+Never for: A sentence with a full stop. A title that reads as prose is a description that has been set at eighty pixels
+
+### headingLevel — `h1` | `h2` (default `h1`)
+
+- `h1` — The default, and correct whenever the hero opens the page — which is what a hero is for
+- `h2` — The rare page that already carries its `h1` elsewhere, and would otherwise have two
+
+Use when: Which heading element the title renders as. The default is right for the band a page opens with, which is the only place this belongs.
+
+The appearance never changes — both levels bind `font.h1`, because the size is the band's decision and the level is the document's.
+Never for: Making the title look smaller. The level is what a screen reader builds its outline from, and nothing about it reaches the type
+
+### description — `string`
+
+Use when: The sentence under the title that says what the claim above it means, for the reader who is not yet convinced by the claim alone
+Never for: A paragraph. It is held to a readable measure and set at body size; past a couple of sentences a reader scrolls rather than reads, and the actions go under the fold
+
+### actions — `node`
+
+Accepts: Button, Link
+Use when: The one or two things the page wants a reader to do. Composed by the page rather than described to this component, so a call to action is the same Button here as anywhere else on the site
+Never for: A row of destinations. Three or more controls under a title is a menu, and a reader who has to choose between five things chooses none
+
+## Accessibility
+
+Guaranteed by the component. Write none of it by hand: the ids these attributes point at are generated per instance, so an attribute set from outside either says the same thing twice or points at nothing.
+
+- Announced as: `region`
+- `Tab` — Moves through whatever the actions hold, in the order the page composed them. Nothing in the band is a composite widget — there is no roving tabindex and no arrow keys, because a hero is read rather than operated.
+- accessible name from title, so the band is a named region a screen reader can jump to and skip rather than an unlabelled section a reader has to walk
+- The title renders as h1 by default and h2 only where the page already carries its h1. Nothing about the level changes the type, so a page cannot be tempted to choose it for the size
+
+## Rules
+
+- **On a phone a section's actions stack and each fills the width, including when there is only one** — On a phone a page's actions stack, and each one fills the width. Not most of it, and not the width its label happens to need — the whole column.
+
+Two side by side is what this replaces. On the narrowest screen each gets half a column minus the gap, which is rarely enough for a real label: the words wrap inside the pills, the two buttons come out different heights, and the pair reads as a broken row rather than as a choice. Stacked, each has the whole width and neither has to shorten its words to fit.
+
+A single action fills too, and that is the part worth saying, because it is the one that looks unnecessary. A lone button has the room to sit at its natural width and still should not: a full-width control is the phone's convention for the thing the screen is asking you to do, and a pill hugging its label reads as one option among others that are not there. It also makes the target predictable — the whole width, wherever the thumb lands — which a centred pill does not.
+
+Filling is the row's job rather than the button's. A button has no width of its own and is not given one; the row it sits in becomes a column and stretches its children, so nothing about the control changes and the same button is full width here and its own size on a desktop.
+
+This is the phone's breakpoint, size.breakpoint.md, and not the wider one that decides whether a heading is centred. Those are different questions and they break at different widths: a heading stops being centred when the measure is the screen, while a button stops being full width much sooner than that — stretched across a tablet it is a long way from its own label, and a label centred in a metre of pill is harder to hit than one in a pill the size of the words.
+
+What this is not about is every row of controls. A set of filter chips, a pagination strip, a toolbar, a link sitting after a sentence — none of these is the page asking for something, and stacking them to full width would turn a strip the eye skims into a list it has to read. The test is whether the row is the call to action the section was written for.
+  Guidance only — cannot be checked automatically.
+- **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, Input and Switch simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+- **A component is written along the reading axis, not along the page's left and right** — Every measure, inset and placement in this package names an axis rather than a side: inline-size and block-size, padding-inline and padding-block, inset-inline-start and inset-block-end, margin-inline: auto, text-align: start. Written that way a component follows whichever direction the page is read in, and a band whose claim ranges to the leading edge with its subject on the trailing one is the same composition in Arabic as in English, mirrored, with nothing restated. Written as left and right it is the same pixels in both, which is a layout nobody designed for the second language.
+
+The enum values follow the same rule and for the same reason. A prop that names where a picture sits takes start and end, never left and right — FeatureSplit, FeatureBullets and FeatureScroll all declare mediaPosition that way, and the flex directions they generate flip on their own because row already means the reading order. A value called left would have to be re-read as right by every author working in a mirrored page, which is a translation this system should be doing rather than asking for.
+
+The guidance a contract carries is part of the component, so it follows too. Describing a claim as ranging left is describing one of the two languages, and it was written that way here for a while: three of the opening bands said so in their own intent. A reader in a mirrored page meets that sentence and has to decide whether the component is wrong or the sentence is, and neither answer is one documentation should force.
+
+Two things genuinely have no logical form and are not covered by this. A CSS gradient takes a physical direction — there is no to inline-end — so a pattern that must mirror has to be stated twice under a direction query, and one that is periodic and centred, like PageHeader's rule grid, does not need to. A glyph that points the way onward is the other: an arrow is a picture of a direction, and mirroring it belongs to the icon set rather than to the component holding it.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ PageHeader for: The page is the front page, or a campaign page under it
+   The landing tier, a screen tall, with the claim ranged to the reading edge and a subject beside it
+   → use `LandingHero` instead.
+
+❌ PageHeader for: The page is a product or a market page
+   The product tier, a screen tall, with the product itself under the claim
+   → use `ProductHero` instead.
+
+❌ PageHeader for: The band closes the page rather than opening it
+   → use `Footer` instead.
+
+## Example
+
+```tsx
+import { PageHeader } from '@deriv-com/dds-marketing'
+
+<PageHeader title="Contact us" description="Got questions? Here's how to get answers." />
+```
+
+## In use
+
+### The band as a page has it
+
+A name and a line saying what the page is. No photograph and nothing to press — the reader came for the content, and it starts directly under this.
+
+```tsx
+import { PageHeader } from '@deriv-com/dds-marketing'
+
+// Contact
+<PageHeader title="Contact us" description="Got questions? Here's how to get answers." />
+
+// A legal page, named and nothing more
+<PageHeader title="Terms and conditions" />
+```
+
+### How much the band carries
+
+Every part but the title is optional, and the steps close up rather than leaving a gap where a part would have been.
+
+```tsx
+import { Button, PageHeader } from '@deriv-com/dds-marketing'
+
+// Title alone
+<PageHeader title="Terms and conditions" />
+
+// Title and description
+<PageHeader title="Regulatory information" description="The licences Deriv holds, the entities that hold them, and what each one covers." />
+
+// With an eyebrow and somewhere to go
+<PageHeader eyebrow="Support" title="Help centre" description="Answers to the questions we are asked most, and a way to reach us when none of them fit." actions={<Button variant="primary">Contact support</Button>} />
+```
+
+### The document's outline
+
+The title is the page's leading heading. `headingLevel` changes the element a screen reader builds its outline from and nothing about the type.
+
+```tsx
+import { PageHeader } from '@deriv-com/dds-marketing'
+
+// h1 — the default, and what a band opening a page is
+<PageHeader headingLevel="h1" title="Contact us" description="Got questions? Here's how to get answers." />
+
+// h2 — the page already carries its h1 elsewhere
+<PageHeader headingLevel="h2" title="Contact us" description="Got questions? Here's how to get answers." />
+```

package/.llm/components/pagination.md

@@ -11,42 +11,30 @@ What separates this from product's is what a press is. A page of an index has an
 - An index or archive has been split across pages and the reader needs to move through it — a blog listing, a news archive, a resource library. It belongs below the results, because the decision to move on is one the reader makes after reading what is here
 - The reader needs to reach a particular page rather than step towards it — page fourteen of forty, in one press. That is the pages variant, and the only one offering a target with a number on it. Where the row has no room for that number, the break standing in for it opens a menu of the pages it hides, so a page the row cannot show is two presses away rather than a walk
 - The pages have addresses a search engine should follow. Numbered targets drawn as links are how an index gets crawled past its first page, which on a marketing site is usually the reason the index exists
-- How much is left matters as much as where the reader stands. A total passed to the count variant turns the readout from a position into a measure, which is what tells someone whether to keep reading or search instead
-- The reader is walking a short visual sequence and what they want to know is where they are in it rather than what that position is called — a carousel of cards, a testimonial slider, a walkthrough. That is the dots variant, and it holds while the set stays under about ten: a dot carries no number, so past a handful the reader is counting marks too small and too many to count
 
 ## Do not use
 
+- A short sequence the reader moves through — a slider's slides, a carousel of cards, a walkthrough → `PaginationDots`
 - The reader is moving between views of one page rather than through one long set → `TabList`
 - More results are appended to the view as the reader reaches the end, rather than one page replacing another → `Button`
 - The reader is hunting for one row among thousands rather than walking the set → `SearchInput`
 - A set that fits on one page. There is nothing to move between, and a control offering to move is read as a promise that there is more — so the reader presses it, nothing happens, and they are left unsure whether the control or the results are at fault
 - Placing above the content it governs. The reader decides whether to move on only after seeing what is here, so a control above the results asks the question before they hold the answer — and on a long page it puts the control off screen at exactly the moment they want it
-- Ten or more positions under the dots variant. A dot carries no number, so a reader working out where they are is counting marks; past a handful the marks are too small and too many to count, and the row degrades into saying only "somewhere in the middle"
 - Standing in for a filter. Handing a reader four hundred pages is not giving them access to the set, it is giving them the shape of it — the answer is a narrower query, and pagination is what works once the set is small enough to walk
 
 ## Anatomy
 
-Pagination renders 8 elements. A token binding names the part it applies to.
+Pagination renders 6 elements. A token binding names the part it applies to.
 
-- `root` — `<nav>`, class `dds-pagination`. The nav landmark the control sits in, and the layout decision for it. A nav because a reader listing a page's landmarks is looking for the way through the results, and an unnamed row of buttons is not something they can find. It paints nothing: its only choice is that the two step controls flank whatever the middle holds, centred, wherever they are drawn — and showSteps is the one thing that takes them away, for a set the reader moves through by swiping cards or images and this only reports. One skeleton rather than the more familiar split layout, where the readout sits at one edge and the steps at the other — that needs the steps wrapped together, which would make a step's declared parent true in some variants and false in others. Flanking keeps the controls where the reader's hand left them as the variant changes. It never exceeds the width it is given, and what gives when the row outgrows it is the window rather than the layout. The row measures what it has — the width left once the two step controls have taken theirs, against the widest slot the set can draw — and shows as many siblings as that holds, down to none, which is the five-slot row of the two ends, two breaks and the page the reader is on. This is the one thing the component measures and the one thing it holds of its own, because the container's width is a fact no consumer can pass it. It is measured rather than compared against a threshold in pixels: a numbered target is a Button, so how much room a digit takes is Button's padding and the loaded font, neither of which this component owns. Below the shortest row — first page, break, current page, break, last page — the list is what gives: it shrinks below its contents and scrolls, while the two steps hold their size, because a centred flex row with nothing allowed to shrink overflows in both directions at once, which put the back control on top of whatever sat to the left and the forward one outside the container entirely. That last degrade is a scroller with a page cut in half at the edge of it, which a reader cannot tell from a broken control — so it is where a column too narrow for numbers should have been given count or compact instead.
-- `list` — `<div>`, class `dds-pagination__list`. The row of targets between the two step controls: numbered pages under the pages variant, position marks under dots, and nothing at all under the rest, where the readout takes this place. A div rather than an ol, deliberately — an ordered list may hold only li elements, so each target would need a wrapper, doubling the anatomy to buy semantics the nav landmark and aria-current already provide.
-  
-  Under pages it holds Buttons, which in this package are anchors: each carries the address of the page it names, so a visitor can cmd-click one, see where it goes, and a crawler can follow it. They are secondary and transparent, with the current one dropping its transparency so it alone carries a ground. Under dots it holds this component's own marks, which are buttons — a slide has no address to point at.
-- `summary` — `<span>`, class `dds-pagination__summary`. The readout, in place of the row of targets, under two variants and reading differently in each. Count answers how much is left: a range against a total. Compact answers only where the reader stands and drops the words to do it, reading "3 / 24", which is the terseness the variant exists for.
-  
-  Label text rather than body, which is the opposite of the choice product made and deliberate. This package's body ramp is page copy — its small step is described as the legal line at the foot of a section — and a readout set in it reads as small print rather than as part of the row of controls it sits between. label is this package's text for chrome: semibold, tight, and the same measure the controls either side of it carry. At the default foreground, because it reports a fact rather than offering one. Rendered only when `variant` is set.
-- `dot` — `<button>`, class `dds-pagination__dot`. One position in a short sequence, under the dots variant alone. The button is the target and not the mark: a dot at the size a dot should be is about eight pixels, a third of what WCAG asks of anything a pointer must hit, so the pressable box is held at size.target.min and the visible circle is a child of it — while the marks are the only way through the set. Growing the dot to twenty-four instead would produce the pages variant with the numbers taken out.
-  
-  That target is also what made a long row too wide for a phone: twenty of them is four hundred and eighty pixels before the steps have taken theirs. So the box narrows to the mark's own width while the steps are drawn beside it, which is a twelve-pixel pitch with the gap and fits twenty marks and both steps inside a phone. The exception is the one WCAG names rather than one of ours: an undersized target is allowed where the same function is reachable by a control that meets the size, and the steps are that control — every position the marks offer is reachable by pressing them. Take the steps away and the exception goes with them, so the box returns to the full target, and the width the steps were taking pays for it. It is the block axis that stays either way: a shorter box would cost hit area on the axis that was never the problem. It paints nothing of its own but the focus ring — its ground stays transparent through hover and press, and what it carries instead is the colour the mark paints with. A ground here drew a filled circle three times the mark's width under the pointer, which reads as a control appearing around the dot rather than as the dot answering, and at the tightest gap the scale offers those grounds nearly touched their neighbours'. Holding the colour rather than the ground is also the only way the mark can answer at all: hover belongs to whatever the pointer is over, the target is this button, and a span is never hovered as a target. So every state the reader sees on the mark — at rest, under the pointer, pressed, current — is declared here, and the mark inherits it. Round for the focus ring's sake, which is the one thing it still draws around itself.
-  
-  Its four colours are product's own, reached through roles that do not sound like it. The mark steps through solid greys toward the page the reader is on — E6E8EA at rest, D8DADD under the pointer, BDC0C5 pressed, black when current — which is exactly product's ramp in light. This package has no neutral mid-grey roles to say that with, so the two middle steps borrow color.bg.readonly and color.border.default for their values. The names are wrong and the pixels are right, which is the trade taken knowingly: the alternative was color.bg.hover and color.bg.active, whose names fit perfectly and whose values are alpha overlays meant to sit behind something — bound to a foreground they rendered the mark at five per cent black, which is a dot that disappears under the pointer. Naming these two properly is a small addition to the colour layer and the right fix; until then this comment is the record that they were chosen rather than mistaken. Rendered only when `variant` is set.
-- `dot-mark` — `<span>`, class `dds-pagination__dot-mark`. The circle the reader actually sees, centred in a target three times its width. It carries the current position by a change of ground rather than of size: a dot that grows moves its neighbours, and a row that reflows as the reader steps through it is a row they must re-read. Its ground is currentcolor and so is every state of it — the recessive fill at rest, a step up under the pointer, a step further pressed, and when current the strongest the page can carry, which is the widest separation two solids in this system have and what survives being eight pixels across. The colour is the button's because the states are: this is a span inside the target rather than the target, so it cannot be hovered as one, and a fill bound here would have sat still while the thing the reader was pointing at changed. Nothing else about it moves, which is the point — the mark answers by darkening where it is. Rendered only when `variant` is set.
+- `root` — `<nav>`, class `dds-pagination`. The nav landmark the control sits in, and the layout decision for it. A nav because a reader listing a page's landmarks is looking for the way through the results, and an unnamed row of buttons is not something they can find. It paints nothing: its only choice is that the two step controls flank whatever the middle holds, centred, wherever they are drawn. One skeleton rather than the more familiar split layout, where the readout sits at one edge and the steps at the other — that needs the steps wrapped together, which would make a step's declared parent true in some variants and false in others. Flanking keeps the controls where the reader's hand left them as the variant changes. It never exceeds the width it is given, and what gives when the row outgrows it is the window rather than the layout. The row measures what it has — the width left once the two step controls have taken theirs, against the widest slot the set can draw — and shows as many siblings as that holds, down to none, which is the five-slot row of the two ends, two breaks and the page the reader is on. This is the one thing the component measures and the one thing it holds of its own, because the container's width is a fact no consumer can pass it. It is measured rather than compared against a threshold in pixels: a numbered target is a Button, so how much room a digit takes is Button's padding and the loaded font, neither of which this component owns. Below the shortest row — first page, break, current page, break, last page — the list is what gives: it shrinks below its contents and scrolls, while the two steps hold their size, because a centred flex row with nothing allowed to shrink overflows in both directions at once, which put the back control on top of whatever sat to the left and the forward one outside the container entirely. That last degrade is a scroller with a page cut in half at the edge of it, which a reader cannot tell from a broken control — so it is where a column too narrow for numbers should have been given compact instead.
+- `list` — `<div>`, class `dds-pagination__list`. The row of targets between the two step controls: numbered pages under the pages variant, and nothing at all under the rest, where the readout takes this place. A div rather than an ol, deliberately — an ordered list may hold only li elements, so each target would need a wrapper, doubling the anatomy to buy semantics the nav landmark and aria-current already provide. Under pages it holds Buttons, which in this package are anchors: each carries the address of the page it names, so a visitor can cmd-click one, see where it goes, and a crawler can follow it. They are secondary and transparent, with the current one dropping its transparency so it alone carries a ground.
+- `summary` — `<span>`, class `dds-pagination__summary`. The readout, in place of a row of targets. Under compact it answers only where the reader stands and drops the words to do it, reading "3 / 24", which is the terseness the variant exists for. Label text rather than body, which is the opposite of the choice product made and deliberate. This package's body ramp is page copy — its small step is described as the legal line at the foot of a section — and a readout set in it reads as small print rather than as part of the row of controls it sits between. label is this package's text for chrome: semibold, tight, and the same measure the controls either side of it carry. At the default foreground, because it reports a fact rather than offering one. Rendered only when `variant` is set.
 - `step` — `<button>`, class `dds-pagination__step`. One of the two step controls, drawn by this component rather than borrowed. Product hands this job to ButtonIcon; this package's ButtonIcon has no disabled and says so in its own source — it is a link family, and a link cannot be disabled, which is a correct decision there and an unusable one here. A step at the end of the set must be disabled rather than removed: removing it shifts every remaining target sideways at the moment the reader is aiming at one.
   
   An <a> when the component was given pageHref and a <button> when not, which is the rule ButtonIcon and CardButton already follow. At the first or last page there is no page to point at, so the anchor becomes a disabled button rather than a link to nowhere — the only place the two modes meet.
 - `page` — `<button>`, class `dds-pagination__page`. One numbered target, under the pages variant. An <a> when given pageHref and a <button> when not, the same rule the step follows.
   
-  Drawn here rather than taken from Button, which was the intention until Button turned out not to fit: it is an anchor with a required href, so it cannot be a press the page handles, and its quiet form does not exist — the variants are primary, secondary and inverse, none of them the transparent target a row of page numbers wants. A page number is not a call to action, and a row of them set as one reads as a row of offers rather than a position.
+  Drawn here rather than taken from Button, which was the intention until Button turned out not to fit: it was then an anchor with a required href, so it could not be a press the page handles, and its quiet form does not exist — the variants are primary, secondary and inverse, none of them the transparent target a row of page numbers wants. A page number is not a call to action, and a row of them set as one reads as a row of offers rather than a position.
   
   Declared unconditional though it is drawn under the pages variant alone, which is the one place this anatomy is less precise than the component. presentWhen marks a part absent by default and present once a prop is set; this part is the opposite — pages is the default, so it is there on a bare render and gone under the other three. Saying presentWhen: variant would generate a test asserting it is missing from the default row, where it is the row. The break beside it does not have the problem, needing a set long enough to break before it appears at all.
 - `break` — `<button>`, class `dds-pagination__break`. The control standing between two runs of numbered pages, which presses: it opens a menu of exactly the pages the row had no room to draw.
@@ -64,19 +52,11 @@ Apply these classes from the generated `paginationParts` constant rather than wr
 
 ## Props
 
-### variant — `pages` | `count` | `compact` | `none` | `dots` (default `pages`)
+### variant — `pages` | `compact` (default `pages`)
 
 - `pages` — An index or archive whose pages have addresses of their own — a blog listing, a news archive, a resource library. The only variant offering a numbered target, so the only one on which reaching page fourteen costs a single press rather than thirteen, and the only one a crawler can follow past page one. It draws Buttons, which in this package are anchors, so it needs pageHref and the pages it points at have to exist as URLs. A page too far out to be drawn is still not a walk: the break between two runs of numbers presses, and offers the pages it stands for
-- `count` — A long set where the reader's real question is how much is left rather than which page they are on — "page 3" says nothing until you know whether there are four pages or four hundred. Pass totalItems so the readout can answer it. The steps take pageHref where the pages have addresses and fall back to onPageChange where they do not
-- `compact` — A place with no room for a row of numbers — a card footer, a sidebar, a column at a phone's width. Position and the two steps, and nothing else. Like count, its steps are anchors given pageHref and buttons without it
-- `none` — The two steps and nothing between them, for a place where position is either obvious or beside the point — a lightbox moving through images, a set of two. It is the least this component can be, and choosing it is a claim that the reader does not need to know where they are, which on a page with an address per position is a claim worth making deliberately
-- `dots` — A carousel of cards, a testimonial slider, a walkthrough — a short visual sequence where the reader cares where they are rather than what that position is called. The marks are always buttons and the press is always the page's to handle, a slide having no address to link to; pageHref is ignored here rather than obeyed. The case it was built for is a set the reader swipes: pass showSteps={false} there and the row is marks alone, which is also the only variant still offering a target once the steps are gone. Keep the set under about ten — a dot carries no number, so beyond a handful the reader is counting marks too small and too many to count
-Never for: Choosing by the width available rather than by the reader's question. The five answer different questions, and which one is being asked comes from the content above the control, not the room beneath it. Reaching for compact because a row of numbers will not fit is the one defensible inversion — and still a narrowing of what the reader can do, not a neutral swap
-
-### showSteps — `boolean` (default `true`)
-
-Use when: Whether the two step controls are drawn, under the dots variant. True wherever this component is the way through the set, which is nearly all of them. False for a set the reader moves through some other way and this only reports — a carousel they swipe, a gallery with its own arrows — where a second pair underneath competes with the first. Dropping them also buys the width that lets a long row of marks fit a phone
-Never for: Any variant but dots, where it is inert rather than obeyed — the same as siblingCount under count, or totalItems under pages. Dots is the only middle holding targets of its own, so it is the only row that still works once the arrows go. The type cannot say so: an exclusion names one prop and one value, and there is no way to write one naming five variants at once
+- `compact` — A place with no room for a row of numbers — a card footer, a sidebar, a column at a phone's width. Position and the two steps, and nothing else. Like pages, its steps are anchors given pageHref and buttons without it
+Never for: Choosing by the width available rather than by the reader's question. The two answer different questions, and which one is being asked comes from the content above the control, not the room beneath it. Reaching for compact because a row of numbers will not fit is the one defensible inversion — and still a narrowing of what the reader can do, not a neutral swap
 
 ### page — `number` (default `1`)
 
@@ -86,27 +66,17 @@ Never for: Half a controlled component. Passing this without updating it when on
 ### totalPages — `number` (default `1`)
 
 Use when: How many pages the set has been divided into. It decides where the row ends, when the ellipsis appears, and when next goes disabled. The default of one is the honest answer for a set nothing has been said about, and it is also the case the component should not be used in at all — a single page has nothing to move between
-Never for: A count of items. That is totalItems, and passing one for the other gives a reader four hundred page numbers for forty pages of results. Nor for an unknown total: a number invented so the component would render is a promise about how much is left, and the reader has no way to tell it from a real one
+Never for: A count of items. Pages, not results: passing the number of results gives a reader four hundred page numbers for forty pages of them. Nor for an unknown total: a number invented so the component would render is a promise about how much is left, and the reader has no way to tell it from a real one
 
 ### onPageChange — `callback`
 
-Use when: What the page does when the reader asks for another one, counting from one. Required wherever the route to a page is a press rather than a destination: the dots variant always, and the steps under any variant given no pageHref. Under pages it is the pageHref that carries the reader, so this is the reporting half rather than the moving one — useful for telling analytics, and unnecessary if nothing is listening. One of this and pageHref is needed; a component given neither draws a row nothing can move.
+Use when: What the page does when the reader asks for another one, counting from one. Required wherever the route to a page is a press rather than a destination: the numbered targets and the steps under any variant given no pageHref. Under pages it is the pageHref that carries the reader, so this is the reporting half rather than the moving one — useful for telling analytics, and unnecessary if nothing is listening. One of this and pageHref is needed; a component given neither draws a row nothing can move.
 Never for: Navigating by hand when pageHref would do it. A press handler that sets window.location is an anchor with its advantages removed — no cmd-click, no destination in the status bar, nothing for a crawler to follow.
 
 ### pageHref — `callback`
 
-Use when: The address of a page, given the page number. Passing it makes every route to a page an anchor: the numbered targets, and both steps. Required under the pages variant, which draws Buttons — and a Button in this package is an anchor with a destination, never a press the page handles. Pass it under compact or count too wherever the pages have real URLs, because an anchor is what gives a visitor cmd-click, a destination in the status bar, and a link a search engine can follow to page two. One of this and onPageChange is needed; a component given neither draws a row nothing can move.
-Never for: A carousel or any sequence whose positions have no address. A slide is not a place, so a link to one is a link to nowhere and the dots variant ignores this entirely. Nor for smuggling state into a query string the page does not actually route on — a URL that renders the same page whatever it says is worse than a button, which at least does not promise otherwise.
-
-### totalItems — `number`
-
-Use when: How many results there are altogether, where that is known. It is what turns the count variant's readout from a position into a measure — "1–10 of 240" rather than "page 1 of 24" — which is the fact that tells a reader whether to keep stepping or narrow their filter instead
-Never for: A count of what is on this page. It is the whole set, which is what makes the range in front of it mean anything. Nor an estimate presented as exact: a reader shown a total treats it as one, and a number that moves as they page through the set reads as the results changing underneath them
-
-### pageSize — `number`
-
-Use when: How many items each page holds, which is what lets the count variant work out the range on screen from the page number alone. Pass it alongside totalItems; on its own it has nothing to be a fraction of. It reports the size in force and does not offer to change it — a control for that is the consumer's to place, beside this one
-Never for: Changing how many items are fetched. This component displays and nothing else — the fetch is the consumer's, and a page size passed here while the query still asks for a different number produces a readout that describes a page nobody is looking at
+Use when: The address of a page, given the page number. Passing it makes every route to a page an anchor: the numbered targets, and both steps. Required under the pages variant, which draws Buttons — and a Button in this package is an anchor with a destination, never a press the page handles. Pass it under compact too wherever the pages have real URLs, because an anchor is what gives a visitor cmd-click, a destination in the status bar, and a link a search engine can follow to page two. One of this and onPageChange is needed; a component given neither draws a row nothing can move.
+Never for: A carousel or any sequence whose positions have no address. Nor for smuggling state into a query string the page does not actually route on — a URL that renders the same page whatever it says is worse than a button, which at least does not promise otherwise.
 
 ### siblingCount — `number` (default `1`)
 
@@ -142,14 +112,10 @@ its props — do not re-derive them from the variant descriptions above.
 
 - **A transactions table at the foot of a desktop page, where the reader returns to particular pages** — `variant="pages"`
   Numbered targets are the only ones a reader can aim at deliberately, and a table is the case where they come back to a page they have already read rather than only moving on from it
-- **A long list of search results where the reader is judging whether to keep going** — `variant="count"`
-  The question underneath the press is how much is left, and a page number cannot answer it. Pass totalItems and pageSize so the readout gives a range against a whole
 - **A card footer or a side panel too narrow for a row of numbers** — `variant="compact"`, not `variant="pages"`
   A row of numbers in a narrow column either wraps or clips, and both are worse than dropping the numbers deliberately. Compact keeps the two steps and the position, which is the part that survives the loss of width
 - **An archive running to dozens of pages, where the reader wants one further out than the row can draw** — `variant="pages"`
   The break between two runs of numbers presses and lists the pages it stands for, so a page the row cannot show is two presses away rather than a walk. Past fifty it lists an evenly spaced sample of the run instead, and the break beside where the reader lands stands for a shorter run and steps through it more finely
-- **A carousel or an onboarding walkthrough of a handful of screens** — `variant="dots"`
-  The sequence is short and unnamed, so position is the whole of what the reader needs — and a dot shows it without asking them to read anything
 
 ## Accessibility
 
@@ -158,7 +124,7 @@ Guaranteed by the component. Write none of it by hand: the ids these attributes
 - Announced as: `navigation`
 - `Tab` — Moves onto and through the controls in the order they are read — the step back, then whatever targets the variant offers, then the step forward. No roving tabindex here, unlike a segmented control: these are separate destinations rather than one question with several answers, and a reader tabbing through them is choosing between things they can see rather than cycling a value
 - `Enter` — Goes to the page the focused control names. Where that control is an anchor — a numbered target, or a step given pageHref — Enter follows the link and the browser does the rest, which is the whole point of drawing it as one. Where it is a button, the page is reported through onPageChange and nothing moves until the consumer passes the new page back. On the break between two runs of numbers it opens that break's menu instead, since the break names no page of its own
-- `Space` — The same as Enter on everything this component draws as a button: the marks under dots, the numbered targets and steps where no pageHref was given, and a step sitting at either end of the set. On an anchor it does nothing, which is the browser's rule rather than this component's — a link answers Enter alone
+- `Space` — The same as Enter on everything this component draws as a button: the numbered targets and steps where no pageHref was given, and a step sitting at either end of the set. On an anchor it does nothing, which is the browser's rule rather than this component's — a link answers Enter alone
 - `Arrow keys` — Move through the pages a break's menu offers once it is open, and open it from the break itself — down onto the first page it lists, up onto the last. DropdownMenu's behaviour rather than this component's: the break is its trigger and the menu is its surface, which is the whole reason the break is built out of it
 - `Escape` — Shuts a break's menu and puts focus back on the break, leaving the reader on the page they were already on. DropdownMenu's as well
 - an accessible name drawn from label, so a reader listing the page's landmarks can tell what this one pages through. A navigation landmark without a name is one they cannot navigate to, and a page carrying two of them unnamed is worse — the list reports the same word twice
@@ -167,7 +133,6 @@ Guaranteed by the component. Write none of it by hand: the ids these attributes
 - the step-forward control carries its own, from nextLabel, and the two stay parallel — a pair reading "Next page" and "Go back" is two people's wording in one control
 - a step control at the boundary is disabled rather than removed. Removing it shifts every remaining target sideways at the moment the reader is aiming at one, and takes away the thing a screen reader user was about to be told is unavailable. The native disabled attribute rather than aria-disabled, because there is nothing here to explain: the reader can see they are on the first page
 - the current page's own target stays enabled and in the tab order. Disabling it would leave the one page a keyboard reader is on as the one page they cannot reach, and the row would report a different number of stops depending on where in the set they stood
-- the position marks under the dots variant are buttons with names, not decoration. A dot that cannot be reached or announced leaves a keyboard reader with the two step controls and no way to know how many positions there are
 - the break between two runs of numbers is a control with an accessible name of its own, from morePagesLabel, and announces that it opens a menu. It was punctuation and aria-hidden while it did nothing, which was right then and is not now: the pages behind a break are the ones a reader deep in a long set most needs, and a control that offers them to a pointer and not to a screen reader is worse than the punctuation it replaced
 
 ## Rules
@@ -236,9 +201,21 @@ The target and the mark are separate decisions, and conflating them is what prod
 
 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
 
+❌ Pagination for: A short sequence the reader moves through — a slider's slides, a carousel of cards, a walkthrough
+   Where the reader is in a few slides is a different question from how far a set of results runs, and a dot carries no number to answer the second. PaginationDots is the row of marks for the first, with the steps left to whatever holds it.
+   → use `PaginationDots` instead.
+
 ❌ Pagination for: The reader is moving between views of one page rather than through one long set
    Tabs name their destinations and pagination numbers them, which is the difference between choosing a view and advancing through a sequence. A reader handed numbers for what are really four named sections has to open each one to learn what it holds, and the numbers imply an order that the sections do not have
    → use `TabList` instead.
@@ -271,17 +248,8 @@ import { Pagination } from '@deriv-com/dds-marketing'
 // Pages — a blog index the reader returns to
 <Pagination variant="pages" page={3} totalPages={24} />
 
-// Count — the same archive, measured
-<Pagination variant="count" page={3} totalPages={24} totalItems={240} pageSize={10} />
-
 // Compact — a card footer with no room
 <Pagination variant="compact" page={3} totalPages={24} />
-
-// None — steps only, position unstated
-<Pagination variant="none" page={3} totalPages={24} />
-
-// Dots — a five-card carousel, not the archive
-<Pagination variant="dots" page={3} totalPages={5} />
 ```
 
 ### Where the reader stands
@@ -328,34 +296,3 @@ import { Pagination } from '@deriv-com/dds-marketing'
 // Two, one either side
 <Pagination variant="pages" page={12} totalPages={24} siblingCount={2} />
 ```
-
-### When the total is unknown
-
-The count variant needs both a total and a page size to state a range. Given neither it counts pages instead, which lets the variant be chosen before the data arrives.
-
-```tsx
-import { Pagination } from '@deriv-com/dds-marketing'
-
-// Total known — a range against a whole
-<Pagination variant="count" page={3} totalPages={24} totalItems={240} pageSize={10} />
-
-// Total unknown — pages, not items
-<Pagination variant="count" page={3} totalPages={24} />
-```
-
-### A set the reader swipes
-
-Cards moved by swiping, where the row reports position and does not offer to change it. Marks alone, at the full target, being the only way through for anyone not swiping.
-
-```tsx
-import { Pagination } from '@deriv-com/dds-marketing'
-
-// Five cards, third one showing
-<Pagination variant="dots" page={3} totalPages={5} showSteps={false} />
-
-// The same set with steps
-<Pagination variant="dots" page={3} totalPages={5} />
-
-// Twenty marks and both steps
-<Pagination variant="dots" page={8} totalPages={20} />
-```