Deliver First Class Websites: 101 Essential Checklists (Anglais) Broché – 1 juin 2006
|Neuf à partir de||Occasion à partir de|
Descriptions du produit
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.
Détails sur le produit
Commentaires en ligne
Commentaires client les plus utiles sur Amazon.com (beta)
Contents: Let's Get Started - but How?; What to Find Out - Initial Questions to Answer; Preparing Web Site Content; Managing all the Content; Web Site Usability - Focusing on the User; Color; Information Architecture; Navigation; Best Coding Practice - W3C Standards and Recommendations; Creating Accessible Web Sites; Web Site Optimization; Search Engine Optimization; Design; Testing; Preparing for Launch; Post-launch Follow-up; Ecommerce Checklists; Index
The main thing to remember here is that this *isn't* an exhaustive reference manual on the items listed above. There have been many separate books written about any one of the items. But Kaiser does a nice job in distilling the best and common practices into a short format that can help you remember the things that you often forget. For instance, in Best Coding Practices, she reminds the reader to use proper heading elements, to use ul, ol, and li elements for lists, use for line breaks, not paragraph breaks, and so on. Rather than just say "because I said so", these recommendations are based on solid advice from standards groups and alternative forms of web readers (like page readers for sight-impaired people). You may think that it's no big deal, but the assistive technology works far better when you remember small things like this.
You'll likely find that some chapters are more appealing to you than others. She covers the entire range of development, from design through post-implementation review. So if you're a code monkey by nature, you'll probably gravitate towards those topics. Also, I design with Notes/Domino, so advice on laying out specific pages and determining your folder structure don't necessarily fit nicely in my dynamic web site generation world. But still, there's a lot of good advice regardless of where you're at and what you use...
This is one of those books that can help you consolidate a lot of what you already know to be right, and structure it such that you practice it properly on a regular basis...
I'll be frank, there are like 900 (or perhaps 9000?) checkboxes of "things to do" included in this book. Some are clearly "common sense," like:
"Provide obvious, clear error messages that explain how the user can resolve the error."
...but in practice are so rarely implemented! A couple of weeks ago, I was on the web site of one of the banks that I use. When I tried to access one of my accounts, it presented an error message telling me that I had to log back in due to inactivity. Of course, I had simply clicked on the account and there was no inactivity, but the site had some kind of a problem. The error message was totally irrelevant AND it suggested that the problem was MY fault because I was "inactive."
These kinds of things make a "web experience" either pleasant or terribly annoying. There is nothing worse than a web site that tells you that you're doing something wrong and doesn't explain how or even if there is a way to correct it. Shirley's book should DEFINITELY be read by those in the banking industry! ...and probably anyone else who wants their web site(s) to be encountered without the pain and frustration that comes from poorly considered content.
Shirley provides numerous examples of how to better "align" your site with the needs of users. And, that's what it is really about, isn't it? We don't make web sites for ourselves, we make them for those who visit them. If you're expecting people to visit your web site, you need to read this book. More importantly, you NEED to do what this book recommends. If you're not, you're treating your web users poorly.
One thing that I can definitely say about Shirley's work and that is she recommends that web masters check their server logs for web browsers. I use Linux and Opera and I am very tired of web sites that cater only to IE and Windoze. Her recommendations are useful and relevant, in that one should check their logs to see what kinds of client browsers are visiting their sites. This implies developing content suited to the various browers and testing the web site for compatibility with those kinds of clients. With the ever-growing expansion of web-centric devices and different platforms, it is wholly unacceptable to have floating content sitting over the top of other content particularly in forms where the data fields are REQUIRED for submission.
I was recently on a web site for insurance where a required field (zipcode) was errorneously displayed due to a floating border. Granted, it is difficult to test for the 20% in the "80/20" rule, but I don't do business with those who refuse to consider me, too. If you can't afford to lose the 20%, this book is definitely for you. If you just want to address the 80%, this book is an absolute requirement. If you follow even 10% of the recommendations presented in this book, you'll be a world ahead of where you are now with your web site(s)!
CMS discussions, navigation architecture, color management, W3C standards, SEO, Ecommerce checklists are just a few sections to be found. ... Highly recommended! *****