# Minimal FAQ accordion

Schema: Design Details SECTION.md v3.2
Website: Kelvin
Source: https://kelvin.8b.com/
Source section IDs: 7e06d403-e846-487a-bc0f-c1c79d991c69
Status: AI analysed; vocabulary promotion is automated

## Builder's note

What makes it work:
- The two-column split gives the heading and intro their own space, while the question list stays easy to scan on the right.
- A large display serif heading set against plain sans-serif question rows creates clear contrast between brand voice and utility.
- Thin horizontal rules and one plus icon per row keep the list quiet, and the questions are specific to the event, with the contact email placed inside the intro.

What a screenshot can't show:
- The recording showed no motion, so the expand/collapse timing and the plus-to-minus change can't be confirmed from it.
- No measured spacing or type sizes were captured, apart from the heading's roughly 86px size with tight tracking.

Borrow: Pair one expressive display heading with a deliberately plain, rule-divided list so the personality sits in one place and the utility stays clear.
Leave alone: Don't copy the Kalnia quirky serif, the warm cream and near-black palette, or the festival-specific questions; use a different characterful serif and your own content.

## Classification

- Type: faq
- Layout: A 2-column layout dividing the title/intro text from a vertical stack of collapsible question rows.
- Styles: minimal, typographic, editorial
- Confidence: 100%

## Purpose and structure

A straightforward frequently asked questions section with a heading on the left and an interactive accordion on the right.

Visual signature: Very sparse, utilizing horizontal lines to separate questions and simple plus signs for interaction.

## Components

- Section heading
- Contact email link
- Accordion question rows
- Expand/collapse icons (+/-)

## Typography

- Display: Kalnia — 86.4px 200
- Heading: Hubot Sans — 34.6px 800
- Body: Hubot Sans — 17px 400

## Functional palette

- Canvas: canvas #F1EDE4
- Text: text #110D19
- Muted-Text: muted text #5B5664

## Motion evidence

- No section-specific authored motion was established.

## Section quality

Overall: 58.41/100 (Competent)
Scored coverage: 85%

- Typography: 64 — Pairs a quirky-serif display face (Kalnia, 86px, tight tracking) against bold uppercase-free sans-serif question rows, giving clear voice contrast between brand personality and utilitarian list text. Hierarchy is clean but type choices alone don't push past polished execution. Next tier: Needs more typographic nuance (e.g. varied weight/size in answers, refined baseline alignment with icons) to feel distinctive rather than a well-set default pairing.
- Composition: 62 — Simple, confident two-column split with left-aligned heading/intro and right-aligned question list bound by thin horizontal rules; generous whitespace lets the display type breathe. Alignment is consistent and grid-based, but the layout is a very common FAQ pattern without a distinguishing compositional idea. Next tier: Lacks an asymmetry, scale shift, or unexpected spatial relationship between the two columns that would elevate it beyond a standard two-column FAQ template.
- Motion: not_assessed — No motion_moments or animation data supplied; accordion expand/collapse behavior is implied by +/- icons but no timestamped visible change is given. Next tier: Needs timestamped evidence of the actual expand/collapse transition (easing, icon rotation, height animation) to assess.
- Content: 58 — Questions are specific to the festival context (filming, heat, accessibility) rather than generic placeholder FAQs, and the contact email is integrated naturally into the intro paragraph, giving it a human, site-specific feel. Next tier: Content integration is functional but doesn't do anything structurally interesting beyond listing Q&A; no supporting visual or data tying content to the broader site system.
- Originality: 45 — The plus-icon accordion with horizontal dividers is a widely used FAQ convention; the only differentiator is the display serif heading, which is a styling choice rather than a structural or interactive innovation. Next tier: Needs a structural or interaction twist (e.g. unconventional reveal, unique icon treatment, atypical column ratio) that isn't just a recognizable accordion pattern.
- Adaptability: 60 — Clear separation of heading block, intro/contact link, and repeatable accordion row component with consistent spacing and a single shared border/icon treatment makes the structure easy to reskin or extend with more rows. Next tier: Dependence on the specific display typeface for personality and lack of documented interaction parameters limit how cleanly the skin can be swapped without design judgment calls.

Strengths:
- Confident type pairing between expressive serif heading and clean uppercase-free sans for list items creates immediate hierarchy
- Thin horizontal rule dividers keep the list airy and legible without boxy card treatments
- Contextual, specific questions and embedded contact email ground the section in the actual event rather than generic FAQ copy

Weaknesses:
- Two-column FAQ-with-accordion is an extremely common pattern with no structural differentiation
- No evidence of motion/transition quality for the accordion interaction
- Answer content/expanded state not shown, limiting judgment of full interaction design
- Relies heavily on the display typeface for personality rather than composition or interaction

