Who or what exactly is an Arduino?

Overview

What exactly is an Arduino? That was the first question I asked—and it took some effort to answer. A clear explanation is buried two levels deep from the homepage or tucked into the FAQ.

Users typically arrive on a site with two immediate questions: what is this, and how do I find what I need? The site does not answer either question quickly.

Key Issue

Core concepts are not surfaced early, weakening information scent and forcing users to rely on exploration rather than recognition. As a result, users must work to understand what each component or tool does, creating unnecessary friction.

Information Architecture Pattern

Large, contributor-driven platforms like Arduino often evolve into a network of semi-independent subsites. Over time, these subsites diverge from the main structure causing confusion.

Impact

As users move deeper into the site, global navigation frequently disappears, breaking orientation and continuity. The experience becomes fragmented, and users can easily lose their sense of place within the system.

Recommendations

1. Surface a clear “What is Arduino?” explanation on the homepage, paired with immediate pathways for common user goals (e.g., learn, buy, build).
2. Strengthen information scent by using plain, descriptive labels instead of brand or internal terminology.
3. Maintain persistent global navigation across subsites to preserve orientation and continuity.
4. Introduce lightweight wayfinding cues (such as breadcrumbs or section labels) to help users understand where they are within the system.
5. Consolidate or better integrate subsites to reduce fragmentation and create a more unified experience.