Product Description

You code. And code. And code. You build only to rebuild. You focus on making your site compatible with almost every browser or wireless device ever put out there. Then along comes a new device or a new browser, and you start all over again.

You can get off the merry-go-round.

It's time to stop living in the past and get away from the days of spaghetti code, insanely nested table layouts, tags, and other redundancies that double and triple the bandwidth of even the simplest sites. Instead, it's time for forward compatibility.

Isn't it high time you started designing with web standards?

Standards aren't about leaving users behind or adhering to inflexible rules. Standards are about building sophisticated, beautiful sites that will work as well tomorrow as they do today. You can't afford to design tomorrow's sites with yesterday's piecemeal methods.

• Slash design, development, and quality assurance costs (or do great work in spite of constrained budgets)
• Deliver superb design and sophisticated functionality without worrying about browser incompatibilities
• Set up your site to work as well five years from now as it does today
• Redesign in hours instead of days or weeks
• Welcome new visitors and make your content more visible to search engines
• Stay on the right side of accessibility laws and guidelines
• Support wireless and PDA users without the hassle and expense of multiple versions
• Improve user experience with faster load times and fewer compatibility headaches
• Separate presentation from structure and behavior, facilitating advanced publishing workflows

Product Details

• Amazon Sales Rank: #125292 in Books
• Published on: 2003-06-05
• Original language: English
• Number of items: 1
• Binding: Paperback
• 456 pages

From the Back Cover

You code. And code. And code. You build only to rebuild. You focus on making your site compatible with almost every browser or wireless device ever put out there. Then along comes a new device or a new browser, and you start all over again.

You can get off the merry-go-round.

It's time to stop living in the past and get away from the days of spaghetti code, insanely nested table layouts, tags, and other redundancies that double and triple the bandwidth of even the simplest sites. Instead, it's time for forward compatibility.

Isn't it high time you started designing with web standards?

Standards aren't about leaving users behind or adhering to inflexible rules. Standards are about building sophisticated, beautiful sites that will work as well tomorrow as they do today. You can't afford to design tomorrow's sites with yesterday's piecemeal methods.

• Slash design, development, and quality assurance costs (or do great work in spite of constrained budgets)
• Deliver superb design and sophisticated functionality without worrying about browser incompatibilities
• Set up your site to work as well five years from now as it does today
• Redesign in hours instead of days or weeks
• Welcome new visitors and make your content more visible to search engines
• Stay on the right side of accessibility laws and guidelines
• Support wireless and PDA users without the hassle and expense of multiple versions
• Improve user experience with faster load times and fewer compatibility headaches
• Separate presentation from structure and behavior, facilitating advanced publishing workflows

About the Author

Jeffrey Zeldman¿s personal web site (www.zeldman.com) has welcomed more than 16 million visitors and is read daily by thousands in the web design and development industry. In 1998, Zeldman co-founded The Web Standards Project (www.webstandards.org), a grassroots coalition of web designers and developers that helped end the Browser Wars by persuading Microsoft and Netscape to support the same technologies in their browsers.

Customer Reviews

A little too much tub-thumping
As an amateur website designer, who tries to stick to modern standard-based layout, I'm always keen to pick up tips from the pros. This book certainly helps with this, there are a lot of useful tricks and pointers to websites I might otherwise have missed.

Like other reviewers, I found that the earlier part of the book is overly concerned with the methods of 5 to 10 years ago. People buying the book will probably be sold on CSS-based layout (or at least standards as the method of choice) before they buy. So a much shorter case would suffice. There is an over-emphasis on older browsers as well: Netscape 4.x, IE/Win 4 and IE/Mac 5 get much too much space. Most people are targeting IE 6, Firefox Opera 8 and Safari today.

Overall, there is a lot to learn from this book. Be prepared to skip over the lecturing, though.

How frustrating........memories of the past
After the first 200 pages of negativity, I had to throw the book in the bin!

Zeldman continually patronises the developers of the past working in environments of which the browser providers had no standard (to which still continues to a greater or lesser degree today). The fact that multiple instances of a site were required to cater for the anomolies between browser types and versions is true however CSS would not have saved the day then nor now.

Zeldman is right......you do need standards and from what I was picking up on his thoughts, the standards you create yourself are probably appropriate to the work you are performing. This I agree with Zeldman however blaming the development strategies of the past are not the way forward. I do understand Zeldmans frustrations from the past however blaming each developer for using multiple font tags is not really approprite for the time he refers.

I was looking for technical inspriation to the world of CSS (of which I totally agree is the way forward). Certainly, the first two hundred pages do not offer this. I could not cope reading further......hence the book went in the bin.

Out of date and mainly rhetoric
It's ironic that a book that is so much about future proofing spends so much time talking about version 4.0 browsers, making much of the book fairly obselete.

Much of the other content is out of date. It reccomends the box model hack, when conditional comments could be used. Fahner image replacement is also detailed, when newer methods eliminate the need for a non-semantic span element.

It is also vague. For example many of the reasons cited to use XHTML are not really convincing. "New browsers love XHTML ... and accord it special treatment" is too vague. To say that using an XHTML 1.0 strict doctype because it switches all browsers to standards/almost standards mode and therefore your site is more likely to work in all browsers would be better.

In short it attempts to fight old beliefs with new beliefs, rather than knowledge