# Tabbed feature carousel

Schema: Design Details SECTION.md v3.2
Website: Calendly
Source: https://calendly.com/
Source section IDs: b1cced45-34b4-4b2f-aacf-1742b616d461, gap-42da61dc-2787-3866
Status: AI analysed; vocabulary promotion is automated

## Builder's note

What makes it work:
- A white two-column card floats over a soft pastel gradient, with text on the left and a product mockup on the right, so the eye lands on one clear focal area.
- Circular icon tabs sit on the card's top edge and bridge into it, linking the controls to the content they change.
- Each tab pairs a feature name, badge, short description, text link and a matching UI mockup, so every state shows real product context in a repeatable slot structure.

What a screenshot can't show:
- On tab change, the content container slides up and fades in the new text and graphics while the icons switch state, seen at about 4-8 seconds in the recording.
- No font sizes, spacing values or animation timings were measured, so the exact type scale and easing are unknown.

Borrow: Attach round icon tabs to the edge of a single floating card, and swap its content in repeatable slots so navigation and content read as one object.
Leave alone: Don't copy Calendly's pastel gradient, blue action colour, specific icons or recap and consultation mockups; use your own palette, icon set and product visuals.

## Classification

- Type: hero
- Layout: Centered floating container with top navigation tabs over a full-width gradient background.
- Styles: soft, gradient, minimal
- Confidence: 95%

## Purpose and structure

A large central UI card with interactive icon tabs across the top, displaying different feature content on a soft gradient background.

Visual signature: Prominent floating white card with circular icon tabs on top, sitting over a soft pastel gradient background.

## Components

- tab navigation
- icon buttons
- UI mockups
- text description
- text link

## Typography

- Display: Calendly Sans — 72px 500
- Heading: Calendly Sans — 60px 500
- Body: Geist — 18px 400

## Functional palette

- Text: text #071A31
- Canvas: canvas #FCFBF8
- Surface: surface #FFFFFF
- Muted-Text: muted text #5F6D77
- Border: border #D8DCE0
- Primary-Action: primary action #4890E3

## Motion evidence

- 4.0–8.0s — The main hero component transitions through different features, sliding its content container up and fading in new text and graphics as the top icons change state. (95% confidence)

## Section quality

Overall: 61.60/100 (Good)
Scored coverage: 100%

- Typography: 62 — Clean hierarchy with large display heading, muted body copy, and consistent label/badge treatment, but matches the typography system used elsewhere on the site with no section-specific innovation. Next tier: Needs a distinct typographic moment unique to this carousel, not just a reuse of global scale/weight pairing.
- Composition: 66 — Well-balanced two-column card layout with floating tab icons bridging into the card, soft gradient backdrop, and clear left-text/right-visual split; consistent across both tab states shown. Next tier: Layout is a fairly standard tabbed-feature card pattern; needs a more distinctive spatial idea (asymmetry, layering, depth) to move into strong/memorable territory.
- Motion: 58 — Gemini confirms a specific timestamped transition (4-8s) where content slides up and fades while icon tabs change state, which is a real but conventional carousel transition. Next tier: Only one generic slide/fade transition is evidenced; no distinctive easing, staggered reveal, or icon-specific micro-interaction is described to justify higher scoring.
- Content: 60 — Each tab pairs a feature name, badge, short description, CTA, and a relevant UI mockup (recap cards, consultation card), giving concrete product context rather than generic placeholder content. Next tier: Content mockups are competent but generic SaaS UI patterns; nothing here feels custom-crafted enough to signal a next-tier content integration.
- Originality: 58 — The floating icon-tab-to-card connector is a nice touch but the overall tabbed carousel over gradient is a widely used SaaS marketing pattern. Next tier: Lacks a signature visual or interaction detail that would be hard to find in competitor sites; the connecting line is the only differentiator and is minor.
- Adaptability: 64 — Structure clearly separates into repeatable tab/content/visual slots with consistent card chrome, making the pattern easy to reproduce with different icons, copy, and mockups. Next tier: No deterministic spacing, radius, or shadow tokens were supplied for this specific section to confirm precision of reuse beyond visual inspection.

