Information Architecture 2.0
From a new Web Magazine - UXmatters
"The typical information architect thinks about structure—how one item in a group relates to all the other items in the group and how that group relates to all other groups. In the early days of information architecture (IA), groups and their related items tended to be well defined. For example, in the heyday of e-commerce, an information architect translated a product catalog into a storefront on the Web. Today, these problems seem old hat.
Modern Web technologies permit greater flexibility in navigation, search, retrieval, and display. At the same time, the quantity of information is growing exponentially, and users expect greater control over content. Today’s Web offers
- more sophisticated interactions between browser and server—through the XMLHttpRequest object
- more dynamic interfaces—through JavaScript and CSS
- more flexible formats for distributing content—through XML and RSS" continued ... (Via UXmatters)
"The typical information architect thinks about structure—how one item in a group relates to all the other items in the group and how that group relates to all other groups. In the early days of information architecture (IA), groups and their related items tended to be well defined. For example, in the heyday of e-commerce, an information architect translated a product catalog into a storefront on the Web. Today, these problems seem old hat.
Modern Web technologies permit greater flexibility in navigation, search, retrieval, and display. At the same time, the quantity of information is growing exponentially, and users expect greater control over content. Today’s Web offers
- more sophisticated interactions between browser and server—through the XMLHttpRequest object
- more dynamic interfaces—through JavaScript and CSS
- more flexible formats for distributing content—through XML and RSS" continued ... (Via UXmatters)
UXmatters
0 Comments:
Post a Comment
<< Home