Why it does not reach the next tier: The section executes a familiar FAQ accordion cleanly with good typographic contrast and specific content, but it does not introduce any structural, interactive, or compositional idea beyond the convention — it reads as well-crafted but substitutable.

## Adaptation guidance

- Effort: Low
- Guidance: Rebuild the layout skeleton (left intro, right accordion list with rule dividers) freely; swap in any serif/sans pairing with similar scale contrast, and define your own expand/collapse transition since none was captured.

What transfers:
- Two-column heading-plus-accordion layout
- Thin rule divider list structure
- Plus/minus icon expand affordance pattern

Dependencies:
- Specific display serif typeface for heading personality
- Exact palette (beige canvas, dark text) for mood
- Unknown accordion animation timing/easing

## Living vocabulary

- No reusable vocabulary candidates were supported by this section.

Only terms with status `active` enter the public taxonomy. Deferred and proposed terms remain available to later AI passes; rejected terms remain as provenance so they are not repeatedly reinvented.

## Provenance and limitations

- Section boundaries and naming: Gemini Pro visual observation
- Motion observations: Gemini Pro direct-video analysis
- Quality judgment: Claude
- Exact design facts: browser/CSS extraction at website scope
- Rubric: Design Details section rubric 3.2 (Typography 20%, Composition 20%, Motion 15%, Content 15%, Originality 15%, Adaptability 15%)
- No visible expanded/open state or answer text provided
- No animation timing data for the accordion transition
- Only desktop viewport evidence available

## Usage guidance

Use this section as design evidence. Create an original implementation; do not reproduce the source copy, assets, or proprietary composition exactly.

## Build blueprint v3.2

### Purpose and classification

- Canonical type: faq
- Source type: faq
- Structure: two-column
- Layout: A 2-column layout dividing the title/intro text from a vertical stack of collapsible question rows.
- Styles: minimal, typographic, editorial
- Components: Section heading, Contact email link, Accordion question rows, Expand/collapse icons (+/-)
- Purpose: A straightforward frequently asked questions section with a heading on the left and an interactive accordion on the right.
- Visual signature: Very sparse, utilizing horizontal lines to separate questions and simple plus signs for interaction.
- Place on the page: 9 of 11, after Pricing (`kelvin-8b-com:C08`), before Contact (`kelvin-8b-com:C10`)

### Crop and composition

- Crop: 1440×738px; aspect ratio 1.951:1
- Page bounds: 10571–11309px of 13551px
- Guidance: Preserve the visual relationship between the two columns; adapt their ratio to the new content instead of copying the source dimensions.

### Exact typography evidence

The sectionScale values were measured inside this crop. The siteRoles values explain how those faces function across the source website; they must not replace section measurements.

```json
{
  "sectionScale": [],
  "siteRoles": [
    {
      "role": "display",
      "size": "86.4px",
      "family": "Kalnia",
      "source": "computed",
      "traits": "Regular",
      "weight": "200",
      "evidence": "font-5: computed CSS at 1440×1000; AI role: Kalnia (serif), 200 weight, 86.4px. Used for elegant, prominent section headings like 'Every set is filmed in heat.'",
      "sampleId": "font-5",
      "confidence": 0.95,
      "lineHeight": "88.1px",
      "letterSpacing": "-1.7px"
    },
    {
      "role": "heading",
      "size": "34.6px",
      "family": "Hubot Sans",
      "source": "computed",
      "traits": "uppercase",
      "weight": "800",
      "evidence": "font-2: computed CSS at 1440×1000; AI role: Hubot Sans, 800 weight, 34.6px uppercase. Used for strong subheadings and pricing titles.",
      "sampleId": "font-2",
      "confidence": 0.9,
      "lineHeight": "31.8px",
      "letterSpacing": "0.2px"
    },
    {
      "role": "body",
      "size": "17px",
      "family": "Hubot Sans",
      "source": "computed",
      "traits": "Regular",
      "weight": "400",
      "evidence": "font-12: computed CSS at 1440×1000; AI role: Hubot Sans, 400 weight, 17px. Used for standard descriptive paragraphs and text blocks.",
      "sampleId": "font-12",
      "confidence": 0.95,
      "lineHeight": "26.4px",
      "letterSpacing": "normal"
    }
  ]
}
```

### Exact color evidence

The section samples record where each computed value was used. Functional roles come from the website-level classifier and remain separate.