Strengths:
- Clear content hierarchy with icon, badge, heading, description, and CTA per tab
- Floating icon tabs visually tethered to the active card create a nice state-indicator detail
- Consistent layout and gradient treatment across different tab contents

Weaknesses:
- Pattern is a common tabbed-feature-carousel template seen across many SaaS marketing sites
- Only one motion transition is evidenced, limiting judgment of overall animation quality
- Visual distinctiveness relies mostly on palette/gradient rather than a structural idea

Why it does not reach the next tier: The section executes a well-worn SaaS tabbed-carousel pattern competently but does not introduce a structural or interaction idea distinct enough from category conventions; motion evidence is limited to a single generic slide/fade, and content mockups use familiar UI card patterns rather than something harder to substitute.

## Adaptation guidance

- Effort: Medium
- Guidance: Rebuild the tab bar and connector line as a reusable component, then swap gradient backgrounds and mockup content per use case; typography and card chrome should follow the site's existing design tokens.

What transfers:
- Icon-tab-to-card connector concept
- Two-column text/visual tab content layout
- Badge + heading + description + CTA content slot pattern

Dependencies:
- Specific gradient background treatment
- Custom UI mockup illustrations per tab
- Calendly Sans/Geist typography pairing

## 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 deterministic spacing, radius, or shadow values were supplied specifically for this section
- Only one motion transition was described with timestamps, limiting full motion assessment
- Cannot verify exact animation easing or duration parameters

## 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: hero
- Source type: hero
- Structure: centered single-column
- Layout: Centered floating container with top navigation tabs over a full-width gradient background.
- Styles: soft, gradient, minimal
- Components: tab navigation, icon buttons, UI mockups, text description, text link
- Purpose: A large central UI card with interactive icon tabs across the top, displaying different feature content on a soft gradient background.
- Visual signature: Prominent floating white card with circular icon tabs on top, sitting over a soft pastel gradient background.
- Place on the page: 4 of 13, after Other (`6f255186-dc8d-4f3a-9c6e-cec6951f780d`), before Feature collection (`calendly-com:WorkflowSteps`)

### Crop and composition

- Crop: 1440×885px; aspect ratio 1.627:1
- Page bounds: 1902–2787px of 13878px
- Guidance: Use a narrow central reading axis and deliberate scale contrast rather than adding unnecessary side content.

