@deriv-com/dds-marketing 1.0.2 → 1.1.0

package/.llm/components/illustrationcard.md

@@ -4,7 +4,7 @@
 
 A pane of glass holding a piece of product information — a market's price, a balance, a status — in one of three shapes, used as a picture: laid over a photograph or a piece of art, or standing on its own as the image a section shows beside its words. It is never the section's content. What a section says is set in the section's own blocks and type; this is an illustration of the product, the way a screenshot would be one, only drawn from the system's own parts.
 
-It owns the two things every such picture has to get right and nobody gets right twice: its shape and its surface. The shape is one of three — four by three, square, three by four — so pictures on one page and across a site agree, and none is a one-off. The surface is always glass over a blur of whatever is behind it — light glass in light mode, a faint frosted white in dark — so the pane reads as part of the image it sits on rather than a box pasted onto it.
+It owns the two things every such picture has to get right and nobody gets right twice: its shape and its surface. The shape is one of three — four by three, square, three by four — so pictures on one page and across a site agree, and none is a one-off. The surface is always dark glass over a blur of whatever is behind it, in light mode and dark alike — the product as it looks in its dark theme, which a picture of it should not change with the page — so the pane reads as part of the image it sits on rather than a box pasted onto it.
 
 Everything inside is illustrative: built from the system's real components so it looks exactly like the product, and made inert, so nothing in it can be focused, pressed or typed into, and a screen reader hears one image described by `label`. The product information inside is the page's. A photograph or a person it sits on, or beside, is the page's or a block's to place; this is the pane alone.
 
@@ -29,7 +29,7 @@ Everything inside is illustrative: built from the system's real components so it
 
 IllustrationCard renders 2 elements. A token binding names the part it applies to.
 
-- `root` — `<div>`, class `dds-illustrationcard`. The pane: one of three proportions whatever is put in it — the aspect tokens — and the glass. Its fill is color.bg.surface-glass — white at most of its strength in light mode, a faint frosted white in dark — over a blur of size.backdrop-blur in illustration-card-impl.css, because a blur is a function no binding can name. It holds radius.surface and space.inset.card like a Card, a hairline edge so its outline survives on a light page, and the default ink, color.fg.default, which follows the glass from dark on light to light on frosted. It is one image to assistive technology — `role="img"`, named by `label` — so a screen reader hears what the picture shows in a sentence rather than a list of controls that are not there.
+- `root` — `<div>`, class `dds-illustrationcard`. The pane: one of three proportions whatever is put in it — the aspect tokens — and the glass. It is drawn in the dark theme whatever the page's, so the product it shows looks the same on every page. Its fill is color.bg.surface-glass — a faint frosted white — laid over the dark page's ground when it stands alone and over the photograph in a scene, over a blur of size.backdrop-blur in illustration-card-impl.css, because a blur is a function no binding can name. It holds radius.surface and space.inset.card like a Card, a hairline edge so its outline survives on a light page, and the default ink, color.fg.default — light on the frosted pane. It is one image to assistive technology — `role="img"`, named by `label` — so a screen reader hears what the picture shows in a sentence rather than a list of controls that are not there.
 - `content` — `<div>`, class `dds-illustrationcard__content`. What the pane holds, made a picture. It is `inert`: whatever components draw it — a Button, a SegmentedControl, a TextInput — look exactly as they do anywhere, and none of them can be focused, tabbed to, pressed or typed into, so a reader never meets a control that does nothing. Laid out down the pane from the start edge at its own size, and scaled down as a whole where the pane is too small to hold it — the way a picture shrinks — so a pane on a phone shows the same UI smaller rather than overlapped or cut off. The shape is fixed: the UI never stretches the pane.
 
 Apply these classes from the generated `illustrationCardParts` constant rather than writing the strings by hand.

package/.llm/components/illustrationscene.md

@@ -17,7 +17,7 @@ The photograph is the scene and the card is what it says. The card's `label` des
 - There is only a photograph → `AspectRatio`
 - A section's content. Like the card it holds, the scene is a picture of the product, and what a section says belongs in its own blocks
 - More than one card over one photograph. A second card is a second picture competing for the same eye; two scenes side by side say two things clearly