```json
{
  "sectionUsage": [],
  "functionalPalette": [
    {
      "hex": "#F1EDE4",
      "name": "canvas",
      "role": "canvas",
      "source": "computed",
      "evidence": "color-1: computed rgb(241, 237, 228); AI role: Light beige (#F1EDE4) used as the primary background for the upper half of the page.",
      "sampleId": "color-1",
      "confidence": 0.95
    },
    {
      "hex": "#110D19",
      "name": "text",
      "role": "text",
      "source": "computed",
      "evidence": "color-2: computed rgb(17, 13, 25); AI role: Dark (#110D19) used for high-contrast typography on light backgrounds and as the canvas for the dark sections.",
      "sampleId": "color-2",
      "confidence": 0.9
    },
    {
      "hex": "#5B5664",
      "name": "muted text",
      "role": "muted-text",
      "source": "computed",
      "evidence": "color-4: computed rgb(91, 86, 100); AI role: Grey (#5B5664) used for secondary paragraph text and subtitles to lower visual hierarchy.",
      "sampleId": "color-4",
      "confidence": 0.8
    }
  ]
}
```

### Design tokens

```json
{
  "radius": "0px, no border-radius visible.",
  "density": "Low density; ample negative space emphasizes the scale of the typography and vibrancy of the images.",
  "evidence": "Visual inspection of stat blocks (fine lines), button shapes (sharp), and section pacing confirms these tokens.",
  "borderStyle": "Thin (1px), solid borders used extensively as structural dividers in lists, stats, and tables.",
  "buttonStyle": "Solid, sharp-edged rectangles (often black on light, or white on dark) containing bold, uppercase, highly-tracked sans-serif text.",
  "cornerStyle": "Strictly sharp corners across all buttons, images, and layout containers.",
  "contentWidth": "Wide max-width with elements often breaking the grid or spanning full viewport width, but maintaining alignment down central columns.",
  "spacingRhythm": "Generous spacing with large macro-margins between sections, allowing the large typography and imagery to breathe."
}
```

### Reconstruction specification

This is the implementation contract for the captured desktop viewport. Prefer section-specific facts here over general website descriptions.

- Root container was not deterministically isolated.
- Layout containers: 0; cards/surfaces: 0; media elements: 0; browser animations: 0.

#### Container, grid, and spacing

```json
{
  "viewport": {
    "width": 1440,
    "captureBounds": {
      "top": 10571,
      "bottom": 11309,
      "pageHeight": 13551
    }
  },
  "container": null,
  "spacing": {
    "observedGapsPx": [],
    "representativeContentWidthsPx": []
  },
  "columns": []
}
```

#### Cards and surfaces

```json
{
  "cards": [],
  "surfaces": {
    "radii": [],
    "borders": [],
    "shadows": []
  }
}
```

#### Media treatment

```json
[]
```

#### Browser-exposed animation parameters

```json
[]
```

### Measured geometry, surfaces, media, and animation

These raw values come from the saved element map and computed styles. Empty arrays mean the fact was not captured; they are not permission to invent source values.

```json
{
  "root": null,
  "cards": [],
  "media": [],
  "bounds": {
    "top": 10571,
    "bottom": 11309,
    "pageHeight": 13551
  },
  "schema": "little-details-section-measurements-v1",
  "source": "saved DOM/CSS element and animation maps",
  "columns": [],
  "spacing": {
    "gapsPx": [],
    "representativeContentWidthsPx": []
  },
  "coverage": {
    "cards": 0,
    "media": 0,
    "animations": 0,
    "elementsInSection": 0
  },
  "surfaces": {
    "radii": [],
    "borders": [],
    "shadows": []
  },
  "animations": [],
  "capturedAt": "2026-11-01T08:13:50.678Z",
  "limitations": [
    "Values describe the captured desktop viewport and may change at other breakpoints.",
    "Transforms, sticky layers, and virtualized content can make the inferred section root approximate.",
    "Animations include browser-exposed Web Animations API state; CSS or script motion that was inactive at capture time may be absent."
  ],
  "viewportWidth": 1440
}
```

### Observed motion

No timestamped authored motion is attached. Use only restrained baseline transitions.

The browser animation records above are deterministic parameters captured from active browser animations. The timestamped observations describe what Gemini saw in the video. Treat them as complementary evidence. When either source is empty or they conflict, state the uncertainty instead of inventing timing or easing.

### Responsive contract

- Measured viewport: 1440px wide.
- Mobile/tablet values: not measured by this section evidence unless a separate capture is explicitly listed.
- Preserve hierarchy and sequence; collapse simultaneous columns only where needed, maintain media aspect ratios, and verify touch targets and text wrapping at target breakpoints.

### Structure versus visual skin

- Preserve: content hierarchy, layout relationships, section rhythm, interaction purpose.
- Adapt: brand colors, font family, copy, imagery, icons, decorative details.
- Rule: Preserve the observed design logic while creating original branding, copy, assets, and implementation details.

