- Paperback: 360 pages
- Publisher: New Riders; 1 edition (July 4, 2009)
- Language: English
- ISBN-10: 0321601351
- ISBN-13: 978-0321601353
- Product Dimensions: 7.3 x 0.8 x 9.1 inches
- Shipping Weight: 1.4 pounds
- Average Customer Review: 5 customer reviews
- Amazon Best Sellers Rank: #1,497,751 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Modular Web Design: Creating Reusable Components for User Experience Design and Documentation 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Customers who viewed this item also viewed
Customers who bought this item also bought
From the Back Cover
User experience design teams often suffer from a decentralized, blank canvas approach to creating and documenting a design solution for each new project. As teams repeatedly reinvent screen designs, inconsistency results, and IT teams scramble to pick up the pieces. Pattern libraries only go so far, suggesting general solutions to common problems instead of offering concrete, specific design treatments. At times, documented solutions turn into a costly mess of unclear expectations, unrealistic goals, and abandoned work.
Enter components, each of which represents a chunk of a Web page. Designers can produce wireframes, mockups, or markup far more efficiently reusing components based on an established design system. Rather than limit innovation, components enable designers to render solved design frameworks quickly and to focus on the problem at hand, drastically improving the quality and rate of production. In addition, teams develop a deeper baseline for collaboration, a platform for governance, and a structure for useful and predictable documentation.
This book defines the role of components and why they matter, maps out how to organize and build a component library, discusses how to use components in practice, and teaches a process for documenting and maintaining components.
About the Author
Nathan Curtis is a founder and principal at EightShapes, LLC, a user experience consulting firm based in Washington, DC. Nathan has been a user experience design practitioner since 1996 in areas including information architecture, interaction design, usability, and user interface development. Prior to founding EightShapes, Nathan practiced user experience design during stints at Sprint Nextel, BIG fish Design, and SAS Institute, Inc. Nathan obtained a B.S. summa cum laude in mathematics and statistics from Virginia Tech, followed by a master’s degree in statistics from the University of Chicago. He blogs at www.nathancurtis.com and currently lives in Fairfax, VA, with his wife and two children.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
What I liked about the book:
- It's down to earth, very well structured.
- The fundamental approach is very inspiring: how to cut a design into pieces, document the pieces, search for reusable elements and define those as components.
- Examples and figures are abundant and illustrate the points very well.
What you should be aware of:
- If you're mainly working for on small to mid-sized projects or you're not really decided to go and start creating and sharing component libraries, the detailed process in the 2nd part of the book may be really overkill for you.
The book has very helpful visuals and goes into depth. If you were ever creating or maintaining a library, this would be an awesome bible and I am sure it would ensure that you didn't miss a step. On the other hand, this is useful for many other situations. For example, our website is going through a massive redesign, and I have found it incredibly useful for doing content inventories of the old site and for thinking of both the old and new sites in terms of modules.
The book is very detailed, which makes it long, especially for people who are not creating libraries. However, it's still a great read and should be read by designers, developers, and anyone else involved with website components.
Looking for some tips that will take your design deliverables to the next level?
Have customers ever looked at your deliverables and said, "Huh? Where are you referring?"
Then Modular Web Design is worth buying and reading.
I confess that I can be a bit lazy. I'm also extremely swamped. I want to make engaging, easily understood deliverables as quickly as possible and this book has helped me review my current body of work and enhance it. It's given me some new ways to think about how I create great deliverables and leverage existing work.
I may have gotten something out of it if it were half the length, much more focused, and a little more detailed. Throw in some case studies of actual cause-effect examples, and it would have grabbed my attention.