![]() The mobile testing highlighted users' ability to navigate the admin interface but revealed a few concerns about font size, spacing, and user expectations about the "expand sidebar" feature. These in-person tests allowed us to observe how users interacted with the menu on their mobile devices, something that can't be done on a video call. Participants had varying levels of experience using Drupal Core's admin interface. ![]() User testing: round 3ĭuring DrupalCon Lille's Contribution Day, we conducted seven pop-up tests to evaluate the mobile implementation of the new toolbar. This round of testing taught us that we'll have to work on the change management and communication strategy to help align more experienced users. They completed tasks arranged for them in the testing environment and generally agreed that the new layout could help with onboarding less experienced users. However, they were able to orient themselves quickly. This group of testers wasn't as enthusiastic about the big change because it meant modifying their current setup. Our initial prototype was well received, and the menu groups made sense to users.įor round two, David Rosen, a User Experience Analyst from the University of Minnesota, organized a group of experienced Drupal site builders and content editors accustomed to the current toolbar implementation. User testing: round 2Īhead of our second round of testing, we felt optimistic. The original idea to add these groupings came from discussions years ago and then crystallized into this proposal. As a result, we introduced separate task groups tailored for editors and site builders, enhancing the overall user experience for these specific audiences. They got us thinking about the words (Drupalisms) we use and how we might use plain(er) language to reduce onboarding time for less experienced users. All participants preferred the new navigation over the old, though they also provided valuable insights for iteration. Our first round of testers provided overall positive feedback for the new collapsable, vertical layout. User testing: round 1Īn HTML mockup served as the testing ground to gauge user satisfaction. We plan to "rinse and repeat" this process until there is a contributed module ready for Drupal Core. ![]() We used a combination of card sorting, surveys, and moderated usability tests to collect feedback, which was used to iterate on the toolbar over several months. As the saying goes, thirty hours of development time can save you three hours of planning, and we'd rather that be flipped around. Multiple rounds of user testing helped ensure we were going in the right direction. Our goals were to get fast, iterative feedback before jumping into development. We approached this design work by testing, iterating, and testing again. At a high level, this suggested a left/top/top layout as being the easiest to scale and scan. ![]() We also gathered insights from the admin theme Gin, which helped us validate several hypotheses. We based our initial designs and prototypes on the research of competitors, industry standards, and previous UX studies on the topic. Our overarching goal is to improve the usability, accessibility, and design of the navigation system to provide a better user experience for site builders and content editors. Since our last update, we've been focused on a redesign of Drupal's main navigation, or "the toolbar." It's one of the most visually impactful changes to the Drupal Admin UI, and when it's completed, it will complement other efforts like the Dashboard and Field UX initiatives. Second, its redesign will support other active initiatives to improve Drupal's Admin UI. First, it's one of the most visually impactful areas of the Admin UI. We decided on this direction for two reasons. For Lullabot's first sponsored contribution, we've been focused on improving Drupal's main navigation.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |