Images and illustrations play a critical role in communicating the Alius brand. They must feel authentic, technical, and grounded in the real-world practice of robotics and embodied intelligence — not detached, futuristic, or artificially polished.

Image Style

Alius images should depict the reality of robotics development — the craft, the iteration, and the hands-on nature of building intelligent machines:

  • Real laboratory environments and workbenches
  • Debugging and testing scenes with actual screens and tools
  • Workbenches with parts, tools, and components in progress
  • Individual parts: gears, joints, actuators, sensors, fasteners
  • 3D prints, prototypes, and iterative builds
  • Cables, connectors, wiring harnesses
  • Development boards, microcontrollers, and electronic components
  • Screens showing code, configuration interfaces, and terminal output
  • Hands assembling, calibrating, or adjusting hardware
  • Community events, workshops, and collaborative sessions

Visual Themes to Avoid

  • Excessive glow, lens flare, or light bloom effects
  • Neon colors and fluorescent highlights
  • Unrealistic humanoid robots with human-like expressions
  • Futuristic cityscapes, floating holograms, or sci-fi environments
  • Sterile, perfectly clean environments with no signs of actual work
  • Overly polished product renders that hide the engineering reality
  • Stock-photo-style images of people pointing at screens

Product Images

Hardware products should be documented with a consistent set of image types:

  • Front view: Standard product photograph, front-facing
  • Side view: Side profile showing depth and form factor
  • Back view: Rear panel with ports, connectors, and labels visible
  • Scenario / Context: Product in use — on a desk, mounted on a robot, in a lab setting
  • Dimension diagram: Technical drawing with labeled measurements
  • Exploded view: Disassembled view showing internal components and assembly order
  • Wearing / mounting diagram: How the product is attached, worn, or integrated
  • Port diagram: Close-up of ports, connectors, and pin assignments

Technical Images

Diagrams and technical illustrations support documentation and developer resources:

  • Architecture diagrams: System-level overview showing major modules and their relationships
  • Module relation diagrams: How software or hardware modules connect and communicate
  • Data flow diagrams: How data moves through the system from input to output
  • Control flow diagrams: Decision trees and process flows for software behavior
  • State machine diagrams: State transitions for system or component behavior
  • Hardware connection diagrams: Wiring and connection layout for physical assemblies
  • API call sequence diagrams: Request/response flows for API interactions
  • Training flow diagrams: Machine learning and training pipeline visualization

Naming Convention

Follow a consistent naming pattern for all image assets:

  • Use lowercase letters, numbers, and hyphens
  • Include the product or component name
  • Include the image type (front, side, exploded, diagram, etc.)
  • Include the variant if applicable (dark, light, annotated)
  • Example: alius-joint-servo-front.webp
  • Example: alius-joint-servo-exploded-annotated.webp
  • Example: system-architecture-v2.svg

Format Guidelines

  • Use WebP for photographs (with fallback to PNG or JPG)
  • Use SVG for diagrams, icons, and technical illustrations
  • Optimize all images for web delivery
  • Provide 2x resolution assets for high-DPI displays
  • Maintain consistent aspect ratios within image categories