Changes between Version 14 and Version 15 of SimplifyingBeWelcome


Ignore:
Timestamp:
Apr 20, 2008, 5:42:41 PM (11 years ago)
Author:
lemon-head
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SimplifyingBeWelcome

    v14 v15  
    8080a) navigation sidebar (our sidebar does not count, because it appears as
    8181part of the content, and not as something outside meant for navigation).
     82
    8283Examples: gmail, studivz, a big number of major sites.
     84
    8385Issues:
    84 - Consumes horizontal space: Sidebars reduce the page width we can use for
     86 - Consumes horizontal space: Sidebars reduce the page width we can use for
    8587content. This is ok for pages with one column of text, because smaller
    8688columns are easier to read anyway. But any time we want to use more than
    8789one column for the content, or we want to show big things such as a map,
    8890we want all the horizontal space we get.
    89 + has more space for text, links and even images, than a horizontal menu
     91 - (+) has more space for text, links and even images, than a horizontal menu
    9092has.
    91 + can be nicely separated into several sections (like the "widgets" in
     93 - (+) can be nicely separated into several sections (like the "widgets" in
    9294wordpress sidebar)
    9395
    9496b) tabs and horizontal menus (as we have it already).
     97
    9598Issues:
    96 - Consume vertical space, so it easily happens that you have to scroll for
     99 - Consume vertical space, so it easily happens that you have to scroll for
    97100the desired content.
    98 - Space in one row of tabs is limited, and more than 2 levels of tabs will
     101 - Space in one row of tabs is limited, and more than 2 levels of tabs will
    99102usually look strange.
    100 + The strict tree hierarchy implied by a tab-based navigation is great for
     103 - (+) The strict tree hierarchy implied by a tab-based navigation is great for
    101104memorizing the navigation structure, even when it does not always fit with
    102105the actual structure of our site (or does it?).
     
    104107c) CSS / Javascript dropdown menus (a combination of css and js can make
    105108them more accessible for older browsers). Issues:
    106 - items in the dropdown are not visible in the first place
    107 - problems in IE6 with js switched off.
    108 - easily pops out unintended, then it hides other page elements. Special
     109 - items in the dropdown are not visible in the first place
     110 - problems in IE6 with js switched off.
     111 - easily pops out unintended, then it hides other page elements. Special
    109112attention in the design!
    110 - Often a dropdown does not look like anything will pop up. Consider
     113 - Often a dropdown does not look like anything will pop up. Consider
    111114visual affordances in the design!
    112 + efficient use of display space.
     115 - (+) efficient use of display space.
    113116
    114117d) increase the number of navigation steps from A to B, making it possible
     
    117120hub"), when they want from page A to page B. (I am generally not in favour
    118121of this solution).
     122
    119123Issues:
    120 - slower navigation.
     124 - slower navigation.
    121125
    122126e) have different navigation links on each page. For instance, we could
     
    124128menus for group or profile pages, with links to "navigation hubs", or with
    125129drop menus to save space.
     130
    126131Issues:
    127 - Not consistent on different types of pages. We have to do the design
     132 - Not consistent on different types of pages. We have to do the design
    128133with care, so people still recognize a link as the same, if one time it is
    129134in a sidebar, and another time int a horizontal menu.