Arduino Site Map

PROJECT OVERVIEW

This presentation includes an as-is site map for arduino.cc created and analyzed by ChadCo. Studio. The mapping of this site can be used to reference the current information architecture and content used to navigate the site.

We have annotated the site map, noting how the site works, with a focus on the information architecture used throughout, and have included a summary of our analysis of the site that includes:

• • What is Working Well?
  • What Is Not Working Well?
  • What Needs to be Addressed?
  • What Needs to be Retained?

ANALYSIS & CRITIQUE

Homepage: The Homepage’s main navigation is a mix of direct links to other pages, or headers for dropdown menu items. Being that the heading links are not actionable, the discrepancy in consistency becomes confusing for users of the site. Several pages open a subdomain or subdirectory page, and may be presented as a new site, most notably the Store page. There is an opportunity here to address consistency between pages, layouts, and styling of IA, even if the use of subdomain or subdirectory is required. There are also links accessible from the main nav that open in new tabs. This takes the user out of their current thinking model, and drops them into another space (digitally and mentally). There is potential to keep the Arduino user within the Arduino mindset, even if there is a family of pages necessary for the overall experience. Overall the labels are short, and easy to understand without much site/product specific knowledge. Exceptions to this are the more technical or product specific labels, which may benefit from additional exploration of content. Another area the homepage excels in, is its adherance to more common website standards and expectations. Examples of this include: logo in upper-left-hand corner of the page, main navigation centered on the page, and search/store/login options in the upper-right-hand side of the page.

Store: The Store, as mentioned before, feels and acts like a separate child-site from the main homepage. It includes an additional sidebar navigation with several links to help users organize products. Some of these links might be better served as filters (which is how they function), and could help shorten and simplify some of the IA labels within the Store sidebar nav. Additionally, several of the labels appear to be links, but are unactionable as a parent category. Changing this to allow for a higher-level filtering of products, might remove an additional click from user’s hands, and get them closer to their desired product quicker. Again, similar to the main homepage, the Store does a good job of keeping individual labels concise and understandable.

Education: The one item to highlight on the Education page would be the opening of Arduino.CC in a new tab. For reasons aforementioned, it is recommended that this label link within the current tab. 

Pro: Likewise, the Pro page includes labels that are not actionable. While this follows an existing pattern from other IA implementations on sister pages, it is not recommended and should be addressed.

RECOMMENDATIONS

• • BE CONSISTENT – Whether considering the use of dropdowns, the individual labels, or the way a new page opens within the browser, remain as consistent as possible for the best user experience.
  • BE PRECISE – When looking at content and labels, use precise and well known terms by avoiding jargon and technical verbiage. This will go a long way in assisting users who are navigating the site.
  • BE THOUGHTFUL – Consider all users of the site to be novice users. Consider ways to guide them throughout the experience, and offer simple ways to return to previously visited pages.
  • BE CONCISE – Limit labels in the main and sidebar nav only to those that are absolutely necessary. Avoid redundancies on the nav and within individual pages when possible, and keep those labels short!
  • BE INCLUSIVE – Arduino should feel like an inclusive family of pages, rather than a body of loosely related sites. Work to ensure the flow and consistency is easily recognizable, while keeping individual characteristics of specific pages.

APPENDIX

Full Report (PDF)