-- A photograph whose subject sits where the card goes. The card covers the middle of the frame, or one side of it with `placement`; choose or crop the photograph so the person or the object stays clear of it
+- A photograph whose subject sits where the card goes. The card covers the middle of the frame, or its foot with `placement`; choose or crop the photograph so the person or the object stays clear of it
 
 ## Anatomy
 
@@ -45,11 +45,10 @@ Apply these classes from the generated `illustrationSceneParts` constant rather
 Use when: The scene's shape. One of three, the same three IllustrationCard takes, so scenes and cards across a site agree
 Never for: Fitting a particular photograph. The shape is a decision about the layout; the photograph is chosen or cropped for it
 
-### placement — `center` | `start` | `end` (default `center`)
+### placement — `center` | `bottom` (default `center`)
 
 - `center` — The default: the card in the middle of the frame. For a photograph whose subject frames the middle — a person looking down at what the card shows
-- `start` — The card towards the start edge, for a photograph whose subject is at the end
-- `end` — The card towards the end edge, for a photograph whose subject is at the start
+- `bottom` — The card centred along the foot of the frame, held off it by the card's own inset — for a photograph whose subject fills the top: a face, a person reaching up, a skyline
 
 Use when: Where the card sits over the photograph, so the subject of the photograph stays clear of it
 Never for: Anything but keeping the photograph's subject clear. The card's size is fixed by the shape; placement moves it and nothing else
@@ -217,7 +216,7 @@ import { IllustrationScene } from '@deriv-com/dds-marketing'
 
 ### Where the card sits
 
-Centred, or towards one edge, so the photograph's subject stays clear of the card.
+Centred, or along the foot of the frame, so the photograph's subject stays clear of the card.
 
 ```tsx
 import { IllustrationScene } from '@deriv-com/dds-marketing'
@@ -225,9 +224,6 @@ import { IllustrationScene } from '@deriv-com/dds-marketing'
 // center — the default
 <IllustrationScene ratio="square" src="/sample-card-image.svg">{illustrationcards}</IllustrationScene>
 
-// start
-<IllustrationScene ratio="square" src="/sample-card-image.svg" placement="start">{illustrationcards}</IllustrationScene>
-
-// end
-<IllustrationScene ratio="square" src="/sample-card-image.svg" placement="end">{illustrationcards}</IllustrationScene>
+// bottom
+<IllustrationScene ratio="square" src="/sample-card-image.svg" placement="bottom">{illustrationcards}</IllustrationScene>
 ```

package/.llm/components/imagebanner.md