### Adaptation and dependencies

- Effort: low
- What transfers: Two-column heading-plus-accordion layout; Thin rule divider list structure; Plus/minus icon expand affordance pattern
- Dependencies: Specific display serif typeface for heading personality; Exact palette (beige canvas, dark text) for mood; Unknown accordion animation timing/easing
- Guidance: Rebuild the layout skeleton (left intro, right accordion list with rule dividers) freely; swap in any serif/sans pairing with similar scale contrast, and define your own expand/collapse transition since none was captured.

### Evidence readiness

- Coverage: 6/7
- Can build: Yes
- Missing facts: section-specific computed typography and color samples; timestamped authored motion
- Warning: Buildable with adaptations for these unsupported facts: section-specific computed typography and color samples; timestamped authored motion.

### Agent implementation prompt

Create an original faq section inspired by the design evidence titled “Minimal FAQ accordion”.

Purpose: A straightforward frequently asked questions section with a heading on the left and an interactive accordion on the right.

Structure: two-column. Source layout label: A 2-column layout dividing the title/intro text from a vertical stack of collapsible question rows.. Preserve the visual relationship between the two columns; adapt their ratio to the new content instead of copying the source dimensions.

Visual signature to preserve at the pattern level: Very sparse, utilizing horizontal lines to separate questions and simple plus signs for interaction.

Components: Section heading, Contact email link, Accordion question rows, Expand/collapse icons (+/-).

Style direction: minimal, typographic, editorial.

Observed crop: 1440×738px (1.951:1). Treat this as evidence of composition, not a mandatory output size.

Typography evidence: {"role":"display","size":"86.4px","family":"Kalnia","source":"computed","traits":"Regular","weight":"200","evidence":"font-5: computed CSS at 1440×1000; AI role: Kalnia (serif), 200 weight, 86.4px. Used for elegant, prominent section headings like 'Every set is filmed in heat.'","sampleId":"font-5","confidence":0.95,"lineHeight":"88.1px","letterSpacing":"-1.7px"} {"role":"heading","size":"34.6px","family":"Hubot Sans","source":"computed","traits":"uppercase","weight":"800","evidence":"font-2: computed CSS at 1440×1000; AI role: Hubot Sans, 800 weight, 34.6px uppercase. Used for strong subheadings and pricing titles.","sampleId":"font-2","confidence":0.9,"lineHeight":"31.8px","letterSpacing":"0.2px"} {"role":"body","size":"17px","family":"Hubot Sans","source":"computed","traits":"Regular","weight":"400","evidence":"font-12: computed CSS at 1440×1000; AI role: Hubot Sans, 400 weight, 17px. Used for standard descriptive paragraphs and text blocks.","sampleId":"font-12","confidence":0.95,"lineHeight":"26.4px","letterSpacing":"normal"}

Color evidence: {"hex":"#F1EDE4","name":"canvas","role":"canvas","source":"computed","evidence":"color-1: computed rgb(241, 237, 228); AI role: Light beige (#F1EDE4) used as the primary background for the upper half of the page.","sampleId":"color-1","confidence":0.95} {"hex":"#110D19","name":"text","role":"text","source":"computed","evidence":"color-2: computed rgb(17, 13, 25); AI role: Dark (#110D19) used for high-contrast typography on light backgrounds and as the canvas for the dark sections.","sampleId":"color-2","confidence":0.9} {"hex":"#5B5664","name":"muted text","role":"muted-text","source":"computed","evidence":"color-4: computed rgb(91, 86, 100); AI role: Grey (#5B5664) used for secondary paragraph text and subtitles to lower visual hierarchy.","sampleId":"color-4","confidence":0.8}

No section-bounded typography samples were measured.

No section-bounded color samples were measured.

Exact section measurements from the saved element map: spacing {"gapsPx":[],"representativeContentWidthsPx":[]}; surfaces {"radii":[],"borders":[],"shadows":[]}

Do not invent signature motion. Use only restrained baseline transitions if the product needs them.

Transfer these principles: Two-column heading-plus-accordion layout; Thin rule divider list structure; Plus/minus icon expand affordance pattern.

Dependencies: Specific display serif typeface for heading personality; Exact palette (beige canvas, dark text) for mood; Unknown accordion animation timing/easing.

Adaptation guidance: Rebuild the layout skeleton (left intro, right accordion list with rule dividers) freely; swap in any serif/sans pairing with similar scale contrast, and define your own expand/collapse transition since none was captured.

Use new copy, imagery, branding, and implementation details. Do not reproduce the source website or its proprietary assets.
