Design System & UI

Design Philosophy

ComplianceCheck is a professional, high-trust tool for compliance teams. The UI must convey clarity, precision, and governance. It should feel authoritative without being intimidating — compliance work is serious, and the interface should reflect that.

Aesthetic: Clean, minimal, professional. Think regulated industry (finance, pharma) meets modern SaaS. Typography-driven, generous whitespace, subtle shadows, data-forward (tables and lists are primary UI components).

Color Palette

ColorHexUse Case
Primary Navy#0F2A4AHeaders, navigation, primary buttons, key data emphasis
Off-White Surface#F7F5F1Page background, subtle section dividers
Gold Accent#B8922AStatus badges, CTAs, highlights, approval indicators
Text Primary#111111Body text, headings, critical data
Text Secondary#4A4A4ADescriptive text, metadata, table cells
Text Tertiary#6B7280Hints, labels, less important context
Success Green#10B981Passed checks, approved status, positive indicators
Warning Red#EF4444Failed checks, critical findings, errors
Border/Divider#E5E1DBTable borders, card separators, subtle lines

Typography

ElementFont FamilySizeWeightUse
Display (H1)Playfair Display2.5rem700Page titles
Heading 2 (H2)Playfair Display2rem700Section titles
Heading 3 (H3)Playfair Display1.5rem700Subsection titles, card headers
Body TextInter1rem400Paragraphs, descriptions
Small TextInter0.875rem400Metadata, labels, hints
Code/MonospaceCourier New0.9rem400Code snippets, IDs, technical values

Spacing Scale

All spacing based on 8px base unit:

Components

Buttons

Cards

Tables

Badges

Forms

Status Indicators

Page Layouts

Dashboard (Auditor)

Layout: Sidebar nav + main content

Audit Detail View

Layout: Horizontal tabs + findings table

Finding Review

Layout: Two-column (finding detail + document preview)

Approval View (Manager)

Layout: Audit summary + approval form

Responsive Design

Primary use case: Desktop and tablet (compliance team at workstations). Mobile is secondary but should not break.

Next step: Once build team is defined, create detailed Figma/design system file with all components, states, and interactions. Design system assets to be shared with frontend team as a reference.