@@ -0,0 +1,278 @@
+<!-- GENERATED from image-banner.contract.json. Do not edit. -->
+
+# ImageBanner
+
+A dark card in the middle of a page, pairing a headline and a line under it with a photograph — beside it or behind it, with one action.
+
+The reference site's ImageBanner, and a break rather than an opening: a dark, editorial moment between lighter sections that asks for one thing. The card is dark on every ground; `ground` paints the band it sits in, the way it does for every block.
+
+## Use when
+
+- Driving a single mid-page or end-of-page action with a photograph to carry it — a community, a hub, a platform
+- A dark, editorial break between lighter sections
+
+## Do not use
+
+- The section opens the page → `ProductHero`
+- The point wants the page's own light ground rather than a dark card → `FeatureSplit`
+- There is no photograph, only a headline and an action → `CtaBanner`
+- The section says what a programme or a product comes with, as a list of features → `FeatureBullets`
+- The page's opening band. A dark card at the top of a page competes with the navigation above it and the hero it should be
+- More than one action. The card asks for one thing, and a second button beside it is a second demand on a card already set apart from the page
+- A picture carrying words a reader needs. The cover photograph sits under a scrim and the text, and the split's is cropped to fill its half
+
+## Anatomy
+
+ImageBanner renders 8 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-imagebanner`. The section. It paints one of the page's three grounds and the ink that goes with it — see `ground` — and asks its own width, so the card folds on the section's measure rather than the window's. A region named by its headline.
+- `inner` — `<div>`, class `dds-imagebanner__inner`. The measure and the gutter, the same column every band holds its content in. On a phone the card gives up the gutter and runs the width of the screen, as the reference design's does.
+- `card` — `<div>`, class `dds-imagebanner__card`. The dark card holding everything: color.bg.brand-strong, or color.bg.surface-card-strong on the dark band so it is still a card there, with white ink on both. It clips the photograph to its rounded corners. From 48rem the words and the photograph sit side by side, in the order `mediaPosition` names; below it they stack.
+- `content` — `<div>`, class `dds-imagebanner__content`. The headline, the line under it and the action, inset from the card's edge. It sets no gap of its own: the step from a title to its description and the step from a description to what follows are two roles, carried by each part's own margin.
+- `title` — `<h2>`, class `dds-imagebanner__title`. The headline. `h2` by default because the card sits under the page's own heading; `headingLevel` moves the level and never the size. Drawn at font.h2.
+- `description` — `<p>`, class `dds-imagebanner__description`. The line under the headline, at the body step and the description measure. Rendered only when `description` is set.
+- `action` — `<div>`, class `dds-imagebanner__action`. The one action, under the line. On a phone it fills the width of the card; from 48rem it is its own size. Rendered only when `action` is set.
+- `media` — `<div>`, class `dds-imagebanner__media`. The photograph. Split: one half of the card, edge to edge and cropped to fill it — landscape on a phone, the card's full height from 48rem. Cover: the whole card behind the words, under a scrim of color.bg.overlay fading through color.bg.overlay-subtle to clear, toward the side `mediaPosition` names.
+
+Apply these classes from the generated `imageBannerParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `ImageBanner`, `CtaBanner`, `CtaBannerSlider`, `FeatureSplit`, `FeatureBullets`, `LandingHero`, `ProductHero`, `PageHeader`, `Footer`, `Navbar` — in children or in any prop that takes a node
+
+## Props
+
+### ground — `page` | `subtle` | `strong` (default `page`)
+
+- `page` — The default, and the page's own white, with the dark card set into it. Most of the time: the card is already the break
+- `subtle` — The grey band, for a card that follows a white section the page wants told apart from this one. 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 a step lighter at color.bg.surface-card-strong so it still reads as a card. For a page whose dark band is already here and wants the card inside it
+
+Use when: Which of the page's three grounds the band around the card paints. The card is dark whatever this says — that is what the block is — so this is about the rhythm of the page, white, grey or dark, and never about the card. The ink follows the ground and is not a second decision.
+Never for: Making the card darker. The card is dark on every ground; painting the band dark too spends the page's one dark band on a section that was already one.
+
+### variant — `split` | `cover` (default `split`)
+
+- `split` — The default. The words in one half and the photograph filling the other, edge to edge, with one action under the words. On a phone the card runs the width of the screen and the photograph stacks with the words
+- `cover` — The photograph fills the whole card, with the words over it behind a scrim that darkens the side they are on and leaves the photograph clear on the other. For a photograph wide enough to be the band rather than half of it
+
+Use when: What the photograph does: beside the words, or behind them. Both carry one action — two of the reference design's layouts.
+Never for: Choosing by how busy the page looks. Cover hides part of the photograph under the scrim; it is a decision about the photograph, not decoration.
+
+### mediaPosition — `end` | `start` (default `end`)
+
+- `end` — The default. The words lead and the photograph follows, which is the order the card argues in
+- `start` — The photograph leads — the second of two cards on a page, or a photograph whose subject faces the words. A split card puts it above the words on a phone as well, as the reference design does
+
+Use when: Which side the photograph takes, and in cover, which side it shows clear on with the words on the other. Alternating it with the section above is the page's decision, not this one's.
+Never for: Aligning the words to the far edge. They start where their column starts on either side, because a heading beside content starts with it.
+
+### title — `string` **Required.**
+
+Use when: Always. The one thing the card says, in under eight words — "Join our global community".
+Never for: A sentence. The description under it carries the argument
+
+### headingLevel — `h2` | `h3` (default `h2`)
+
+- `h2` — The default: the card is a section of the page, under the page's own h1
+- `h3` — The card sits inside a section that already carries the h2 it belongs to
+
+Use when: Matching the outline of the page around the card, so the headline keeps its place in the hierarchy rather than skipping a level — CtaBanner's and ResourceBanner's prop. The level only: the size stays font.h2.
+Never for: Making the headline bigger or smaller. The card decides the size; this decides only where the headline sits in the page's outline.
+
+### description — `string`
+
+Use when: The line under the headline saying what it means for the reader, in one or two sentences.
+Never for: A paragraph. Past about two hundred characters the words run longer than the photograph beside them, which is the reference design's limit as well
+
+### action — `node`
+
+Accepts: Button, Link
+Use when: The one thing the card asks for. The card is dark in both themes, so a Button here takes tone="inverse": the primary is the coral fill and it is the card's one primary. On a phone it fills the width of the card.
+Never for: A second action. The card asks for one thing.
+
+### media — `node` **Required.**
+
+Accepts: *
+Use when: Always. The page's photograph, through AspectRatio or as an image — people or product. Split and cover crop it to fill the space they give it. Alt text is the page's to give, empty where the photograph is decoration.
+Never for: Artwork with words in it. The cover photograph sits under a scrim and the text, and the split crops to fill
+
+### parallax — `boolean` (default `false`)
+
+Use when: The photograph drifts against the scroll as the card passes through the view, by motion.distance.drift over the whole pass, so it reads as further away than the card — the reference design's ParallaxBanner, which this replaces. For a careers or about page, where the photograph of the people is the point. Off by default: a card selling one action does not need its picture moving under the button.
+Never for: Holding still for a reader who asked for less motion — it already holds still for them, and in a browser that cannot drive it from the scroll.
+
+## 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 to the action, where there is one, and past the section otherwise.
+- accessible name from title, so the card is a named region a screen reader can jump to and skip
+- The words over a cover photograph keep AA contrast against the scrim, which is why the scrim darkens the side the words are on rather than the whole photograph evenly. A photograph too light for that is a split card
+
+## 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 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
+
+❌ ImageBanner for: The section opens the page
+   An opening band is a claim sized to be the first thing read; this is a card set into the page below it
+   → use `ProductHero` instead.
+
+❌ ImageBanner for: The point wants the page's own light ground rather than a dark card
+   The same claim beside a picture, without the card around it
+   → use `FeatureSplit` instead.
+
+❌ ImageBanner for: There is no photograph, only a headline and an action
+   A banner of words and a button is the coral band; this one is half picture and has nothing to show without one
+   → use `CtaBanner` instead.
+
+❌ ImageBanner for: The section says what a programme or a product comes with, as a list of features
+   A list of features is the content there, ruled lines a reader goes down; this card is a photograph and one action
+   → use `FeatureBullets` instead.
+
+## Example
+
+```tsx
+import { ImageBanner, Button, AspectRatio } from '@deriv-com/dds-marketing'
+
+<ImageBanner title="Join our global community" description="Connect with traders around the world to exchange insights, explore portfolios and learn from people who trade the same markets you do." action={<Button variant="primary" tone="inverse" href="/community">Join the community</Button>} media={<AspectRatio ratio="landscape" />} />
+```
+
+## In use
+
+### Two layouts
+
+The photograph beside the words, or behind them under a scrim. Each carries one action.
+
+```tsx
+import { AspectRatio, Button, ImageBanner } from '@deriv-com/dds-marketing'
+
+// Split — photograph beside, one action
+<ImageBanner title="Join our global community" description="Connect with traders around the world to exchange insights, explore portfolios and learn from people who trade the same markets you do." action={<Button variant="primary" tone="inverse" href="/community">Join the community</Button>} media={<AspectRatio ratio="landscape" />} />
+
+// Cover — photograph behind, under a scrim
+<ImageBanner variant="cover" title="Trade on Deriv MT5" description="Forex, stocks, commodities and derived indices on the platform professionals use, with charting and order types built in." action={<Button variant="primary" tone="inverse" href="/platforms/deriv-mt5">Open a Deriv MT5 account</Button>} media={<AspectRatio ratio="landscape" />} />
+```
+
+### Which side the photograph takes
+
+Start puts the photograph first. On a phone a split card puts it above the words too; a cover card shows it clear on that side.
+
+```tsx
+import { AspectRatio, Button, ImageBanner } from '@deriv-com/dds-marketing'
+
+// Photograph last — the default
+<ImageBanner title="Join our global community" description="Connect with traders around the world to exchange insights, explore portfolios and learn from people who trade the same markets you do." action={<Button variant="primary" tone="inverse" href="/community">Join the community</Button>} media={<AspectRatio ratio="landscape" />} mediaPosition="end" />
+
+// Photograph first
+<ImageBanner title="Join our global community" description="Connect with traders around the world to exchange insights, explore portfolios and learn from people who trade the same markets you do." action={<Button variant="primary" tone="inverse" href="/community">Join the community</Button>} media={<AspectRatio ratio="landscape" />} mediaPosition="start" />
+
+// Cover, clear at the start
+<ImageBanner variant="cover" title="Trade on Deriv MT5" description="Forex, stocks, commodities and derived indices on the platform professionals use, with charting and order types built in." action={<Button variant="primary" tone="inverse" href="/platforms/deriv-mt5">Open a Deriv MT5 account</Button>} media={<AspectRatio ratio="landscape" />} mediaPosition="start" />
+```
+
+### The ground around it
+
+The card is dark on every ground; ground paints the band it sits in. On the dark band the card steps up to the strong card fill so it still reads as a card.
+
+```tsx
+import { AspectRatio, Button, ImageBanner } from '@deriv-com/dds-marketing'
+
+// On the page itself
+<ImageBanner title="Join our global community" description="Connect with traders around the world to exchange insights, explore portfolios and learn from people who trade the same markets you do." action={<Button variant="primary" tone="inverse" href="/community">Join the community</Button>} media={<AspectRatio ratio="landscape" />} ground="page" />
+
+// On the grey band
+<ImageBanner title="Join our global community" description="Connect with traders around the world to exchange insights, explore portfolios and learn from people who trade the same markets you do." action={<Button variant="primary" tone="inverse" href="/community">Join the community</Button>} media={<AspectRatio ratio="landscape" />} ground="subtle" />
+
+// On the dark band
+<ImageBanner title="Join our global community" description="Connect with traders around the world to exchange insights, explore portfolios and learn from people who trade the same markets you do." action={<Button variant="primary" tone="inverse" href="/community">Join the community</Button>} media={<AspectRatio ratio="landscape" />} ground="strong" />
+```
+
+### A photograph that drifts
+
+parallax: the photograph falls behind the card as the page scrolls past — the reference's ParallaxBanner. Split or cover, for a careers or about page.
+
+```tsx
+import { AspectRatio, ImageBanner, Link } from '@deriv-com/dds-marketing'
+
+// Split, drifting — Life at Deriv
+<ImageBanner variant="split" parallax title="Life at Deriv" description="We combine human values with AI precision. Collaboration, integrity and continuous learning guide every project, in every office and every time zone." action={<Link href="/careers/culture" tone="inherit">Culture at Deriv</Link>} media={<AspectRatio ratio="landscape" />} />
+
+// Inside a section that has its h2 — headingLevel h3
+<ImageBanner variant="split" parallax title="Life at Deriv" description="We combine human values with AI precision. Collaboration, integrity and continuous learning guide every project, in every office and every time zone." action={<Link href="/careers/culture" tone="inherit">Culture at Deriv</Link>} media={<AspectRatio ratio="landscape" />} headingLevel="h3" />
+```

