Dashboard Best Practices

1. Keep match-critical data front and center
   Battery, drivetrain status, and any autonomous mode indicators should be visible without scrolling.

2. Use consistent tab naming
   Example: “Drive”, “Manipulator”, “Vision”, “Autonomous”.

3. Avoid overloading your network
   Limit high-frequency updates to essential telemetry.

4. Use color and formatting
   Red = warnings, Green = good state, Yellow = transitional states.

5. Version your layouts
   Store .json dashboard layouts in version control (/dashboards folder in your repo).

6. Include operator input visualization
   Add joystick values or button states to help debug driver control issues.