### 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": "72px",
      "family": "Calendly Sans",
      "source": "computed",
      "traits": "Regular",
      "weight": "500",
      "evidence": "font-7: computed CSS at 1440×1000; AI role: Calendly Sans, size 72px, weight 500, tight letter-spacing (-2px). Used for the primary hero headline 'All the work around meetings, handled.'.",
      "sampleId": "font-7",
      "confidence": 1,
      "lineHeight": "79.2px",
      "letterSpacing": "-2px"
    },
    {
      "role": "heading",
      "size": "60px",
      "family": "Calendly Sans",
      "source": "computed",
      "traits": "Regular",
      "weight": "500",
      "evidence": "font-3: computed CSS at 1440×1000; AI role: Calendly Sans, size 60px, weight 500, tight letter-spacing (-2px). Used for major section headings like 'Built for people whose work runs on meetings'.",
      "sampleId": "font-3",
      "confidence": 1,
      "lineHeight": "66px",
      "letterSpacing": "-2px"
    },
    {
      "role": "body",
      "size": "18px",
      "family": "Geist",
      "source": "computed",
      "traits": "Regular",
      "weight": "400",
      "evidence": "font-13: computed CSS at 1440×1000; AI role: Geist, size 18px, weight 400. Used for primary body copy, subheadlines, and descriptive text underneath major headings.",
      "sampleId": "font-13",
      "confidence": 0.95,
      "lineHeight": "25.2px",
      "letterSpacing": "normal"
    }
  ]
}
```

### Contextual design review

```json
{
  "status": "client-review-required",
  "checks": {
    "hierarchy": "Does each eyebrow, label and text level add useful information or clarify a necessary decision?",
    "decoration": "Do borders, effects, motion and spacing explain grouping or express a specific idea?",
    "repetition": "Can repeated claims, descriptions or actions be removed without losing needed information?",
    "identity": "What visible relationship between this offer, actual copy, imagery, typography and space gives the composition a convincing identity? Name its contribution and losses; matching ingredients or sparse styling are insufficient.",
    "reference": "Does it retain the source's dominant explanatory effect, media role, type balance and quiet space, not just columns?"
  },
  "heroMedia": {
    "appliesWhen": "A hero relies on focal media. A reasoned no-image hero remains valid and is judged by its visible composition.",
    "plan": "Record the image/headline first impression, actual available asset and crop, source image contribution, replacement contribution and losses before studies.",
    "review": "Does the actual hero suggest an offer, audience and experience appropriate to the whole brief? Quiet copy space or a recognizable subject is insufficient. One activity may lead without depicting all offers; justify its emphasis and resolve misleading implications. Missing assets or uncertain essential effects remain unverified."
  },
  "optionMedia": {
    "appliesWhen": "A section uses imagery to help visitors distinguish choices.",
    "planPerChoice": [
      "visitor distinction",
      "observable image evidence",
      "available asset or unresolved dependency",
      "crop retaining the distinguishing detail"
    ],
    "review": "Inspect the actual images. Shared atmosphere, changed crops or matching cards do not establish choice-specific meaning. If that role fails, resolve assets, choose an executable alternative or record lost/unverified and reject. Text comparison can be valid; it preserves a different contribution."
  },
  "noteCheck": "Check editorial interpretations against the received image; retain conflicts and unknown states instead of inventing selection or image meaning.",
  "decision": "Judge brief fit and positive character separately from layout preservation. Compare actual renders/references; essential lost or unverified effects prevent proceed. Reject either or both weak directions after inspection.",
  "qualityCertified": false
}
```

### Typography preservation review

```json
{
  "beforeStudy": "Use the actual reference image and captured section values to describe what its typography contributes: letter proportions and width, weight and contrast, case, line breaks and text-block shape, scale, spacing and relationship to the image. Label visual observations separately from captured facts and unknowns.",
  "substitution": "Choose an available, permitted face for the brief. Explain any substitute by the source relationships it preserves and any deliberate change; a familiar family, a serif/sans category or a mood label alone is not a justification. Do not copy an unavailable proprietary font or ban a common family merely because it is common.",
  "finalCheck": "Compare the actual rendered headline and supporting type beside this reference at the intended viewport. Check the loaded face/fallback and visible proportions, weight, line breaks, scale, spacing, contrast and image balance. Revise or reject when an essential typographic contribution is lost or unverified; a layout match or a font name is not a typography pass.",
  "unknowns": [
    "Section-specific computed typography was not recorded; website context cannot fill this gap.",
    "Glyph proportions, optical weight, actual line breaks, text-block shape and type-to-image balance require inspection of the reference image.",
    "Actual rendered face, font availability/licensing and responsive typography are not verified by this response."
  ]
}
```

### 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": "#071A31",
      "name": "text",
      "role": "text",
      "source": "computed",
      "evidence": "color-3: computed rgb(7, 26, 49); AI role: Hex #071A31 (deep blue). Used extensively for primary text, headings, and icons on light backgrounds.",
      "sampleId": "color-3",
      "confidence": 1
    },
    {
      "hex": "#FCFBF8",
      "name": "canvas",
      "role": "canvas",
      "source": "computed",
      "evidence": "color-1: computed rgb(252, 251, 248); AI role: Hex #FCFBF8 (off-white). Used as the primary background color for the main page canvas and many sections.",
      "sampleId": "color-1",
      "confidence": 0.95
    },
    {
      "hex": "#FFFFFF",
      "name": "surface",
      "role": "surface",
      "source": "computed",
      "evidence": "color-2: computed rgb(255, 255, 255); AI role: Hex #FFFFFF (white). Used for the navigation bar, feature cards, and floating UI elements to stand out against the off-white canvas or colored backgrounds.",
      "sampleId": "color-2",
      "confidence": 0.95
    },
    {
      "hex": "#5F6D77",
      "name": "muted text",
      "role": "muted-text",
      "source": "computed",
      "evidence": "color-6: computed rgb(95, 109, 119); AI role: Hex #5F6D77 (grey). Used for secondary text, descriptions, and supporting copy.",
      "sampleId": "color-6",
      "confidence": 0.9
    },
    {
      "hex": "#D8DCE0",
      "name": "border",
      "role": "border",
      "source": "computed",
      "evidence": "color-25: computed rgb(216, 220, 224); AI role: Hex #D8DCE0 (light grey). Used for subtle borders around cards and list items.",
      "sampleId": "color-25",
      "confidence": 0.8
    },
    {
      "hex": "#4890E3",
      "name": "primary action",
      "role": "primary-action",
      "source": "computed",
      "evidence": "color-31: computed rgb(72, 144, 227); AI role: Hex #4890E3 (bright blue). Used as an accent or interaction color, though dark blue (#071A31 or #0B0D0F) is often used for primary buttons.",
      "sampleId": "color-31",
      "confidence": 0.7
    }
  ]
}
```