package/.llm/components/navbar.md

@@ -180,7 +180,7 @@ Apply these classes from the generated `navbarParts` constant rather than writin
 ### tone — `default` | `inverse` (default `default`)
 
 - `default` — The page begins on a light ground, which is most marketing pages. The bar paints in ink and the pill is paper
-- `inverse` — The first section of the page paints its own dark ground and the bar stands on it — a dark hero, a photograph, a brand-coloured takeover. The bar's ink runs light, and the pill and the collapsed bar take the dark see-through material — a near-opaque black base, a white tint and a blur — so a light photograph behind cannot wash them out
+- `inverse` — The first section of the page paints its own dark ground and the bar stands on it — a dark hero, a photograph, a brand-coloured takeover. The bar's ink runs light, and the pill and the collapsed bar take a frosted white glass — a faint white base, a white tint over it and a blur — so the dark ground or the photograph shows through it, lightened, rather than a black slab standing on it. Choose a photograph dark where the bar sits: the glass lightens what is behind it and does not darken it
 
 ### label — `string` **Required.**
 

package/.llm/components/navbaritem.md

@@ -86,6 +86,10 @@ Never for: Decoration on every item. A glyph beside each of five destinations co
 Use when: The destination leaves the site. It draws the mark, opens in a new context, and the implementation extends the accessible name to say so in words — a glyph alone is a warning only sighted readers get
 Never for: A different area of the same site. A subdomain the reader experiences as one place is not a change of context, and marking it as one teaches them to ignore the mark where it matters
 
