Skip to main content

// Design to code

Status: Illustrative design artifact

From design intent to implementation.

Follow one reusable component across four projects: design source, state specifications, working React, and Storybook documentation.

Component
WorkflowCard · 7 states
Data
Fictional, across four projects
Independent portfolio demonstrations with fictional data. Separate from historical client work and résumé-reported career facts.

In the real enterprise engagement, DoD leadership formally established the delivered visual and interaction direction for other teams within the program. The examples below are current independent components. Read the professional account and its program scope.

INDEPENDENT DESIGN SYSTEM / TOKENS TO BEHAVIOR

One language. Many product states.

Explore the foundations, components, and interaction rules behind a coherent interface. These are current portfolio examples, separate from confidential enterprise assets.

01 / TYPOGRAPHY

Clarity
by design.

Display48–64 / purposeful emphasis

A clear next step.

Heading24–32 / a readable hierarchy

Keep the work, the context, and the next action together.

Body14–16 / useful, readable detail
02 / COLOR ROLES
Surface#f7f9f3
Content#273b34
Action#4d715b
Attention#a97435
Error#a44242

Color carries a defined role. Text and icons also name state; color alone never communicates the outcome.

03 / SPACING RHYTHM
4Detail
8
12
16Control
24
32Panel
48Section

A small, repeatable scale keeps density and hierarchy consistent across a complex product.

Review pattern example

Interaction state / shared React component

Choose a project and a state.

Use Tab to enter the state selector, then arrow keys to move. Home and End jump to the first and last states.

Behavior contract

  • Status: text and icon carry meaning alongside color.
  • Action: the parent owns the enabled action and persistence.
  • Recovery: explain the next step and preserve context.
  • Permission: label limits; enforce access on the server.

Rendered component / sample data

Orbit / service request

Equipment access review

REQ-2841 · Jordan Lee

In review

Record context, status, and the next action stay visible together.

The controls change this local example only. Try the enabled action to inspect its event feedback.

Responsive behavior

Context and status wrap at the available width. Long titles break, actions remain reachable, and no fixed desktop width is required.

Actual component API

<WorkflowCard
  project="orbit"
  state="default"
  onAction={handleAction}
/>

Usage + implementation guidelines

One record. Explicit behavior at every state.

When to use it

Use a status-and-action card when one record needs a clear owner, state, explanation, and next action. Reuse the same contract across request, report, case, and product contexts.

When to use another pattern

Use a table for comparing many records and a full detail view for complex decisions. Keep destructive confirmation, multi-step forms, and detailed audit history in their own patterns.

State ownership and service boundaries

The React parent passes a typed state and handles onAction. The card does not fetch, mutate, or infer permissions. Product services enforce access and supply authoritative status; loading prevents duplicate submission.

Responsive and accessible by default

Use semantic headings and a native button, communicate status with text and icon, provide visible keyboard focus, announce status updates, and honor reduced motion. Let content wrap instead of clipping labels.

Maintaining the system

Start with an existing variant. Add a new state only when its meaning or recovery behavior differs. Update the design kit, shared type, Storybook story, and acceptance guidance together; record the reason for the change.

Iterative, component-driven delivery

Review the workflow and state contract with product and engineering, implement a small increment, inspect it in Storybook with QA, and refine from feedback. Compose shared components; keep presentation separate from service logic.

project: WorkflowProject
Required. orbit | vector | nexus | commerce. Sets domain labels and recovery guidance.
state: WorkflowState
Required. default | warning | blocked | complete | read-only | loading | error.
title / recordId / owner: string
Optional content overrides. Test realistic long labels and localization before release.
onAction: () => void
Optional event callback for an enabled action. The product owns navigation, retries, and writes.

Acceptance checks: blocked / read-only / loading actions cannot fire; enabled actions emit one event; errors describe recovery; labels survive narrow widths; status has meaning without color; state selection works with keyboard and reduced motion.

Storybook / live component documentation

Inspect the implementation in isolation.

Open the component docs, change props with Controls, inspect all seven states, and review usage rules and accessibility findings. Stories import the same WorkflowCard rendered above. Each project also includes a long-label example and executable interaction checks.

These are newly created portfolio samples. No prior client use of Storybook or adoption result is claimed.

DESIGN SOURCE + WORKING COMPONENTS

Open the files behind the examples.

Open the native Figma companion to these cases: shared semantic variables, editable content properties, seven component states in wide and narrow layouts, and connected prototype flows. The source kits also include SVG exports, token references, and implementation specifications.

These are independent portfolio demonstrations with fictional data. Figma asks visitors to sign in to inspect component properties or present the prototype flows.

See the representative design-system case / Nexus