### Design tokens

```json
{
  "radius": "Large border radii, often appearing pill-shaped for smaller buttons/badges or with substantial rounded corners (likely 24px-32px or more) for large structural containers and feature cards.",
  "density": "Low density. The layout prioritizes large type, substantial whitespace, and prominent visuals over packing information tightly.",
  "evidence": "Observation of large gaps between text and visuals, consistent rounding on the navigation bar, hero graphic containers, and the CTA buttons. The prominent use of large, bold headings with ample line height.",
  "borderStyle": "Subtle. Borders are used sparingly, usually as a 1px solid line in a light grey or muted color to delineate sections or card edges without being visually heavy.",
  "buttonStyle": "Solid fill with deep blue or dark grey, rounded corners (often pill-shaped), and white text for primary actions. Outline variants are used for secondary actions like 'Log In'.",
  "cornerStyle": "Highly rounded. Cards, buttons, and floating UI elements feature prominent border radii, contributing to the 'soft' aesthetic.",
  "contentWidth": "Restricted central column for main text content to maintain readability, while visual elements, carousels, and section backgrounds frequently extend wider or full-width.",
  "spacingRhythm": "Generous spacing. Sections are separated by significant vertical padding, allowing content to breathe. Margins within components are also substantial, emphasizing readability and a clean layout."
}
```

### 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": 1902,
      "bottom": 2787,
      "pageHeight": 13878
    }
  },
  "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": 1902,
    "bottom": 2787,
    "pageHeight": 13878
  },
  "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-10-07T06:35:21.501Z",
  "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

1. **observed sequence** — The main hero component transitions through different features, sliding its content container up and fading in new text and graphics as the top icons change state. (4s–8s; 95% confidence). Recreate the interaction principle with project-appropriate timing and easing; the evidence does not guarantee source easing values.

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

These categories describe evidence, not independent layers that can be swapped without changing the design. Study the complete reference system before adapting it.

- Preserve: content hierarchy, layout relationships, section rhythm, interaction purpose.
- Adapt: brand colors, font family, copy, imagery, icons, decorative details.
- Rule: These compatibility categories are coupled: fonts, color and imagery can carry the layout's design logic. Preserve or purposefully replace their contribution while creating original branding, copy, assets, and implementation details.

### Adaptation and dependencies

- Effort: medium
- What transfers: Icon-tab-to-card connector concept; Two-column text/visual tab content layout; Badge + heading + description + CTA content slot pattern
- Dependencies: Specific gradient background treatment; Custom UI mockup illustrations per tab; Calendly Sans/Geist typography pairing
- Guidance: Rebuild the tab bar and connector line as a reusable component, then swap gradient backgrounds and mockup content per use case; typography and card chrome should follow the site's existing design tokens.

### Evidence readiness

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

### Agent implementation prompt

Create an original hero section inspired by the design evidence titled “Tabbed feature carousel”.

Purpose: A large central UI card with interactive icon tabs across the top, displaying different feature content on a soft gradient background.

Structure: centered single-column. Source layout label: Centered floating container with top navigation tabs over a full-width gradient background.. Use a narrow central reading axis and deliberate scale contrast rather than adding unnecessary side content.

