@deriv-com/dds-marketing 1.1.3 → 1.2.1

package/.llm/components/documentlink.md

@@ -0,0 +1,237 @@
+<!-- GENERATED from document-link.contract.json. Do not edit. -->
+
+# DocumentLink
+
+One document a reader can open or save: its mark, its title, and an optional second link beside it.
+
+## Why it is built this way
+
+A legal or regulatory page lists documents by the dozen — key information documents, policies, a licence per country — and each is the same thing: a mark saying what kind of thing it is, the title a reader looks for, and a link to it, usually a PDF off the site. This draws that one thing the same way everywhere.
+
+The whole of the mark and the title is the link. A second link — choosing the document's language, say — sits beside it as a sibling, never inside it, so there are two targets a reader can tell apart rather than one inside another. `chip` sets it on a surface of its own, for documents grouped in a list; `plain` leaves the mark and the title on the page, for a grid of many, as a grid of country flags is.
+
+## Use when
+
+- A document on a legal, regulatory or help page — a policy, a key information document, a licence, a form
+- Many documents of one kind, listed or laid in a grid inside a Documents block
+
+## Do not use
+
+- One to four related pages or documents at the end of a section → `ResourceBanner`
+- A link inside a sentence, or a page rather than a document → `Link`
+- Navigation between pages of the site. A document chip says a file is behind it
+- A document whose title alone does not say which it is. Two chips both reading "Key information document" are the same chip twice
+
+## Anatomy
+
+DocumentLink renders 5 elements. A token binding names the part it applies to.
+
+- `root` — `<div>`, class `dds-documentlink`. The document's row: the link and, where there is one, the action beside it, pushed to the far end. Under `chip`, a surface of its own — color.bg.surface-card-raised edged with color.border.subtle, at radius.surface, padded by space.inset.sm and space.inset.md — so it stands out on any ground. Under `plain`, nothing but what it holds. Not itself interactive: it holds up to two links side by side, never one inside another. A chip sets its own ink, color.fg.default, on its own surface; a plain entry takes the ink of whatever it stands on, so it reads on a dark band as on the page.
+- `link` — `<a>`, class `dds-documentlink__link`. The document: its mark and its title, one target. Opens in place, or in a new tab under `external`; saves the file under `download`. Its accessible name is the title, ending with `externalLabel` or `downloadLabel`, heard and never drawn, so a reader who cannot see the mark is told what happens. Underlined on hover; shows the focus ring when focused.
+- `mark` — `<span>`, class `dds-documentlink__mark`. What kind of document it is, before its title: `mark`, or a file when there is none — FilePdfSolidIcon for a PDF, a country's flag from the flag icons for one country's licence. Decoration; the title names it. At icon.size.lg in a chip, icon.size.md plain.
+- `title` — `<span>`, class `dds-documentlink__title`. The document's title, as a reader looks for it, at font.label.md in a chip and font.body.sm plain. Wraps rather than widening the row.
+- `action` — `<div>`, class `dds-documentlink__action`. A second link beside the document — choosing its language — at the far end of the row, a sibling of the document's link and never inside it. Rendered only when `action` is set.
+
+Apply these classes from the generated `documentLinkParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `text`
+
+## Props
+
+### variant — `chip` | `plain` (default `chip`)
+
+- `chip` — The default: the document on a surface of its own, for a list of documents grouped under headings
+- `plain` — The mark and the title on the page itself, for a grid of many short entries — a licence per country, each behind its flag
+
+Use when: How much the document stands out from the page around it
+Never for: Mixing the two in one list. A list is one kind of thing; chips beside plain entries read as two
+
+### href — `string` **Required.**
+
+Use when: Always. Where the document is: a URL, usually a PDF
+Never for: A page on the site. A page is a Link
+
+### external — `boolean` (default `false`)
+
+Use when: The document is hosted off the site — opens in a new tab, and its accessible name ends with `externalLabel`
+Never for: A document on this site, which opens in place
+
+### download — `boolean` (default `false`)
+
+Use when: The link saves the file rather than opening it — its accessible name ends with `downloadLabel`
+Never for: A document a browser opens to read, which most PDFs are. A file on another site. Browsers ignore `download` across origins and open the file instead, so the name would promise a download that does not happen; such a file is `external`
+
+### mark — `node`
+
+Accepts: Icon
+Use when: What kind of document it is, as a glyph — FilePdfSolidIcon for a PDF, FileShieldSolidIcon for a policy, or a country's flag from `@deriv-com/dds-marketing/icons/flag` (`MaltaIcon`, `GermanyIcon`) for one country's licence. Left out, a plain file
+Never for: Saying what the title does not. The mark is decoration and is never read out
+
+### action — `node`
+
+Accepts: Link
+Use when: A second link beside the document — "Choose language" — drawn at the far end of the row as its own target
+Never for: A second document. Each document is its own DocumentLink
+
+### externalLabel — `string` (default `(opens in a new tab)`)
+
+Use when: What an external document's accessible name ends with. Never drawn. Translate it with the page
+Never for: Anything a sighted reader needs; it is never shown
+
+### downloadLabel — `string` (default `(downloads a file)`)
+
+Use when: What a download's accessible name ends with. Never drawn. Translate it with the page
+Never for: Naming the file's format, which belongs in the title where it matters
+
+Also accepts everything from `HTMLAttributes<HTMLDivElement>`.
+
+## Accessibility
+
+Guaranteed by the component. Write none of it by hand: the ids these attributes point at are generated per instance, so an attribute set from outside either says the same thing twice or points at nothing.
+
+- `Tab` — Moves to the document's link, then to the action beside it where there is one
+- the document's link and the action are two sibling links, never one inside the other
+- an external document's accessible name ends with `externalLabel`, and a download's with `downloadLabel`, so a reader who cannot see the mark is told what happens
+- the mark is decoration; the title names the document
+
+## 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, CardButton and TextInput simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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
+
+❌ DocumentLink for: One to four related pages or documents at the end of a section
+   A short stack of where to read more is ResourceBanner's job; this is one document among many
+   → use `ResourceBanner` instead.
+
+❌ DocumentLink for: A link inside a sentence, or a page rather than a document
+   A document has a mark and a title a reader scans for; a link to a page is a Link
+   → use `Link` instead.
+
+## Example
+
+```tsx
+import { DocumentLink, Icon } from '@deriv-com/dds-marketing'
+import { FileShieldSolidIcon } from '@deriv-com/dds-marketing/icons'
+
+<DocumentLink href="https://example.com/key-information-document.pdf" external mark={<Icon size="xs"><FileShieldSolidIcon /></Icon>}>Key information document: CFDs on forex</DocumentLink>
+```
+
+## In use
+
+### Chip and plain
+
+A chip for a document in a grouped list; plain for one entry in a grid of many, a licence behind its country's flag.
+
+```tsx
+import { DocumentLink, Icon } from '@deriv-com/dds-marketing'
+import { FileShieldSolidIcon } from '@deriv-com/dds-marketing/icons'
+
+// chip
+<DocumentLink variant="chip" href="https://example.com/kid.pdf" external mark={<Icon size="xs"><FileShieldSolidIcon /></Icon>}>Key information document: CFDs on forex</DocumentLink>
+
+// plain
+<DocumentLink variant="plain" href="https://example.com/malta.pdf" external mark={<Icon size="xs"><FileShieldSolidIcon /></Icon>}>Malta</DocumentLink>
+```
+
+### With a second link
+
+A language choice beside the document, its own target at the far end of the row.
+
+```tsx
+import { DocumentLink, Icon, Link } from '@deriv-com/dds-marketing'
+import { FileShieldSolidIcon } from '@deriv-com/dds-marketing/icons'
+
+// action
+<DocumentLink href="https://example.com/terms.pdf" external mark={<Icon size="xs"><FileShieldSolidIcon /></Icon>} action={<Link href="#" tone="inherit">Choose language</Link>}>Terms and conditions</DocumentLink>
+```
+
+### A file to save
+
+`download` saves the file rather than opening it, and the link's name says so.
+
+```tsx
+import { DocumentLink } from '@deriv-com/dds-marketing'
+
+// download
+<DocumentLink href="https://example.com/form.pdf" download>Account closure form</DocumentLink>
+```

package/.llm/components/documents.md

@@ -0,0 +1,268 @@
+<!-- GENERATED from documents.contract.json. Do not edit. -->
+
+# Documents
+
+A section of documents to open or save — grouped under headings that expand, or laid in a grid beside its heading.
+
+## Why it is built this way
+
+Legal, regulatory and help pages publish documents by the dozen: key information documents by product, policies, a licence for each country the company works in. This is the section they sit in, in one of two shapes — the reference design's DocumentChips and CountryLinkGrid, one block because they are one job.
+
+`groups` lays the documents under headings that expand, one group open at a time, each document a DocumentLink chip, two to a row from the fold. `grid` sets the heading beside a grid of short entries — a country's flag and its name, each a link to that country's document — two to four across as the width allows. Both are built from children, so a page writes the groups and the documents it has, and flags are the package's own flag icons rather than images fetched from elsewhere.
+
+## Use when
+
+- A legal or regulatory page's documents — key information documents grouped by product, policies, terms
+- A document per country, region or entity, each behind its flag or mark — `layout="grid"`
+- Any list of more documents than a ResourceBanner's four
+
+## Do not use
+
+- One to four documents or pages at the end of a section → `ResourceBanner`
+- Questions and their answers → `FaqAccordion`
+- Documents the reader must see before acting — a risk warning on the page it governs. A folded group is one most readers never open
+- Navigation between the site's pages. Each entry is a document; a page is a Link
+- Mixing the two shapes in one section. Groups of chips beside a grid of flags is two sections
+
+## Anatomy
+
+Documents renders 8 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-documents`. The section, a region named by its heading, on the ground `ground` paints with the ink that goes with it.
+- `inner` — `<div>`, class `dds-documents__inner`. The measure and the gutter, the same column every band holds its content in, and the step from the heading to the documents: space.heading.content.
+- `title` — `<h2>`, class `dds-documents__title`. What the documents are — "Regulatory documents", "Licences by country". `h2` because a section sits under the page's own heading, and each group heading below it is an `h3` — Accordion's own default level. Starts on a phone, centred from the fold under `groups`.
+- `header` — `<div>`, class `dds-documents__header`. The heading and the line under it. Over the documents under `groups`; beside the grid from 62rem under `grid`, and over it below.
+- `description` — `<p>`, class `dds-documents__description`. The line under the heading, at font.body.md. Rendered only when `description` is set.
+- `body` — `<div>`, class `dds-documents__body`. The documents: an Accordion of the groups under `groups`, the list of entries under `grid`.
+- `list` — `<ul>`, class `dds-documents__list`. Under `grid`, the entries as a list: two across on a phone, three from 35rem, four from 48rem; from 62rem, where the grid shares the width with the heading, two, and three again from 75rem — so a country's name stays on one line. Rendered only when `layout` is set.
+- `item` — `<li>`, class `dds-documents__item`. One entry of the grid, holding one DocumentLink.
+
+Apply these classes from the generated `documentsParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `AccordionItem`, `DocumentLink`
+- Never contains: `Accordion`, `FaqAccordion`, `Documents`, `LandingHero`, `ProductHero`, `PageHeader`, `Footer`, `Navbar` — in children or in any prop that takes a node
+- Holds at least 1
+
+## Props
+
+### ground — `page` | `subtle` | `strong` (default `page`)
+
+- `page` — The default, and the page's own white. A section that has nothing to separate itself from what is above it — most of them — and the ground a reader is already on
+- `subtle` — A quiet step off the page, for a band that wants to read as its own section without changing the page's voice — the reference design's slate FAQ. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section.
+- `strong` — `color.bg.brand-strong`, the dark band. It stops the page rather than dividing it, so it is for a section a reader should arrive at — and one per page is usually one more than enough. The documents turn round with it: white group headings, a muted chevron, rules in the band's own veil and a focus ring drawn for the dark, fixed like the band
+
+Use when: Which of the page's three grounds this section paints. A marketing page is white, and a band that wants to be seen as a band takes one of the other two — so this is how a page builds its rhythm: white, white, grey, white, dark. Two in a row is a deliberate pair rather than an accident, and the section above knows nothing about the one below it, so the page is the only thing that can decide.
+
+The ink follows the ground and is not a second decision: a dark band carries white type because this sets both halves in one value, which is what the painted-ground-carries-its-ink rule exists to stop a page getting wrong.
+Never for: Marking importance. Every section on a page painted a ground is a page with no emphasis left.
+
+### layout — `groups` | `grid` (default `groups`)
+
+- `groups` — The default: the documents under headings that expand, one group open at a time — AccordionItem children, each holding DocumentLink chips, two to a row from the fold. The reference design's DocumentChips
+- `grid` — Many short entries of one kind — a document per country, each behind its flag — DocumentLink children with `variant="plain"`, in a grid beside the heading from 62rem and under it below. The reference design's CountryLinkGrid
+
+Use when: How the documents are laid out: grouped under headings, or as one grid of entries
+Never for: Choosing by how many documents there are alone. Groups are for documents of different kinds; a grid is for many of one kind
+
+### title — `string` **Required.**
+
+Use when: Always. What the documents are, in a few words — "Regulatory documents", "Licences by country". It names the section
+Never for: A sentence. The line under it says more
+
+### description — `string`
+
+Use when: A line under the heading saying what the documents are for or who they apply to
+Never for: Instructions a reader must follow; they belong on the page the documents govern
+
+## Accessibility
+
+Guaranteed by the component. Write none of it by hand: the ids these attributes point at are generated per instance, so an attribute set from outside either says the same thing twice or points at nothing.
+
+- Announced as: `region`
+- `Tab` — Moves through the group headings, then into an open group's documents, each document's link and its action in turn
+- the section is a region named by its heading
+- under `groups`, each group heading is a button that says whether it is open, and one group is open at a time
+- under `grid`, the entries are a list, so a reader hears how many there are
+
+## 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, CardButton and TextInput simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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
+
+❌ Documents for: One to four documents or pages at the end of a section
+   A short stack of where to read more is ResourceBanner's job; this is a library of documents
+   → use `ResourceBanner` instead.
+
+❌ Documents for: Questions and their answers
+   FaqAccordion is questions a reader asks; these headings are groups of files
+   → use `FaqAccordion` instead.
+
+## Example
+
+```tsx
+import { Documents, AccordionItem, DocumentLink, Link } from '@deriv-com/dds-marketing'
+import { FileShieldSolidIcon } from '@deriv-com/dds-marketing/icons'
+
+<Documents title="Regulatory documents" description="Our key information documents and policies, by product.">
+  <AccordionItem title="Key information documents" onExpandedChange={(expanded) => { /* your handler */ }}>
+    <DocumentLink href="/documents/kid-forex.pdf" mark={<FileShieldSolidIcon />} action={<Link href="/documents/languages" tone="inherit">Choose language</Link>}>CFDs on forex</DocumentLink>
+    <DocumentLink href="/documents/kid-stocks.pdf" mark={<FileShieldSolidIcon />} action={<Link href="/documents/languages" tone="inherit">Choose language</Link>}>CFDs on stocks</DocumentLink>
+    <DocumentLink href="/documents/kid-commodities.pdf" mark={<FileShieldSolidIcon />}>CFDs on commodities</DocumentLink>
+  </AccordionItem>
+  <AccordionItem title="Policies" onExpandedChange={(expanded) => { /* your handler */ }}>
+    <DocumentLink href="/documents/execution.pdf" mark={<FileShieldSolidIcon />}>Order execution policy</DocumentLink>
+    <DocumentLink href="/documents/conflicts.pdf" mark={<FileShieldSolidIcon />}>Conflicts of interest policy</DocumentLink>
+  </AccordionItem>
+</Documents>
+```
+
+## In use
+
+Most rows below hold the same set, written once here:
+
+```tsx
+import { AccordionItem, DocumentLink, Link } from '@deriv-com/dds-marketing'
+
+const accordionitems = (
+  <>
+    <AccordionItem title="Key information documents">
+  <DocumentLink href="/documents/kid-forex.pdf" mark={<FileShieldSolidIcon />} action={<Link href="/documents/languages" tone="inherit">Choose language</Link>}>CFDs on forex</DocumentLink>
+  <DocumentLink href="/documents/kid-stocks.pdf" mark={<FileShieldSolidIcon />} action={<Link href="/documents/languages" tone="inherit">Choose language</Link>}>CFDs on stocks</DocumentLink>
+  <DocumentLink href="/documents/kid-commodities.pdf" mark={<FileShieldSolidIcon />}>CFDs on commodities</DocumentLink>
+</AccordionItem>
+    <AccordionItem title="Policies">
+  <DocumentLink href="/documents/execution.pdf" mark={<FileShieldSolidIcon />}>Order execution policy</DocumentLink>
+  <DocumentLink href="/documents/conflicts.pdf" mark={<FileShieldSolidIcon />}>Conflicts of interest policy</DocumentLink>
+</AccordionItem>
+  </>
+)
+```
+
+### Grouped
+
+Documents under headings that expand, one group open at a time, each a chip — the reference's DocumentChips.
+
+```tsx
+import { Documents } from '@deriv-com/dds-marketing'
+
+// layout="groups"
+<Documents title="Regulatory documents" description="Our key information documents and policies, by product.">{accordionitems}</Documents>
+```
+
+### A grid of entries
+
+A document per country beside the heading, each behind its mark — the reference's CountryLinkGrid. A page passes each country's flag from the flag icons.
+
+```tsx
+import { DocumentLink, Documents } from '@deriv-com/dds-marketing'
+import { FileShieldSolidIcon } from '@deriv-com/dds-marketing/icons'
+
+// layout="grid"
+<Documents layout="grid" title="Licences by country" description="Our licence in each country we passport into.">
+  <DocumentLink href="/documents/malta.pdf" mark={<FileShieldSolidIcon />} variant="plain">Malta</DocumentLink>
+  <DocumentLink href="/documents/germany.pdf" mark={<FileShieldSolidIcon />} variant="plain">Germany</DocumentLink>
+  <DocumentLink href="/documents/france.pdf" mark={<FileShieldSolidIcon />} variant="plain">France</DocumentLink>
+  <DocumentLink href="/documents/italy.pdf" mark={<FileShieldSolidIcon />} variant="plain">Italy</DocumentLink>
+  <DocumentLink href="/documents/spain.pdf" mark={<FileShieldSolidIcon />} variant="plain">Spain</DocumentLink>
+  <DocumentLink href="/documents/netherlands.pdf" mark={<FileShieldSolidIcon />} variant="plain">Netherlands</DocumentLink>
+  <DocumentLink href="/documents/ireland.pdf" mark={<FileShieldSolidIcon />} variant="plain">Ireland</DocumentLink>
+  <DocumentLink href="/documents/austria.pdf" mark={<FileShieldSolidIcon />} variant="plain">Austria</DocumentLink>
+</Documents>
+```
+
+### Grounds
+
+The section takes one of the page's three grounds; the chips keep their own surface on each.
+
+```tsx
+import { Documents } from '@deriv-com/dds-marketing'
+
+// page
+<Documents title="Regulatory documents" description="Our key information documents and policies, by product." ground="page">{accordionitems}</Documents>
+
+// subtle
+<Documents title="Regulatory documents" description="Our key information documents and policies, by product." ground="subtle">{accordionitems}</Documents>
+
+// strong
+<Documents title="Regulatory documents" description="Our key information documents and policies, by product." ground="strong">{accordionitems}</Documents>
+```

package/.llm/components/downloadbanner.md

@@ -59,7 +59,7 @@ Apply these classes from the generated `downloadBannerParts` constant rather tha
 
 - `page` — The default, and the page's own white. The card is the recessed gray that sets it off — the reference design's light-2
 - `subtle` — The grey band, with the card white on it — the reference design's light. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section
-- `strong` — `color.bg.brand-strong`, the dark band, with the card at color.bg.surface-card-strong and white words on it — the reference design's dark. For a download section a reader should arrive at; the badges are black and keep their own edge on it
+- `strong` — `color.bg.brand-strong`, the dark band, with the card at color.bg.surface-card-strong-on-brand-strong and white words on it — the reference design's dark. For a download section a reader should arrive at; the badges are black and keep their own edge on it
 
 Use when: Which of the page's grounds the section paints, and with it the card's fill: the recessed surface on the page, the raised white on the grey band, and the strong card on the dark band — TestimonialRow's three and the reference design's light, light-2 and dark. The ink follows the ground and is not a second decision.
 Never for: Marking importance. Every section on a page painted a ground is a page with no emphasis left.
@@ -142,6 +142,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   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, CardButton and TextInput simultaneously.
   Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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.

package/.llm/components/dropdownmenu.md

@@ -210,6 +210,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   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, CardButton and TextInput simultaneously.
   Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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.

package/.llm/components/estimator.md

@@ -161,6 +161,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   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, CardButton and TextInput simultaneously.
   Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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.

package/.llm/components/faqaccordion.md

@@ -82,6 +82,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   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, CardButton and TextInput simultaneously.
   Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  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.