Icons provide visual shorthand for actions, categories, and states across the Alius platform. They must be consistent, recognizable, and functional — never decorative.

Icon Style

The Alius icon system follows these style rules:

  • Linear style — all icons use outline/line art, not filled or duotone variants by default
  • Geometric simplicity — shapes are constructed from basic geometric forms (circles, rectangles, triangles, lines)
  • Unified stroke width — all icons use the same stroke width within a set; no mixing thin and thick strokes
  • Unified border radius — corners follow the same radius rules as the design system (XS to S range)
  • Avoid over-realism — icons are abstracted representations, not miniature illustrations
  • Avoid complex AI symbols — no brains, neural networks, glowing circuits, or stereotypical “AI” imagery

Icon Categories

Icons for moving through the interface:

  • Home, back, forward, menu, sidebar toggle, breadcrumb
  • Expand, collapse, search, filter, sort

Functional Icons

Icons for common actions:

  • Add, remove, edit, delete, copy, download, upload
  • Save, refresh, sync, share, link, external link
  • Settings, configure, toggle, lock, unlock

Status Icons

Icons for system and operation states:

  • Success, error, warning, info, loading
  • Online, offline, pending, processing, complete
  • Enabled, disabled, deprecated, new

Hardware Icons

Icons for physical products and components:

  • Robot, joint, servo, motor
  • Sensor, camera, display, battery
  • Cable, connector, mounting bracket
  • Development board, 3D printer, workbench

Software Icons

Icons for digital products and tools:

  • Terminal, CLI, code editor, configuration
  • Agent, model, algorithm, pipeline
  • Dashboard, log, monitor, debug

Community Icons

Icons for community and collaboration features:

  • User, team, organization, contributor
  • Forum, discussion, comment, reaction
  • Repository, pull request, issue, release

File Type Icons

Icons for distinguishing file formats:

  • Document, markdown, PDF
  • Image, video, audio
  • Code file, configuration file, data file
  • Archive, package, firmware

Usage Guidelines

  • Use icons to support text labels, not replace them — especially for navigation and critical actions
  • Maintain consistent sizing within the same context (e.g., all navigation icons are the same size)
  • Provide accessible text alternatives (alt text, aria-labels) for all icons
  • Use the same icon for the same concept everywhere — do not use different icons for “download” in different locations
  • Icons should be optically balanced, not pixel-perfect — a circle and square of the same pixel dimensions should appear visually equal