http://tc.eserver.org/authors/Garrett,_Jesse_James A bibliography of works by Garrett, Jesse James in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Garrett,_Jesse_James http://tc.eserver.org/25721.html http://tc.eserver.org/25721.html Every Web team has its own take on dividing up roles and responsibilities and implementing processes for design and development. Formal titles, job descriptions, and reporting structures can vary widely. But the best teams I’ve encountered have one important thing in common: their team structure and processes cover a full range of distinct competencies necessary for success. http://tc.eserver.org/25703.html http://tc.eserver.org/25703.html If anything about current interaction design can be called 'glamorous,' it’s creating Web applications. After all, when was the last time you heard someone rave about the interaction design of a product that wasn’t on the Web? (Okay, besides the iPod.) All the cool, innovative new projects are online. http://tc.eserver.org/25710.html http://tc.eserver.org/25710.html There's a lot about the Apple Store experience that we can apply to the design of many other kinds of products. http://tc.eserver.org/23215.html http://tc.eserver.org/23215.html Explores the psychology behind how users make navigational choices as they navigate through 'information spaces' and how information architects can use this information when crafting the navigational experience. http://tc.eserver.org/23101.html http://tc.eserver.org/23101.html 2001年のIAサミットを境にIAの理論と実践についてIAコミュニティでかつてない議論が起こりました。この6つの章からなるエッセイは、IAの今までとそしてこれからどこへ向かっていくべきなのか論争に終止符を打つべくJJGが書き上げた渾身のエッセイです。 http://tc.eserver.org/21759.html http://tc.eserver.org/21759.html Information architecture is as old as human communication. Where there's information, there's architecture. http://tc.eserver.org/21739.html http://tc.eserver.org/21739.html There is a discipline, known as information architecture; and there is a role, known as the information architect. They have developed more or less hand in hand, and up to now any discussion of one has involved discussion of the other. But now that may have to change. http://tc.eserver.org/21738.html http://tc.eserver.org/21738.html Diagrams are an essential tool for communicating information architecture and interaction design in Web development teams. This document discusses the considerations in development of such diagrams, outlines a basic symbology for diagramming information architecture and interaction design concepts, and provides guidelines for the use of these elements. http://tc.eserver.org/21737.html http://tc.eserver.org/21737.html Indicates the number of companies (out of 19 surveyed) that included specific requirements in their job descriptions for information architects. http://tc.eserver.org/21730.html http://tc.eserver.org/21730.html The Web was originally conceived as a hypertextual information space; but the development of increasingly sophisticated front- and back-end technologies has fostered its use as a remote software interface. http://tc.eserver.org/21728.html http://tc.eserver.org/21728.html A collection of online resources in information design and information architecture. http://tc.eserver.org/21284.html http://tc.eserver.org/21284.html From an information architecture perspective, a daily web publication presents challenges and possibilities no newspaper editor ever had to face. As one of the longest-running daily publications on the web, Slate has dealt with these issues for years. http://tc.eserver.org/21251.html http://tc.eserver.org/21251.html In many respects, email is the ideal web application: it's an application that people often need access to when they’re away from their 'home' environment, and the core user tasks (reading and writing) are easily accommodated with standard HTML interface elements. http://tc.eserver.org/18940.html http://tc.eserver.org/18940.html Consider the humble URL. In a few short years it's become so ubiquitous as to be rendered invisible. It's hard to imagine a world without it, and it's hard to remember that there was once a time when not having a uniform means of locating resources was considered a fundamental stumbling block to the deployment of any large-scale hypertext system — never mind a world-wide one. But despite the universality of URLs, we often forget that they're not just a handy way to address network resources. They're also valuable communication tools. They help orient users in your architecture, and can suggest whether other options are available.