Components

Data modules

Content modules are collapsible containers that display a structured set of data rows — coverages, claims summaries, financial details — inside a consistent shell with a labeled header, data slot rows, and an optional footer CTA.

Stable

Overview & specs

Modules fill the width of their parent container. Use them in right rail panels (340px), main content areas (variable), and detail drawers. They carry a standard elevation shadow to lift them off the page surface.

border-radius: 8px shadow: Module Standard header padding: 12px 16px row padding: 10px 16px footer padding: 12px 16px width: fills container

Component anatomy

① HeaderTitle + optional action (collapse toggle, kebab menu, add button)
② Slot rowLabel on left · Value on right — repeats for each data point
② Slot rowSecondary label · Secondary value
② Slot rowTertiary label · Tertiary value
③ FooterOptional — text link CTA or secondary action button

Collapsed & expanded

Modules are expanded by default. Users can collapse them to reduce visual noise when a data area is not immediately relevant. The header always remains visible.

Expanded

GL Coverage Summary

CarrierLiberty Mutual
Policy #GL-2024-00441
Effective01/01/2025
Expiration12/31/2025
Premium$48,200

Collapsed

GL Coverage Summary

Benefits module example

Benefits modules list individual coverage line items with their limit, deductible, and status. Each row carries a status indicator aligned to the right.

Employee Benefits Summary

Active
Medical — PPO Plan$5,000 OOP max
Dental$2,000 annual max
Vision$250 / year
Life Insurance2× salary
STD / LTD60% of salary
Enrolled employees1,243

Claims data module example

Claims modules surface financial summaries and open item counts. Currency values are right-aligned and use the brand green for key totals.

Claims Financial Summary

Open claims14
Total incurred$2,847,600
Total paid$1,923,440
Total reserved$924,160
Avg. closure time47 days
Loss ratio YTD68.4%

Usage guidance

Do
  • Keep module titles short (2–4 words) — describe the data set, not the action.
  • Right-align numeric values; left-align labels.
  • Make modules collapsible whenever they contain more than 6 rows.
  • Use the footer for secondary CTAs only — never primary actions.
Don't
  • Don't nest modules inside modules.
  • Don't exceed 10 rows without pagination or a "show more" pattern.
  • Don't put form inputs inside a display module — use a form layout instead.
  • Don't use ad hoc spacing — always use the token values.

Design tokens

TokenValueUsage
--radius-md8pxModule corner radius
--shadow-100Module StandardModule box-shadow
--color-border-subtlegray-200Header/row/footer dividers
--color-bg-subtlegray-50Module footer background
--fs-body-sm14pxModule title and row content
--ws-green-01#319B42Key value highlight color