Slashdot Mirror
Deliver First Class Web Sites
Michael J. Ross writes "Experienced and conscientious Web developers, in their efforts to learn from the mistakes of others and to avoid repeating them on their own projects, tend to accumulate tips and recommendations for the many aspects of successfully creating Web sites. These best practices take the form of bookmarked Web pages, saved articles, downloaded PDF files, scribbled notes on scraps of paper, and hastily created documents that will be better organized one of these days, when the developer's schedule becomes less hectic (sure...). Being difficult if not impossible to find later, these pearls of wisdom are rarely consulted before or during each new Web site project. What the developer needs is a book that brings together as many of these best practices as possible, without being overwhelming. Deliver First Class Web Sites: 101 Essential Checklists may be the answer." Read the rest of Michael's review.
Deliver First Class Web Sites
author
Shirley Kaiser
pages
331
publisher
SitePoint
rating
8
reviewer
Michael J. Ross
ISBN
0975841904
summary
A collection of Web site development best practices.
Authored by Shirley Kaiser, this book was published by SitePoint in July 2006, under the ISBN 0975841904. The publisher maintains a Web page devoted to the book, where visitors will find the book's table of contents online, a free preview (chapters 6, 12, and 14, in PDF format), editorial and customer reviews, a link to download all of the checklists (also in PDF) for all customers, links and an FAQ for ordering directly from SitePoint, and errata (none reported, as of this writing). The fact that SitePoint is willing to allow readers to post unmoderated comments and ratings of their books, suggests that it has real confidence in the quality of the book's material and readers' evaluations of it.
The aforesaid Web page also offers an online version of the index, but without any of the book's page numbers. At first glance, this might seem rather odd, but it does make some sense: Page numbers online would be of little use without the book itself, which of course already contains the index. Perhaps the index keys are offered to supplement the table of contents in helping the prospective customer learn what topics are covered in the book. In any case, this is the first time that I have seen a book's index online, and it will likely not be the last, if other publishers see the value in following suit.
In the preface, Shirley Kaiser explains that the book is intended to be "...a single source of solid information on best practices for everything from planning, designing, developing, and testing, to launching a web site and maintaining it in the long term. By compiling all this information into checklists, we've turned a vast wealth of detail into convenient, easy-to-scan, simple-to-use chunks organized by topic." A technical reader quickly scanning the book, would likely conclude that the author's goal has been achieved, because the book's 101 checklists comprise over 500 checkpoints, and almost all of them are expanded with at least a paragraph of more detailed explanation; many have accompanying code or images to illustrate the checkpoint.
The book's 331 pages of material are organized into 16 chapters, followed by an appendix that focuses on e-commerce advice. The topics covered in the chapters are: how to get started on a Web development project; planning the Web site with a client; assembling the site's content; managing that content; site usability; color schemes and functionality; information architecture; designing the site's navigation; W3C standards and recommendations; site accessibility; optimization of site performance; search engine optimization; design principles; site testing, including accessibility and usability; launch preparation and execution; post-launch follow-up and maintenance.
In terms of the specificity and usefulness of the checkpoints, they are not all consistently stellar, which arguably would have been an impossible expectation anyway. They range from the obvious (e.g., "Use consistent markup") to the not-so-obvious but equally valid (e.g., "Perform content audits"). Some of the checkpoints may on the surface appear mundane, but they could be a lifesaver further down the road, should a project turn sour (e.g., "Archive a copy of the handover package"). Some of them may seem painfully obvious to any decent developer (e.g., "Check all hyperlinks" and "Test all scripting functions"), but even the majority of those are violated on a daily basis, even by major Web sites, which have no excuse for such sloppiness.
The primary value of this book is how it neatly consolidates a considerable amount of worthy advice culled from the author's research and decade in the trenches of the Internet. The book probably will not replace all of the best practices that any top-notch developer will have assembled over the years — especially as none of it addresses advanced topics — but it could easily serve as a solid foundation upon which to add any supplemental recommendations that the book does not cover. Moreover, the book's material is presented in a fairly concise and quite readable format, making use of what appears to be a font slightly larger than is found in the typical computer programming book.
My only complaint with this title is the way that SitePoint continues to include a growing number of advertising pages, at the end of the book, with the bulk of each page black (sometimes even a bit smeared), and containing absolutely no details about the books being advertised. When SitePoint first began publishing books, if memory serves, they would only include one or two such over-the-top pages — possibly because they had so few titles to advertise at the inception. But now they are truly overdoing it. In Deliver First Class Web Sites: 101 Essential Checklists, no fewer than a dozen pages are wasted on this unwanted advertising. It would have been far more effective and efficient to simply list the 11 books' titles with a brief summary of each. Whoever decided to waste all that paper and ink, clearly did not read and understand some of the most basic checkpoints presented earlier in the book concerning type size and page content.
But overall, Deliver First Class Web Sites: 101 Essential Checklists is a much-needed book that brings together a wide range of valuable Web development best practices.
Michael J. Ross is a computer consultant, freelance writer, and the editor of PristinePlanet.com's free newsletter."
You can purchase Deliver First Class Web Sites from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
Authored by Shirley Kaiser, this book was published by SitePoint in July 2006, under the ISBN 0975841904. The publisher maintains a Web page devoted to the book, where visitors will find the book's table of contents online, a free preview (chapters 6, 12, and 14, in PDF format), editorial and customer reviews, a link to download all of the checklists (also in PDF) for all customers, links and an FAQ for ordering directly from SitePoint, and errata (none reported, as of this writing). The fact that SitePoint is willing to allow readers to post unmoderated comments and ratings of their books, suggests that it has real confidence in the quality of the book's material and readers' evaluations of it.
The aforesaid Web page also offers an online version of the index, but without any of the book's page numbers. At first glance, this might seem rather odd, but it does make some sense: Page numbers online would be of little use without the book itself, which of course already contains the index. Perhaps the index keys are offered to supplement the table of contents in helping the prospective customer learn what topics are covered in the book. In any case, this is the first time that I have seen a book's index online, and it will likely not be the last, if other publishers see the value in following suit.
In the preface, Shirley Kaiser explains that the book is intended to be "...a single source of solid information on best practices for everything from planning, designing, developing, and testing, to launching a web site and maintaining it in the long term. By compiling all this information into checklists, we've turned a vast wealth of detail into convenient, easy-to-scan, simple-to-use chunks organized by topic." A technical reader quickly scanning the book, would likely conclude that the author's goal has been achieved, because the book's 101 checklists comprise over 500 checkpoints, and almost all of them are expanded with at least a paragraph of more detailed explanation; many have accompanying code or images to illustrate the checkpoint.
The book's 331 pages of material are organized into 16 chapters, followed by an appendix that focuses on e-commerce advice. The topics covered in the chapters are: how to get started on a Web development project; planning the Web site with a client; assembling the site's content; managing that content; site usability; color schemes and functionality; information architecture; designing the site's navigation; W3C standards and recommendations; site accessibility; optimization of site performance; search engine optimization; design principles; site testing, including accessibility and usability; launch preparation and execution; post-launch follow-up and maintenance.
In terms of the specificity and usefulness of the checkpoints, they are not all consistently stellar, which arguably would have been an impossible expectation anyway. They range from the obvious (e.g., "Use consistent markup") to the not-so-obvious but equally valid (e.g., "Perform content audits"). Some of the checkpoints may on the surface appear mundane, but they could be a lifesaver further down the road, should a project turn sour (e.g., "Archive a copy of the handover package"). Some of them may seem painfully obvious to any decent developer (e.g., "Check all hyperlinks" and "Test all scripting functions"), but even the majority of those are violated on a daily basis, even by major Web sites, which have no excuse for such sloppiness.
The primary value of this book is how it neatly consolidates a considerable amount of worthy advice culled from the author's research and decade in the trenches of the Internet. The book probably will not replace all of the best practices that any top-notch developer will have assembled over the years — especially as none of it addresses advanced topics — but it could easily serve as a solid foundation upon which to add any supplemental recommendations that the book does not cover. Moreover, the book's material is presented in a fairly concise and quite readable format, making use of what appears to be a font slightly larger than is found in the typical computer programming book.
My only complaint with this title is the way that SitePoint continues to include a growing number of advertising pages, at the end of the book, with the bulk of each page black (sometimes even a bit smeared), and containing absolutely no details about the books being advertised. When SitePoint first began publishing books, if memory serves, they would only include one or two such over-the-top pages — possibly because they had so few titles to advertise at the inception. But now they are truly overdoing it. In Deliver First Class Web Sites: 101 Essential Checklists, no fewer than a dozen pages are wasted on this unwanted advertising. It would have been far more effective and efficient to simply list the 11 books' titles with a brief summary of each. Whoever decided to waste all that paper and ink, clearly did not read and understand some of the most basic checkpoints presented earlier in the book concerning type size and page content.
But overall, Deliver First Class Web Sites: 101 Essential Checklists is a much-needed book that brings together a wide range of valuable Web development best practices.
Michael J. Ross is a computer consultant, freelance writer, and the editor of PristinePlanet.com's free newsletter."
You can purchase Deliver First Class Web Sites from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
Learn to spell first!
Linux O Muerte!
It's not necessarily a checklist. It's clean, consistent design based on outstanding communication with your client. You can build the best design in the history of Web design, but if it doesn't match the vision of your client, then you are simply toast.
Surely by definition, a conscientious web developer would be exactly the person who wouldn't, in fact, have all their heuristics and guidelines lying around on pieces of paper/mental notes/etc?
Not to discount the book, but I know in at least the case of the firm I work for, we wikify such matters, and they're regularly converted to a more formal procedures manual. Is this unusual for web development?
Perfecting the art of insanity since 1982
not to be flamebait or anything, but atleast I was not impressed with his sample creations..
Use more Flash, Baby!!!!
For some reason Slashdot links to B & N, but if you look at the Amazon listing [amazon.com], you can see that some sellers are offering the book considerably cheaper.
http://slashdot.org/book.review.guidelines.shtml :
Speaking of links, please do not include links in your reviews to online bookstores. Slashdot has an linking arrangement with Barnes & Noble; that's why when bn.com carries a particular book, you'll see a link to it at the bottom of the review.
Use memorable URLS, and even better are guessable URLs.
3 24324
You know, foo.com/contact, foo.com/about, not foo.com/bar.xyz?asda1=324324324324324324&fds=3247
Surely, Kaiser can't be serious.
She is serious, AND keep calling her Shirley.
Thank you! Thank you! I'll be here all week. Be sure to try the fish!!!
The best thing a Web developer can do is to avoid AJAX.
If you need the functionality of AJAX for your website, then you shouldn't be making a website. Instead, you should be developing a standalone application with networking capabilities. If you write your application in Python or Ruby, you can take advantage of many of the benefits that JavaScript offers. Not only do you get portability, but when using Ruby or Python you get access to a wide variety of libraries and toolkits that just aren't available to AJAX developers.
Never, ever, under any circumstances, for any reason, no matter how much you are paid, threatened or if everyone else is doing it, use Flash for your opening page.
Nothing short of an excessively annoying car commercial which perpetually runs on local radio stations makes my hand move faster than to get away from a site where Flash is required to see what's there.
We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
Usually if you're close to having a 100% functional, accessible web site then some lunatic will decide to make something needlessly depend on javascript. Wikis and formal procedures don't help in that situation, especially when it's been done by an individual intent on pissing everyone else off. Don't you just love "team players"?
I bet book orders are pouring in now that Slashdot ran this story.
Does Slashdot at least get pay-per-click referrals?
I looked through the review for an idea of what the phrase "first class" might mean to the writers, but I didn't spot it. This was a way of getting at the real question: What sort of web site is being pushed here?
;-)
My suspicion, based on lots of other similar examples of advice on building web sites the Right Way, is that "first class" means flashy and entertaining. Maybe I'm wrong, but experience here says to expect the worst.
Not that I'm objecting to that. There's a demand for entertainment on the web. But there's also a demand for informative sites, and the design criteria for information and entertainment are very different.
Most of the web sites I've been involved with are of the informative type. For such sites, the canonical "first class" site is google.com, not (for example) yahoo.com. For a more complex site, news.google.com works pretty well.
But I didn't get a feel from the review or the author's web site what their criteria for "first class" might be. Unless I get a clear idea what sort of web site is being pushed, I probably won't be spending my money on any book of advice.
(I might also obsever that most entertainment sites are really in need of good advice on how to do the job right. But I probably don't need to tell that to anyone who visits them often.
Those who do study history are doomed to stand helplessly by while everyone else repeats it.
of cource you are going to pimp Amazon using your Amazon associates account
Thanks to file sharing, I purchase more CDs
Thanks to the RIAA, I buy them used...
Tom Caudron
http://tom.digitalelite.com/
-Tom
I don't think this author is particularly qualified to speak to "first class" web design. The author's own design company, SKDesigns, is entirely unimpressive. The portfolio includes things like this. So why is Slashdot heaping on the publicity?
Does this book include seo guide or just design issues?
Bhavesh
Source to top search engine ranking
One thing I'd like to see more of in web development are keyboard shortcuts. (This really only applies to websites built for the backend, not so much the front end.) The problem is that websites tend to be a very cumbersome tool as far as human computer interaction is concerned; after all, web pages were originally intended to view documents! Web developers need to program more javascript shortcuts in to their code. Even just simple stuff, like instead of searching for the next button with your mouse, just being able to press 'n'. Want to view a support ticket? Just press 's' and the ticket number. Worker productivity would skyrocket.
Most people perceive "new web technology" as an end in itself, and will rewrite all their software to be web-based without realizing the strengths and weaknesses of the new platform. When this happens, you get is really really bad software. For example, I know some people who work in customer service who were moved off of a telnet based support system to a web gui and lost their minds when a single command line entry became 5 mouse clicks and lots of scrolling with 1 second page loads.
Splash pages in general turn me off. When I go to a website I don't want to have an extra page with a link to click in order to get to the content. Don't make me waste my time and bandwidth on junk like:
"Welcome to My Web Site! Click to Continue!"
Love sees no species.
One thing that really bothers me about many web sites is this: If I have to enter my name, address etc., I frequently find that the web page designer thinks that all countries are the same.
I may find that I am required to write in which state I live. My country doesn't have states.
Or I may be required to write a 10-digit phone number. My phone number has 8 digits.
Or I may be forced to put the postal code after the city. In my country, the postal code goes before the city.
Dear web form designers: It is not unreasonable to expect that people know how to write their own address correctly. You don't have to check everything for them. (Especially if you don't know what to check for.)
</rant>
All kidding aside, based on the Table of Contents this seems to be just an updated version of "How to Design A Website", albeit it looks a bit more detailed than those versions of the past. I like that they mention things like "backups" and other useful topics for the serious mom-and-pop sites (at least they will know what a backup is!)
Still, imagine what those books from the 90's would look like to a modern website developer...
The reviewer mentions that "none of it addresses advanced topics" which to me indicates that yeah, it's great for getting started (as the title suggests) but you should read it fast... the content is probably already out of date. In my opinion, the dead-tree versions of "How to Design a Website" are a bit of an anachronism in this day and age.
"Whoever would overthrow the liberty of a nation must begin by subduing the freeness of speech."--Benjamin Franklin
Looks like it is a book by a front page user....
Web design and development are two different things, everyone can design but only a few can develop.
Got Code?
This is probably an excellent resource, but at this point it is one of many. The persistent problem is not developers, but clients. Internal or external, it doesn't matter. When marketing managers and O-level executives have a resource that tells them that they need to stop making decisions based on what their favorite colors are, or what websites their kids like to visit, we'll all be better off. In the mean time, at least there's Don't Make Me Think. But if the decisionmakers who have the pursestrings don't know what they're doing, a lot of the best practices advocated by developers never sees the light of day.
Read the EFF's Fair Use FAQ
beverly hills
90210
ca
I'll just use my special getting high powers one more time...
Save yourself $14.78 (!!) by buying the book here: Deliver First Class Web Sites. And if you use the "secret" A9.com discount, you can save an extra 1.57%!
More than a book, what the developer really needs is an IDE that he can TAG with tips he creates himself for various situations. As an example, let's say you're using javascript and do a lot of for loops through arrays. You happen across something that tells you that a best practice is to turn the length of the array into a variable before you loop through it so you don't have to access the length on every itteration. It would be cool to be able to "tag" the expression "for (" so that your helpful tip will appear in a line above or below the text edit window that reminds you to do THAT instead of doing "for(i=0;i
Then someone could create a web service with all of these tips that people vote on (like when the tag appears, you can say "yes this was helpful" or "no, don't show me this again" and the best practices will rise to the top.
The problem with the idea of a best practices book is that it's just one more thing I have to pick up while I'm doing my job. I need something that will happen intelligently and INLINE with my workflow, yet unobtrusively enough that it doesn't get in my way if I DON'T want to use it (like if that for loop is looping through something where the array length might change in the middle of my loop).
Can someone work up something like THAT (that I can use in Visual Studio AND Editplus?)
Wait a minute, not all Flash is bad, right?
ok, if it's annoying it's probably Flash or animated Gif (thats why firefox has Adblock)
However, the use of Flash doesn't *have* to be annoying?
does it?
It doesn't play well with countless browser features, including context menus, keyboard focus, accessibility, internationalization, DOM, CSS, text scaling, and copying. It doesn't work on all platforms. It requires a special tool to write, and has a spec that prevents you from using it to write your own tool.
If there was an HTML tag that worked just like <a href=...> but did all these bad things -- broke context menus, keyboard focus, accessibility, internationalization, DOM, CSS, scaling, cross-platform support, the clipboard -- wouldn't that fit the very definition of "annoying"?
The only reason anybody puts up with the crap that is Flash is because it does animation. Therefore the only possible argument in favor of Flash is "my animated graphics and sounds are so cool it's worth losing out on all the normal functionailty of your web browser.
And sometimes, maybe it is, like in the case of YouTube. But unless that's your web page's primary purpose, then no, it's not.
would people object against a well designed Flash site?
Flash can do so much more than plain HTML (olthough usually used for bad things, though)
It does more than HTML in one case: animation. It does far less in all others.
"There is no such word as "alot," and if there is, there shouldn't be. It's "a lot." Two words, not one."
thankslot for the PSA!
Just came across this in a Google Ad promising "Boot Up Any PC to Pure DOS. Include All Major DOS Commands!":
http://www.pcbeginner.com/tools/pcdoctor.htm
I wish this website booted into DOS.
tidokoro
what turns a man's karma neutral? lust for gold? power? or just a heart born full of neutrality?
Why would slashdot pimp this one book? There are hundreds of web site design books equally has horrible as this one. The website for the design company selling this book is terrible, as pointed out be a previous slashdotter. Why don't we use slashdot space for things that are important and cool. This is a pile of pulped wood created by a non-technical self-promoter. How about a good reference on Tomcat Jakarta? How about a cool book on AJAX? How about a slammin' book on integrating Tomcat Jakarta, J2EE and SQL Server?!!
Come on, we expect more...
Personally, I liked moving up to Gmail in 2004, after using Pine and Elm since 1992. Thank Ajax for finally bringing me an email experience that is greater in both functionality AND accessibility than pine. It's nice to finally see these "attachment" things people are always talking about.
-Clio
Karma: Bad (mostly from not giving a fuck)
Blog: http://clintjcl.wordpress.com