Visual signature to preserve at the pattern level: Prominent floating white card with circular icon tabs on top, sitting over a soft pastel gradient background.

Components: tab navigation, icon buttons, UI mockups, text description, text link.

Style direction: soft, gradient, minimal.

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

Typography evidence: {"role":"display","size":"72px","family":"Calendly Sans","source":"computed","traits":"Regular","weight":"500","evidence":"font-7: computed CSS at 1440×1000; AI role: Calendly Sans, size 72px, weight 500, tight letter-spacing (-2px). Used for the primary hero headline 'All the work around meetings, handled.'.","sampleId":"font-7","confidence":1,"lineHeight":"79.2px","letterSpacing":"-2px"} {"role":"heading","size":"60px","family":"Calendly Sans","source":"computed","traits":"Regular","weight":"500","evidence":"font-3: computed CSS at 1440×1000; AI role: Calendly Sans, size 60px, weight 500, tight letter-spacing (-2px). Used for major section headings like 'Built for people whose work runs on meetings'.","sampleId":"font-3","confidence":1,"lineHeight":"66px","letterSpacing":"-2px"} {"role":"body","size":"18px","family":"Geist","source":"computed","traits":"Regular","weight":"400","evidence":"font-13: computed CSS at 1440×1000; AI role: Geist, size 18px, weight 400. Used for primary body copy, subheadlines, and descriptive text underneath major headings.","sampleId":"font-13","confidence":0.95,"lineHeight":"25.2px","letterSpacing":"normal"}

Color evidence: {"hex":"#071A31","name":"text","role":"text","source":"computed","evidence":"color-3: computed rgb(7, 26, 49); AI role: Hex #071A31 (deep blue). Used extensively for primary text, headings, and icons on light backgrounds.","sampleId":"color-3","confidence":1} {"hex":"#FCFBF8","name":"canvas","role":"canvas","source":"computed","evidence":"color-1: computed rgb(252, 251, 248); AI role: Hex #FCFBF8 (off-white). Used as the primary background color for the main page canvas and many sections.","sampleId":"color-1","confidence":0.95} {"hex":"#FFFFFF","name":"surface","role":"surface","source":"computed","evidence":"color-2: computed rgb(255, 255, 255); AI role: Hex #FFFFFF (white). Used for the navigation bar, feature cards, and floating UI elements to stand out against the off-white canvas or colored backgrounds.","sampleId":"color-2","confidence":0.95} {"hex":"#5F6D77","name":"muted text","role":"muted-text","source":"computed","evidence":"color-6: computed rgb(95, 109, 119); AI role: Hex #5F6D77 (grey). Used for secondary text, descriptions, and supporting copy.","sampleId":"color-6","confidence":0.9} {"hex":"#D8DCE0","name":"border","role":"border","source":"computed","evidence":"color-25: computed rgb(216, 220, 224); AI role: Hex #D8DCE0 (light grey). Used for subtle borders around cards and list items.","sampleId":"color-25","confidence":0.8} {"hex":"#4890E3","name":"primary action","role":"primary-action","source":"computed","evidence":"color-31: computed rgb(72, 144, 227); AI role: Hex #4890E3 (bright blue). Used as an accent or interaction color, though dark blue (#071A31 or #0B0D0F) is often used for primary buttons.","sampleId":"color-31","confidence":0.7}

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":[]}

Motion evidence: observed sequence: The main hero component transitions through different features, sliding its content container up and fading in new text and graphics as the top icons change state. (95% confidence)

Transfer these principles: Icon-tab-to-card connector concept; Two-column text/visual tab content layout; Badge + heading + description + CTA content slot pattern.

Dependencies: Specific gradient background treatment; Custom UI mockup illustrations per tab; Calendly Sans/Geist typography pairing.

Adaptation guidance: Rebuild the tab bar and connector line as a reusable component, then swap gradient backgrounds and mockup content per use case; typography and card chrome should follow the site's existing design tokens.

Study layout, typography, color, imagery and spacing as one coordinated source system. Record what creates its effect before producing a concept; preserve or purposefully replace each consequential relationship when adapting the business content and assets.

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