Problem section

States the problem: the claim with the drift palette showcase, three sourced figures, the source line, three short cards and the link.

Template · stable · v1.0.0 · owner: Site system lead · contract 19 of 20 points (open: figma)

Do and don't

Do: The landing problem

Rendered by problem-section.ts

Open example: Problem section · Do: The landing problem Use the full-page example to follow page links.

Claim, picture, figures with sources.

Do: Cards

Rendered by problem-section.ts

Open example: Problem section · Do: Cards Use the full-page example to follow page links.

Three causes.

Don't: Unsourced figures

Rendered by problem-section.ts

Open example: Problem section · Don't: Unsourced figures Use the full-page example to follow page links.

Every number has its source line.

Don't: Fear copy

Rendered by problem-section.ts

Open example: Problem section · Don't: Fear copy Use the full-page example to follow page links.

State the problem plainly.

Rules

RuleWhyCheck
Every figure has its source in the source line.Numbers without sources erode trust.Automated: tests/site/site-claims.spec.ts

API

PropTypeRequiredDefaultWhat it does
idstringYesSection id.
headinghtmlYesThe h2.
copyhtmlYesThe claim.
fightmlYesThe drift palette showcase.
figslistYesSourced figures (n, text).
sourcehtmlYesThe source line (Caption source).
cardslistYesCards (title, html).
linkhtmlNoThe arrow link.

Contract details

The full contract: identity, anatomy, variants, states, tokens, layout, motion, accessibility, content, tests

Identity

AspectValue
Idproblem-section
LayerTemplates
Categorysection
OwnerSite system lead
Statusstable
Version1.0.0
Sourceapps/showcase/site/system/templates/problem-section.ts (private repository; the contract and the render function are this one module)
VersionDateChange
1.0.02026-10-26Problem section as one module: its markup moved out of the page builder (scripts/site) into the system.

Use when

  • The landing's problem, after the hero. Why: The reader must recognise the problem before the answer.

Do not use when

  • For product features. Why: This template states a problem; features use Job sections.

Anatomy

PartWhat it is
rootsection.l-problem.l-drift on cotton, named by its h2
headdiv.l-drift-head: div.l-drift-copy (h2 and copy), div.l-drift-fig (the Drift palette)
figsol.figs.l-drift-figs: b figure and span text
sourcediv.l-drift-source
cardsul.l-drift-cards: h3 and p
linkArrowLink

Made of: heading, text, caption, drift-palette, arrow-link.

Used in: page-landing.

Variants

VariantWhenWhy
defaultWherever the page declaration places it.One shape per job keeps pages predictable.

States

StateRendered or not applicable
defaultdefault
hoverNot applicable: The problem section is not interactive, so it has no hover state.
focus-visibleNot applicable: The problem section does not take focus; links and buttons inside it carry their own focus ring.
activeNot applicable: The problem section cannot be pressed.
disabledNot applicable: The problem section has nothing to disable.
loadingNot applicable: The problem section is rendered at build time and is complete when the page loads.
emptyNot applicable: The problem section is not rendered without content; the builder skips it.
errorNot applicable: The problem section shows no data that can fail.
currentNot applicable: The problem section has no current item.
visitedNot applicable: The problem section is not a link.
expandedNot applicable: The problem section does not open or close.

Tokens

PartToken
root.background--cotton
figure.font--type-h2
figure.mark--madder-ink (a state mark: trouble)
card.rule--rule --madder

Layout

AspectValue
breakpointsRequired review at 390, 768, 1024 and 1440 px; execution is not implied by this declaration; columns stack under 768 px; the wrap keeps a 16 px gutter on phones.
wrappingText wraps; nothing scrolls sideways.
textExpansionJapanese runs 20 to 40% longer; headings break between phrases (jaBreaks) and blocks grow downwards.

Spacing and rhythm

AspectValue
internalOne padding: --section (D-SITE-005).
externalFull bleed.
rhythmOn cotton after the indigo hero (the composer puts the woven edge between them); madder appears only as marks.

Motion

AspectValue
NoneNo intrinsic element animation. The optional claude-entrance consumer profile may translate below-fold structure once (20px, --dur-weave, --ease-enter, --stagger); reduced motion disables it. This preserved baseline entrance is separate from element playback.

Runtime and reuse

  1. Render-only element; mount any registered child enhancements separately. Preserve required Site CSS, fonts, responsive and locale rules from nativeElement.

Accessibility passport

AspectValue
roleregion (section) named by its heading
nameIts h2, by aria-labelledby
keyboardLinks and buttons inside, in reading order.
focusThe --focus ring on every link and button inside.
screenReaderRead in source order; decorative weaving is aria-hidden.
contrastInk on cotton 14:1; text on every dye field 4.5:1 or better (checked by check-brand).
targetLinks and buttons are 44 px tall.

Content

SlotLengthVoice
figure4 charactersA sourced number
card2 sentencesOne cause

Good: “16% · of components are rebuilt by teams who could not find them (source).”

Bad: “Most teams struggle”

Japanese: Figures and sources translated; numbers unchanged.

Icons and illustrations

None: this element uses no icon or illustration of its own.

Decisions and exceptions

Usage

16 uses across the built pages (measured by npm run site:system).

Tests

AspectValue
unittests/unit/site-system.test.ts: renders every do and don't example through the registry and checks the classes it owns
visualNot yet: there are no screenshot baselines; the Library page is checked for sideways scroll at 1440 px by tests/site/system.spec.ts
a11ytests/site/system.spec.ts: axe (0 serious or critical) on the element's Library page in light and dark
parityscripts/site/system/check.ts: Library examples are rendered by the same render function the site imports

Figma

not-yet: The Loom Site Figma library is the last stage of the plan; this element is not mapped yet.

Open in Storybook

Start with a conversation about your system.

We read your system, show you what we found, and agree with your team what to fix first.