+### externalLabel — `string` (default `(opens in a new tab)`)
+
+Use when: What a screen reader hears after an external destination's name, since the arrow that shows it to everyone else is hidden. Translate it with the page.
+
 Also accepts everything from `AnchorHTMLAttributes<HTMLAnchorElement>`.
 
 ## Accessibility

package/.llm/components/pageheader.md

@@ -78,11 +78,12 @@ 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
 
-### background — `halftone`
+### background — `grid` | `halftone` (default `grid`)
 
-- `halftone` — A halftone drawn behind the band's content: coral dots blending to white at the glow's heart, on the band's own dark ground, following the pointer over the band. Drawn by Background, placed as a layer under the content, so the band's own layout is untouched. It replaces the rule grid rather than joining it: two patterns on one band are texture fighting texture.
+- `grid` — The default: the band's rule grid, lit — hairlines a pitch apart rising from a soft bloom at the band's foot, a brighter point where two lines cross and a short dash of light running along every few, brightening around the pointer. Drawn by Background as a layer under the content; before its shader has drawn, and where it cannot, the same rules painted by the stylesheet, so the band is never bare.
+- `halftone` — A halftone drawn behind the band's content: coral dots blending to white at the glow's heart, on the band's own dark ground, following the pointer over the band. Drawn by Background, placed as a layer under the content, so the band's own layout is untouched. It replaces the grid rather than joining it: two patterns on one band are texture fighting texture.
 
