DQ®

Portfolio system / Proposed direction

Review components

04 / Glass utility

A clear operating layer for evidence, decisions, and momentum.

A high-clarity product system with editorial typography, chartreuse action signals, and restrained frosted layers over a warm canvas.

Explore system
01

One action color

02

Utility-led motion

03

Glass with structure

Foundational elements / Proposed tokens

The decisions behind the surface.

Proposed glass-utility translation; glass is constrained to navigation and raised surfaces so content contrast remains stable.

01

Color palette

Semantic roles, usage and minimum contrast.

Canvascanvas.default
#F1EEE8Warm field
Ink 14.03:1 · AAA
Inktext.primary
#22201DText + structure
Canvas 14.03:1 · AAA
Limebrand.primary
#C9F33BPrimary action
Ink 12.66:1 · AAA
Redstatus.error
#B9362BValidation
White 5.79:1 · AA

Rule: body text targets WCAG AA 4.5:1; large text 3:1; focus and component boundaries 3:1. Status never relies on color alone.

02

Typography scale

Family, weight, size, leading and tracking.

RoleFamily / weightSize / lineTracking
DisplayInter45064–96px0.98−0.05em
H2Inter45048–76px1−0.045em
BodyInter40016–20px1.550
Data labelJetBrains Mono50011px1.4+0.08em
03

Spacing & layout

4px base scale with bounded responsive decisions.

0px 4px 8px 12px 16px 24px 32px 48px 64px 96px 128px
Grid
12 columns / 72px guide
Gutter
16px
Page padding
64px → 18px
Max width
1440px
Section gap
96–168px
04

Assets & motion

One visual vocabulary and one response grammar.

Icons
1.5px utility outline; 20px default box
Logo
Ink-only on light glass; white on dark
Images
Crisp product evidence; no blur over readable UI
Illustration
Diagrammatic, grid-aligned, one accent
Hover
150ms · ease-out
Press
scale .97 · 120ms
Enter
300–400ms · utility fade
Reduced
Glass remains; movement removed

Component stress test

One system, every state.

Visible state inventory, exact geometry and equivalent content across all five directions.

Control height46 / 52px
Control padding0 × 18px
Panel padding44px desktop / 24px mobile
Radius16px panel / 7px control

01 / Button

Action hierarchy

PrimarySecondaryQuietHoverFocusPressedDisabledLoading

02 / Text field

Every validation state

Use dots instead of spaces.

03 / Disclosure

Rules stay close

Why is this component shared?

It expresses the same intent in repeated, accepted use and preserves keyboard behavior without custom state.

What stays local?

Project evidence, brand treatments, and one-off narrative compositions remain locally scoped.

04 / Card resilience

Content cannot break it

With imageInterface ecology
No imageStrategy and governance

Supports a text-only evidence path.

Long titleCross-platform interaction architecture for adaptive mobility environments
中文适配本田跨平台智能座舱设计系统

Patterns & implementation

Components only matter in relationships.

Navigation, modal behavior and code mapping remain shared while visual tokens change by direction.

Navigation pattern

Persistent orientation

Brand left, current section centered, one next action right. At mobile widths the context label collapses before the action.

header → nav landmark → current page → primary destination

Modal pattern

Focus stays contained

Open from an explicit trigger, focus the title or first field, close on Escape, restore focus to the trigger, and block background scroll.

Dialog.Root + Overlay + Content + Close

Code mapping

Semantic tokens in code

.projectCard {
  padding: var(--space-6);
  color: var(--text-primary);
  background: var(--surface-raised);
  border-radius: var(--radius-panel);
}
320px viewportSingle column · no horizontal page overflow
200% textContent reflows · controls keep visible labels
Reduced motionStatic final frame · no transform or fade
KeyboardVisible focus · native disclosure behavior

Real content test

A project card has to carry evidence—not just look composed.

Honda HMI Design System interface overview
Published work

Professional project · 2024

Honda HMI Design System

A scalable HMI design system connecting brand language, interaction rules, reusable components, and adaptive delivery across mobile and in-vehicle products.

Design systemsHMICross-platform
Scope
Mobile + HMI
System
3 token layers
Library
20+ components
Read case study

Proposed direction · isolated from production

Use 1–5 or ← → to compare · R to replay