- ペーパーバック: 336ページ
- 出版社: New Riders Press; 1版 (2008/12/4)
- 言語: 英語
- ISBN-10: 0321553845
- ISBN-13: 978-0321553843
- 発売日： 2008/12/4
- 商品パッケージの寸法: 19 x 1.4 x 23 cm
- おすすめ度： この商品の最初のレビューを書き込んでください。
- Amazon 売れ筋ランキング: 洋書 - 1,413,000位 (洋書の売れ筋ランキングを見る)
Flexible Web Design: Creating Liquid and Elastic Layouts with CSS (英語) ペーパーバック – 2008/12/4
Kindle 端末は必要ありません。無料 Kindle アプリのいずれかをダウンロードすると、スマートフォン、タブレットPCで Kindle 本をお読みいただけます。
Liquid or fluid layouts change width based on the user's unique device viewing size. These types of layouts have always been possible with tables but offer new design challenges as well as opportunities when built with CSS. This book, for experienced Web designers with some CSS experience, outlines how to do this successfully.
Designers will learn the benefits of flexible layouts and when to choose a liquid, elastic, or hybrid design. They will learn not only how to build a liquid layout from scratch using standards-compliant and cross-browser compatible (X)HTML and CSS, but will also learn how to design and slice their graphic comps in a way that makes flexible design achievable. This book will show designers that flexible layouts do not have to be visually boring or difficult to build when planned and built correctly. Even those who do not intend to build liquid layouts can use the concepts and techniques taught in this book to improve their fixed-width CSS designs, because they will learn how to design for the inherent flexibility of the web medium, instead of the rigid qualities of print media or table grid-based layouts.
"Another excellent resource comes to us courtesy of Zoe Mickley Gillenwater <http://zomigi.com/> . She’s written a book called Flexible Web Designs <http://flexiblewebbook.com/> . Buy it now. You won’t regret it. I thought I knew my stuff when it came to wrangling CSS but this book had techniques that were new to me. ..." -- Jeremy Keith
"If you want to know more about creating liquid and elastic layouts, you should read Flexible Web Design by Zoe Mickley Gillenwater. I heard about the book on Twitter (via Malarkey) and I bought it almost straight away. I started reading it recently and my first impressions are that this is the best book I have bought in some time. The book describes flexible layout types in some detail and explains how to achieve these with CSS. It really is a worthwhile read if you are new to flexible layouts…. or even if you are a regular ‘flexible web designer’." -- Clive Walker
"The biggest two flaws that this book has is that it wasn't published many years ago and not all web designers have a copy of it. There isn't much that can be done about the first of these and the situation regarding the second will resolve itself gradually as more web designers find out about the book and buy a copy. This book goes into great detail on a number of important techniques for styling web pages with CSS that will be useful to anyone creating web pages. The step by step approach not only shows you how to solve the specific layouts that the book covers but also show very clearly the approach to take to resolve the layout of any web page with CSS." -- Stephen Chapman
Amazon.com で最も参考になったカスタマーレビュー (beta)
This is my third book by Head First (I also have the HTML and AJAX books), so I already knew that I liked the Head First writing style - perhaps a little light on technical side, but the lessons get driven home. The reader simply retains material from these books, and that is tough to find in most technical books on the market.
Again, the only thing to watch out for is the sloppy editing; there were a few too many editing errors for my taste. I still gave the book five stars, though, because it was just that good.
In other words, the goal of the book is to optimize forms for novices, not necessarily for proficient users. In itself, this goal is laudable, however, it ought to have been made explicit. As things stand, it is uncertain if all or which parts of the advice applies to forms whose users interact with them regularly and know them well.
By the standard of this book, complex forms are a mistake. And this may well be true for public facing sites. The situation is different for in-house applications that incidentally have a browser-based user interface. On these, unfortunately, the book remains silent.
I'd like to have seen a discussion of interactive controls beyond the native HTML text fields, drop downs, check and radio boxes. I'd like to have read how to make the best of fluid or elastic page layouts, as it is, all examples assume fixed-width layouts. A chapter on the construction of forms using semantic HTML and CSS wouldn't have been out of place either.
What's missing most of all is an extended case study that goes through all the stages of designing a realistically complex form.
After all this criticism, I'd like to point out that what is there in the book is very solid. As things stand, though, there remains much to be said.
in the Head First series. It is also unique in teaching the entire life cycle of building a usable, information-rich, beautiful, navigable, and accessible web site, and not being confined to illustrating the graphical layout of beautiful web pages. It illustrates, the sketching, information design, navigation, and customer interaction issues involved in developing a sophisticated, content-filled web site and prepares the developer to perform a well-managed design and implementation process. The guide does assume that the prospective web designer have familiarity with HTML, XHTML, and CSS, but that is an entirely reasonable assumption for any web designer and is well served by the HTML/XHTML volume in the Head First Series. This is an excellent and most necessary book for the design of sophisticated information architectures, and usable beautiful web sites that serve both the user and the organization that commissioned them.
And so Luke Wroblewski begins his new book on web form design with a canon shot across the bow, providing just the air cover and ammunition interaction designers need; and every review, including this one, is going to begin with a first impression of the book.
Mine was: Boffo.
(bof·fo (bf) Slang, adj.: Extremely successful; great.)
Wroblewski opens "Web Form Design" with an exploration, from a strategic perspective, of why users interact with forms. News flash: It's not because we like to. It may seem obvious, but the truth is, interaction designers need to confront the truth that a user's goal is to get to some successful outcome on the other side of a form - as quickly and painlessly as possible. We want our iPhone, tax return, or account with Facebook. We don't want to fill out forms.
"Forms suck. If you don't believe me, try to find people who like filling them in. You may turn up an accountant who gets a rush when wrapping up a client's tax return or perhaps a desk clerk who loves to tidy up office payroll. But for most of us, forms
are just an annoyance. What we want to do is to vote, apply for a job, buy a book online, join a group, or get a rebate back from a recent purchase. Forms just stand in our way."
Wroblewski has researched, with admirable thoroughness, everything from the basics of good form design, to labels and most-direct route, delivering his explanations, patterns and recommendations with a casual urgency that never veers into preachiness. This book is a useful guide for both the novice interaction designer and the battle tested UX guru, offering salient, field tested examples of the good, bad, and often times ugly forms that have proliferated the web like so many mushrooms after a good rain.
Wroblewski has also invited many seasoned professionals to contribute sidebars, like Caroline Jarrett's no-nonsense perspective on designing great forms by advising us to "start thinking about people and relationships," instead of just diving into labeling our forms and choosing where to put the Submit button. I especially appreciated her strategic guidelines for picking what questions should go into a form in the first place, which she aptly titles "Keep, Cut, Postpone, or Explain."
Wroblewski is aware of how challenging most readers will find good form design. It comes as a relief, for instance, when he writes that we should think less about forms as a means of filling a database, and more as a means of creating a meaningful conversation between the user and the company. He generally succeeds at adopting the warm tone of a confiding friend and colleague who can win you over with self-deprecating, you-too-can-make-dynamic-forms-every-day enthusiasm. The more subtle points of user-centered design or goal-driven design are not talked about explicitly; they are like a whisper on the wind that you can barely hear unless you train your ears.
What's In the Book?
"Web Form Design" is part of a wave of User Experience books sweeping over us from Rosenfeld Media; books focused on bringing practical, actionable and well researched methods to actual practitioners in the field. This literature is going to have a powerful effect on our community of practice, maybe as powerful as the effect the Polar Bear book had on our grandparents' era. This volume is broken out into three sections:
Section one, "Form Structure" begins with an overview of why form design matters and describes the principles behind good form design, followed by Form Organization, Path to Completion, and Labels (hint: your form design should start from goals). Working quickly through strategy to tactics. Wroblewski gives numerous examples - within the context of usability studies -so that you are not left wondering whether these patterns are recommended based just on his opinion.
Section two, "Form Elements," is a useful, clearly written exploration of each of the components of form design: labels, fields, actions and messages (help, errors, success). Wroblewski attacks each one of these by defining particular problem spaces, and then shows good and bad solutions to the problems while highlighting how these solutions faired in controlled usability tests, including eye-tracking. He then finishes each chapter off with a succinct list of `Best Practices' that I suggest are good enough to staple to the inside of your eyelids.
Section three, "Form Interaction," with chapters on everything from Inline Validation to Selection-dependent Inputs (a barn burner of a chapter). Here we have moved from the world of designing labels, alignment, and content to designing the actual complex interactions between the system -that wants to be fed like the plant in Little Shop of Horrors - and the world-weary user that just wants to get to the other side of the rainbow. As Wroblewski explains in his opening of chapter 9 "Inline Validation,"
"Despite our best efforts to format questions clearly and provide meaningful affordances for our inputs, some of our questions will always have more than one possible answer...
...Inline validation can provide several types of feedback: confirmation that an appropriate answer was given, suggestions for valid answers, and real-time updates designed to help people stay within necessary limits. These bits of feedback usually happen when people begin, continue, or stop entering answers within input fields. "
The chapter tells how to establish communication between the user and the form, providing clear, easy to read feedback so that the user doesn't get the "select a username or die" travesty that we see in registration forms all over the web. You know the ones: you type in your name, choose a username, enter your email address, and your password (twice), hit the submit button...and...bad things happen. The username is already taken. Worse, the form is cleared and you have to enter all that information all over again. Wroblewski provides advice for validation (without set-in-stone rules), and a bulleted list of best practices.
The final, and perhaps most interesting chapter in the book, covers the topic of Gradual Engagement. This is particularly timely given the kudzu-like proliferation of Web 2.0 applications and services as well as social networking sites and micro-blogging sites. Instead of starting your engagement with a new company that all your friends are raving about with YET ANOTHER registration form - Wroblewski highlights the benefits of moving a user through the application or service - actually engaging with it, and seeing it's benefits, while registration is either postponed, or handled behind the scenes. He explores web applications like JumpCut, where the user has gone all the way through creating, uploading and editing their video - and only when they actually want to publish and share it, does the user encounter a form - at which point they have already learned the service, it's benefits, and it's value. Wroblewski doesn't have any hard numbers about fall-off rates, but from a user experience perspective - my gut tells me it's better than confronting a first-time potential user with a form to fill out. I am looking forward to seeing how this approach plays out over the next year.
What is likely to win the most converts, though, is the joy Wroblewski takes in designing - which becomes clear as you page through the book. He isn't just an ardent evangelizer, following the rituals of going to conferences selling snake oil. He's been there in the trenches, just like you; he's done this a hundred, maybe a thousand times; he's tested these ideas - and he has a framework for you to use from day one.
If you want to trust my snap judgment, buy this book: you'll be delighted. If you want to trust my more reflective second judgment, after having read, re-read, and ruminated over the finer points he makes in the book, buy it: you'll be delighted but left wanting more. I don't know if more could have been written about Web Form Design, but if so, I would have gladly read that as well.
For example, an eye tracking study found that fewer mistakes were made when presenting mutually exclusive form groups as horizontal tabs. Wroblewski still recommended vertical tabs and used studies that were not cited as the basis for his recommendation. There are numerous places in the books where studies are referenced but not cited. This is very disappointing to me as I cannot reference the study for context and methodology.
I read this book cover-to-cover and I will continue to use it as a reference. It has clear and insightful observations accompanied by eye-tracking studies, some user testing, and a healthy dose of experience. It's a great companion when making recommendations to a client, superiors, designers, developers, or anyone else.
This book is great for people new to the field or people in juxtaposed fields such as developers, designers, and QA personnel.
I recommend this book.