-Use when: The band is the page's one standout moment and wants more than a flat fill. Leave it out and the band is its flat ground, as it always was
+Use when: The band is the page's one standout moment and wants more than a flat fill. Leave it out and the band draws the lit grid
 Never for: More than one band on a page. The pattern is what makes a band the one a reader remembers, and two of them make neither
 
 ## Accessibility

package/.llm/components/paginationdots.md

@@ -65,7 +65,12 @@ Use when: The name the row is announced by, as a group. Name what the positions
 
 ### itemLabel — `string` (default `Slide`)
 
-Use when: The word each mark is named by, before its number — 'Slide 2'. Translate it with the page; a language that puts the number first is the reason a sentence template would be better, and the reason this is not yet one.
+Use when: The word each mark is named by, before its number — 'Slide 2'. Translate it with the page; a language that puts the number first, or writes it in its own digits, passes positionLabel instead.
+
+### positionLabel — `callback`
+
+Use when: Each mark's accessible name as a sentence, given its position counting from one and how many there are — for a language whose order is not the word then the number, or whose digits are not these. Wins over itemLabel where both are given.
+Never for: Visible text. It names the marks to assistive technology and is never drawn.
 
 ## Accessibility
 

package/.llm/components/producthero.md

@@ -25,7 +25,7 @@ The claim is centred and the product sits under it rather than beside it, whole
 
 ## Anatomy
 
