3rd
January
2001
“Until recently, few people had heard of information architecture, which I define as the process of structuring and organizing information so that it’s easier for users to find and for owners to maintain. But go to any major job site today, and you’ll see many job openings for information architects. It’s not surprising: After five years of authoring and coding, many of us are stuck with Web sites and intranets that are huge, messy, unusable and impossible to maintain. With such a great demand for help, there are many inexperienced information architects repeatedly making the same mistakes. In the hope of fast-forwarding global information architecture literacy, here are some of the most common and avoidable errors I have learned from.”
posted in Information architecture | Permalink |
3rd
January
2001
“Visa International unveiled on Wednesday an animated logo, with audio, that was designed by New York-based i-shop Agency.com to signal when a Visa product is being used for payment on a PC, mobile phone or handheld device.” Here it is. And I don’t even want to know how much that cost.
posted in Logos/Symbols | Permalink |
3rd
January
2001
“Visa International unveiled on Wednesday an animated logo, with audio, that was designed by New York-based i-shop Agency.com to signal when a Visa product is being used for payment on a PC, mobile phone or handheld device.” Here it is. Yuck. And I don’t even want to know how much that cost.
posted in Sound design | Permalink |
3rd
January
2001
Includes three articles by Dick Berry, User Experience Design, IBM Ease of Use team. The first is The iceberg analogy of usability. The second is It’s a matter of style — GUI versus the Web. And Part 3 is Using controls in forms.
posted in Usability | Permalink |
3rd
January
2001
“When I envision an XML development team, I picture several people with different skill sets. For example, an information architect, or what we may once have called a ‘knowledge engineer,’ possesses the background and aptitude for designing and implementing document structure. That’s the DTD or schema developer. Distinctly different is the software engineer who uses APIs like SAX or the Document Object Model (DOM) to access and process documents programmatically. And then there’s a transformation specialist. This is, in my mind, someone who uses the XSL Transformation language (XSLT) to convert, translate, and transform XML into other formats, often for the purpose of data exchange with other systems. The problem arises because this last person, or more importantly his or her skill set, isn’t very well understood. Most managers push these responsibilities onto their user-interface designers. After all, these are style sheets, right?”
posted in XML/XSLT | Permalink |
