Typography
Noto Sans, with responsive roles for application headings, labels and values.
- Value size
- Label weight
A scalable visual foundation for railway fleet, device, software, and configuration management applications. Shared foundations, reviewed components and guidance for consistent interfaces.
Our logo guidelines establish consistency and high contrast legibility for railway-related equipment.
A purposeful palette designed to satisfy critical field legibility and semantic state categorization.
Used for the most prominent components across the UI, such as high-emphasis buttons, FABs, and active navigation states.
Used for less prominent components in the UI, such as filter chips, secondary buttons, and borders.
Used to communicate error states and critical system alerts, f.ex. an incorrect password input or system malfunction.
Used for describing a positive result, successful operations, online indicators, and completion states.
Used for communicating risky operations or states that require user awareness before proceeding.
Used to indicate a need for caution or standby attention without immediate system danger.
Vibrant design tokens for custom visualization highlights and status categorization.
Ranging from index 0 (black) to 100 (white) for each core hue. Click any cell to copy its CSS token variable.
Complete specification for all status states across SignalView — icons, tokens, light & dark backgrounds, and definitions. Source of truth for developers building status-aware components.
Can I communicate with this asset?
--kb-status-online-*--color-s-40--kb-status-nonreporting-*What has the operator done with this alert?
inherits--color-p-40--kb-status-suppressed-*--kb-status-resolved-*How severe is the anomaly or threshold violation?
--kb-status-info-*--kb-status-warning-*--kb-status-critical-*Used in StatusRow components and device avatars. The glow isolates urgency color to the ring — not the entire row — for a clean dark-mode aesthetic.
SignalView uses Lucide React as its standardized icon library. All icons follow a consistent 2px stroke, semantic color inheritance, and must always pair with accessible labels when used in navigation.
currentColor. Never hardcode icon color separately from its context text color.
aria-label.
Review the V1 wizard typography baseline →
Noto Sans is our primary typeface. Fallback: Arial. It ensures optimal legibility on low-resolution field screens.
Subtle transparency, blur, and depth for modern enterprise dashboard experiences.
Used for standard content containers and read-only informational cards.
--glass-bg
Used for content context that requires hover lifts, focus highlights, or floating states.
--glass-bg-elevated
Used to indicate active selection, target device highlighted states, or configuration focus.
--glass-bg-selected
Used for warning indicators, critical errors, or emergency status panel views.
--glass-bg-alert
Consistent structural tokens that establish container scale harmony, feedback cues, and elevation hierarchy.
KB V1 · Shared standard
Typography, color and structure in one place. Values below come from the active shared theme.
Noto Sans, with responsive roles for application headings, labels and values.
Theme-aware surfaces and text. Company colors support actions and accents.
Use the role for the component. Static cards stay flat; primary elevation is optional.
Lucide with consistent size roles, currentColor and stroke 2. Button icons are optional.
Text-only and named icon-only actions are both supported.
Icon roles and naming →KB V1 · Shared standard
Working examples from the shared implementation. Choose a family to inspect its states and usage.
KB V1 · Shared standard
Input, select and textarea behavior is demonstrated in the live example; inspect additional states here.
Example only: enter a valid hostname.
Hover keeps the resting contour. Focus, readonly and invalid states preserve native behavior.
All field states · Field markup and rulesKB V1 · Shared standard
Real components. One shared source. This local example does not save or send data.
Try the fields and actions. Use the page theme control to compare light and dark.
Start from shared styles and working examples.
Use consistent controls across devices and teams.
Keep guidance, tokens and implementation connected.
KB V1 · Shared standard
Clear action hierarchy, optional icons and explicit selection states.
Text-only by default here. Icons and primary elevation depend on the use case. Badges are passive; chips are selectable.
Local demonstrations only.
KB V1 · Shared standard
Flat information surfaces and two explicit modal families, with named controls and keyboard behavior.
Static cards group information without automatic hover lift.
Nested surfaces have their own fill, border and spacing.
KB V1 · Shared standard
Extended examples are retained for exploration. They are separate from the verified V1 component library.
Browse status examples, application patterns and the earlier gallery below. Their presence does not establish a validated organization-wide policy.
Earlier examples retained for reference. Use the current V1 component library above for accepted styling and behavior.
Click below to open live functional overlays built in Noto Sans typography with responsive overlays.
Overview panel content. System reports normal relay tolerance at 99.8%. No anomalies detected.
Details panel content. Serial: GW-1001-A4. Hardware Rev: v1.4.2. Location Coordinates: Lat 45.4215, Long -75.6972.
Activity panel content. Last sync timestamp: 2026-06-09 12:06:40. Configuration updated by administrator.
| Device Name | Status | Version |
|---|---|---|
| GATEWAY-1001 | Online | v2.4.1 |
| GATEWAY-1002 | In Progress | v2.4.1 |
| GATEWAY-1003 | Offline | v2.3.8 |
Common visual layout patterns constructed for device monitoring and configuration panels.
Flexible page templates adapt seamlessly to support all deployment screens. Toggle the viewport simulator below to preview real-time responsive reflows and color changes of the design system.
KB V1 · Shared standard
Reusable styles and guidance. Application adoption happens deliberately, one screen at a time.
Load the theme and the component layers you need. Fonts are optional local assets.
<link rel="stylesheet" href="theme.css">
<link rel="stylesheet" href="fields.css">
<link rel="stylesheet" href="actions.css">
<link rel="stylesheet" href="surfaces.css">
Working CSS consumer →
Keep the standard inside your application scope.
@use './scss' as kb;
@include kb.theme(
$selector: '.application',
$dark-selector: '.application.dark'
);
.application {
@include kb.fields();
@include kb.actions();
@include kb.surfaces();
}
Working Sass consumer →
The adoption skill connects verified rules, source conflicts and checks. Use it with people or coding assistants.
Open the team skill →Choose a bounded pilot, preserve its functionality and review both themes. Measure adoption effort before making organization-wide productivity claims.