-ProductHero renders 9 elements. A token binding names the part it applies to.
+ProductHero renders 10 elements. A token binding names the part it applies to.
 
 - `root` — `<section>`, class `dds-producthero`. The band. It paints the ground, carries the background image where there is one, and clips everything to its own edge so a visual that overruns cannot widen the page. `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-producthero__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 a band's text in the same column as the section under it. Positioned so it sits above the photograph without either of them naming a stacking order.
@@ -37,11 +37,10 @@ ProductHero renders 9 elements. A token binding names the part it applies to.
 - `title` — `<h1>`, class `dds-producthero__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-producthero__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-producthero__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.
-- `media` — `<div>`, class `dds-producthero__media`. The product itself, under the claim. In the column rather than against the band's edge — a product page is about one thing and the reader came to see it whole, so nothing crops it. It clips what it holds, because the corner it binds is otherwise a radius on a box nothing is drawn inside: the picture kept its own square edges and the token did nothing.
+- `media` — `<div>`, class `dds-producthero__media`. The product itself, under the claim, standing on the band's foot. It takes the picture's own shape: given `image`, the frame wraps the picture at its proportions — as wide as that shape allows up to the column, centred — and the screen decides only how tall it may grow, aspect.portrait of the column on a phone and half the band from the fold. A picture past that is drawn smaller, never cropped. Given `media`, an AspectRatio box, the page has fixed the shape on purpose and the box takes the column's width at it.
   
-  It is a square with square corners, standing on the band's foot.
-  
-  A square because what goes here is the product itself rather than a scene around it — a shape with no long side does not ask to be composed into, so a screenshot, a device and a person all sit in it the same way, and a page of these bands keeps one silhouette. Square corners because it is not a card: a rounded edge says the picture is an object placed on the band, and this one is meant to read as the thing the page is about, seen inside it. And on the foot because a picture with air under it floats — cropped by the band's own edge it is standing in the band, which is the arrangement LandingHero's subject takes for the same reason. Rendered only when `media` is set.
+  Its top corners are rounded at radius.container, as FeatureStack's are, and clip what it holds; its bottom corners stay square, where the picture meets the band's edge. On the foot because a picture with air under it floats — cut by the band's own edge it is standing in the band. Rendered when any of `image`, `media` is set, and not otherwise.
+- `image` — `<img>`, class `dds-producthero__image`. The picture, drawn from `image` at its own proportions, as wide as its shape allows up to the frame and no taller than the screen's limit. Rendered only when `image` is set.
 
 Apply these classes from the generated `productHeroParts` constant rather than writing the strings by hand.
 
@@ -83,10 +82,15 @@ 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
 
+### image — `data` `BlockImage`
+
+Use when: The product itself, under the claim and the actions, drawn at the picture's own proportions — a square screenshot stays square, a tall phone stays tall — and only held to the screen's limit: no taller than aspect.portrait of the column on a phone, no taller than half the band from the fold. Never cropped. Give its width and height so the band reserves its shape before it loads. `alt` empty when the claim already names what it shows.
+Never for: The background — that is `backgroundImage`. And beside `media`: one product, one picture. Given both, `image` is drawn and `media` ignored.
+
 ### media — `node`
 
 Accepts: AspectRatio
-Use when: The product itself, under the claim and the actions — in the column, capped to the measure, and whole
+Use when: A product picture in a shape the page fixes on purpose — an AspectRatio box, which keeps its ratio across the column. Prefer `image`, which keeps the picture's own shape and adapts to it.
 Never for: The background. A photograph filling the band is `backgroundImage`; this sits in front of it, in the column, and is never cropped
 
 ### backgroundImage — `string`
