Our UX Principles: 1. Make the most frequent tasks easy and less frequent tasks achievable. 2. Design for the 80% 3. Privilege the Content Creator 4. Make the default settings smart

Understanding the D7UX Information Architecture Approach

Posted: July 1st, 2009 | Author: Leisa Reichelt | Filed under: Concepts, Project Framework, Strategy | Tags: | 2 Comments »

This is the first in a series of posts discussing the proposed information architecture (IA) for D7UX.

Before we get into too much detail, be sure to check out this great video that Roy Scholten (Yoroy) posted recently that helps explain some of the key features and rationale of the IA and how it relates to the current Drupal information architecture.

2 Comments on “Understanding the D7UX Information Architecture Approach”

  1. 1 LeeHunter said at 1:16 pm on July 1st, 2009:

    Wow! Huge improvement. Brilliant. The only thing I think needs a little tweak is reversing the order of “People” and “Appearance”. To my mind, it makes more sense to go Content > Structure > *Appearance* > People > Config etc since the appearance is more closely related to the content and structure and user mgmt is more closely related to configuration.

    Nick Lewis Reply:
    July 28th, 2009 at 3:52 am

    Counter argument is that most people move left to right and people tweek users more than they tweek appearance.

    But — that’s an interesting question: do people find things easier when they grouped conceptually, or grouped by frequency of use.

    Best,
    Dr Smarty Farty Pants