Communicating Design: Developing Web Site Documentation for Design and Planning
| Author | : | |
| Rating | : | 4.29 (722 Votes) |
| Asin | : | 0321392353 |
| Format Type | : | paperback |
| Number of Pages | : | 368 Pages |
| Publish Date | : | 2013-06-02 |
| Language | : | English |
DESCRIPTION:
Dan writes and speaks frequently on information architecture, and contributed to the inaugural issue of UX Matters, a new online magazine dedicated to user experience design. Through his consulting work in both public and private sectors, he has improved enterprise communications for both Federal and Fortune 500 clients,
Through his consulting work in both public and private sectors, he has improved enterprise communications for both Federal and Fortune 500 clients, currently the Federal Communications Commission. About the AuthorDan Brown has been practicing information architecture and user experience design since 1994. Dan writes and speaks frequently on information architecture, and contributed to the inaugural issue of UX Matters, a new online magazine dedicated to user experience design. . Dan is very active in the local Washington, DC information architecture community, and serves on the advisory board for the Information Architecture Institute
Combining quick tips for improving deliverables with in-depth discussions of presentation and risk mitigation techniques, author Dan Brown shows you how to make the documentation you're required to provide into the most efficient communications tool possible. Here at last is a guide devoted to just that topic. Most discussion about Web design seems to focus on the creative process, yet turning concept into reality requires a strong set of deliverables—the documentation (concept model, site maps, usability reports, and more) that serves as the pr
S. Harrison said Buyer beware - companion website does not have promised resources. Part of the value of this book is the promise that the author will provide templates and examples. This promise is worth zero. If you go to the companion website, there is a note from the author that says, essentially, "Ooops, so sorry. Got too busy." Just a tad unprofessional? I guess different people have different perspectives on such things.Call me crazy, but one would think that the author would have had a whole stack of examples and templates BEFORE he wrote the book. How else would he know what documents are needed? Just a rhetorical questionThe book itself is useful, don't ge. Weston Thompson said Good handbook for documentation. I found this to be a good handbook for the type of documentation I often create on projects. I think I wanted more focus on the information design aspect of diagrams / tables, etc. - sort of Dan's take on Tufte. This is more of a comprehensive review of what content a particular document could or should include, how to inflect the doc to different audiences/purposes, and when (or if) to use it in a project. That is important stuff, and Dan does a good job of it. Dan also provides some nice commentary on the future of documentation.. "Wheres the templates and reference material?" according to V. Matyi. EXCELLENT, EXCELLENT book for reference. Actually the best you can find of the type. No filler and I enjoy the authors style.Only four stars because book offers no companion templates for reference. How could a book focusing on documentation offer no documents/templates for reference in this day and age? Lucky for Dan his writing and explanations are THAT good. Though, shame on both the author and publisher for not going the extra step here.