@@ -195,25 +199,45 @@ Two things genuinely have no logical form and are not covered by this. A CSS gra
 ## Example
 
 ```tsx
-import { ProductHero, Button, AspectRatio } from '@deriv-com/dds-marketing'
+import { ProductHero, Button } from '@deriv-com/dds-marketing'
 
-<ProductHero backgroundImage="/sample-band-ground.svg" eyebrow="Forex" title="Trade global currencies" description="Speculate on over 50 major, minor and exotic currency pairs, with competitive spreads and 0% commission." actions={<Button variant="primary">Try free demo</Button>} media={<AspectRatio ratio="square" />} />
+<ProductHero backgroundImage="/sample-band-ground.svg" eyebrow="Forex" title="Trade global currencies" description="Speculate on over 50 major, minor and exotic currency pairs, with competitive spreads and 0% commission." actions={<Button variant="primary">Try free demo</Button>} image={{"src":"/sample-card-image.svg","alt":"","width":800,"height":600}} />
 ```
 
 ## In use
 
+### The picture keeps its shape
+
+`image` shows the picture at its own proportions and only limits its height — portrait of the column on a phone, half the band from the fold.
+
+```tsx
+import { AspectRatio, Button, ProductHero } from '@deriv-com/dds-marketing'
+
+// A landscape picture
+<ProductHero backgroundImage="/sample-band-ground.svg" eyebrow="Eyebrow" title="The product this page is about" description="The sentence under the title that says what the claim above it means." actions={<Button variant="primary">Primary action</Button>} image={{"src":"/sample-card-image.svg","alt":"","width":800,"height":600}} />
+
+// A square picture
+<ProductHero backgroundImage="/sample-band-ground.svg" eyebrow="Eyebrow" title="The product this page is about" description="The sentence under the title that says what the claim above it means." actions={<Button variant="primary">Primary action</Button>} image={{"src":"/sample-aspect-art.svg","alt":"","width":1200,"height":1200}} />
+
+// A tall picture, held to the limit
+<ProductHero backgroundImage="/sample-band-ground.svg" eyebrow="Eyebrow" title="The product this page is about" description="The sentence under the title that says what the claim above it means." actions={<Button variant="primary">Primary action</Button>} image={{"src":"/sample-tall-image.svg","alt":"","width":600,"height":900}} />
+
+// A shape fixed on purpose — media, AspectRatio
+<ProductHero backgroundImage="/sample-band-ground.svg" eyebrow="Eyebrow" title="The product this page is about" description="The sentence under the title that says what the claim above it means." actions={<Button variant="primary">Primary action</Button>} media={<AspectRatio ratio="square" />} />
+```
+
 ### The band as a page has it
 
 The photograph, the claim centred over it, and the product under the actions — in the column, capped to the measure, and whole.
 
 ```tsx
-import { AspectRatio, Button, ProductHero } from '@deriv-com/dds-marketing'
+import { Button, ProductHero } from '@deriv-com/dds-marketing'
 
 // The photograph, the claim, and the visual beside it
-<ProductHero backgroundImage="/sample-band-ground.svg" eyebrow="Forex" title="Trade global currencies" description="Speculate on over 50 major, minor and exotic currency pairs, with competitive spreads and 0% commission." actions={<Button variant="primary">Try free demo</Button>} media={<AspectRatio ratio="square" />} />
+<ProductHero backgroundImage="/sample-band-ground.svg" eyebrow="Forex" title="Trade global currencies" description="Speculate on over 50 major, minor and exotic currency pairs, with competitive spreads and 0% commission." actions={<Button variant="primary">Try free demo</Button>} image={{"src":"/sample-card-image.svg","alt":"","width":800,"height":600}} />
 
 // The same band with no photograph, on its own ground
-<ProductHero eyebrow="Forex" title="Trade global currencies" description="Speculate on over 50 major, minor and exotic currency pairs, with competitive spreads and 0% commission." actions={<Button variant="primary">Try free demo</Button>} media={<AspectRatio ratio="square" />} />
+<ProductHero eyebrow="Forex" title="Trade global currencies" description="Speculate on over 50 major, minor and exotic currency pairs, with competitive spreads and 0% commission." actions={<Button variant="primary">Try free demo</Button>} image={{"src":"/sample-card-image.svg","alt":"","width":800,"height":600}} />
 ```
 
 ### How much the band carries