DQ®

Portfolio system / Proposed direction

Review components

02 / Motion stage

Make complex systems feel alive, legible, and physical.

A dark motion-first stage where warm type, chromatic taxonomy, and choreographed response explain how components relate and change.

Explore system
01

Motion explains state

02

Color names disciplines

03

One continuous stage

Foundational elements / Proposed tokens

The decisions behind the surface.

Proposed motion-first system inferred from GSAP’s visual language; motion values are newly authored because the source document is incomplete.

01

Color palette

Semantic roles, usage and minimum contrast.

Stagecanvas.default
#202421Continuous backdrop
Cream 15.17:1 · AAA
Creamtext.primary
#FFFCE1Primary text
Stage 15.17:1 · AAA
Greenbrand.primary
#78E448Action + success
Stage 9.72:1 · AAA
Pinkstatus.attention
#D88BD2Category signal
Stage 6.40: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
DisplayInter65096–168px0.88−0.06em
H2Inter60052–76px0.95−0.045em
BodyInter40016–20px1.550
Code labelJetBrains Mono50011px1.4+0.10em
03

Spacing & layout

4px base scale with bounded responsive decisions.

0px 4px 8px 12px 16px 24px 32px 48px 64px 96px 128px
Grid
12 columns
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 rounded outline; inherit taxonomy color
Logo
Cream or mono; no glow
Images
High-contrast crop with stage-colored overlay
Illustration
One continuous gradient field; avoid unrelated 3D styles
Hover
150ms · cubic-bezier(.32,.72,0,1)
Press
scale .96 · 120ms
Enter
700ms · 32px → 0 · staged 100ms
Reduced
Static final frame; ambient loops 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
Radius12px panel / pill 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