Orbit / service request
Equipment access review
REQ-2841 · Jordan Lee
Record context, status, and the next action stay visible together.
Follow one reusable component across four projects: design source, state specifications, working React, and Storybook documentation.
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
Explore the foundations, components, and interaction rules behind a coherent interface. These are current portfolio examples, separate from confidential enterprise assets.
Clarity
by design.
A clear next step.
Keep the work, the context, and the next action together.
#f7f9f3#273b34#4d715b#a97435#a44242Color carries a defined role. Text and icons also name state; color alone never communicates the outcome.
A small, repeatable scale keeps density and hierarchy consistent across a complex product.
Interaction state / shared React component
Use Tab to enter the state selector, then arrow keys to move. Home and End jump to the first and last states.
Behavior contract
Rendered component / sample data
Orbit / service request
REQ-2841 · Jordan Lee
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.
Context and status wrap at the available width. Long titles break, actions remain reachable, and no fixed desktop width is required.
<WorkflowCard
project="orbit"
state="default"
onAction={handleAction}
/>Usage + implementation guidelines
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.
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.
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.
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.
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.
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.
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
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 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.
Independent example / RequestCard
Request review, missing evidence, recovery, and approval.
Independent example / ReadinessCard
Reporting freshness, review signals, and accessible data status.
Independent example / CaseCard
Case review, permission limits, and role-aware actions.
Independent example / SelectionCard
Product selection, missing options, cart feedback, and recovery.