<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Zeldman, Jeffrey</title>	<link>http://tc.eserver.org/authors/Zeldman,_Jeffrey</link>
	<description>A bibliography of works by Zeldman, Jeffrey in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Zeldman, Jeffrey</title>
		<link>http://tc.eserver.org/dir/Zeldman,_Jeffrey</link>
	</image>
	<item>
		<title>Understanding Web Design</title>
		<link>http://tc.eserver.org/34481.html</link>
		<guid>http://tc.eserver.org/34481.html</guid>
		<description>We get better design when we understand our medium. Yet even at this late cultural hour, many people don’t understand web design. Among them can be found some of our most distinguished business and cultural leaders, including a few who possess a profound grasp of design—except as it relates to the web. If we want better sites, better work, and better-informed clients, the need to educate begins with us.</description>
	</item>
	<item>
		<title>Twenty Signs You Don’t Want that Web Design Project</title>
		<link>http://tc.eserver.org/33342.html</link>
		<guid>http://tc.eserver.org/33342.html</guid>
		<description>Most clients are good clients, and some clients are great clients. But some jobs are just never going to work out well. Herewith, a few indicators that a project may be headed to the toilet.</description>
	</item>
	<item>
		<title>Version Targeting: Threat or Menace?</title>
		<link>http://tc.eserver.org/30885.html</link>
		<guid>http://tc.eserver.org/30885.html</guid>
		<description>Real DOM support is a game changer. Enabled by default, it would bring many sites to their knees. That would break the web, and not in quotes. Providing IE8&apos;s greater compliance on an opt-in basis is the only way to get everyone over the scripting hump.</description>
	</item>
	<item>
		<title>The Trouble with Web Standards</title>
		<link>http://tc.eserver.org/30650.html</link>
		<guid>http://tc.eserver.org/30650.html</guid>
		<description>You may mistrust web standards because of bad experiences with buggy browsers. Or you might have converted a site from HTML to XHTML, only to discover that their layouts suddenly looked different in standards-compliant browsers. Don&apos;t give in to the dark side! Web standards are here to stay.</description>
	</item>
	<item>
		<title>Web 3.0</title>
		<link>http://tc.eserver.org/26674.html</link>
		<guid>http://tc.eserver.org/26674.html</guid>
		<description>To you who are toiling over an AJAX- and Ruby-powered social software product, good luck, God bless, and have fun. Remember that 20 other people are working on the same idea.</description>
	</item>
	<item>
		<title>CSS in Action: A Hybrid Layout</title>
		<link>http://tc.eserver.org/25737.html</link>
		<guid>http://tc.eserver.org/25737.html</guid>
		<description>In this chapter, we&apos;ll complete our production task by using CSS to achieve design effects that support the brand and make the site more attractive without relying on GIF text, JavaScript rollovers, spacer pixel GIF images, deeply nested table cell constructions, or other staples of old-school web design.</description>
	</item>
	<item>
		<title>XHTML by Example: A Hybrid Layout</title>
		<link>http://tc.eserver.org/25736.html</link>
		<guid>http://tc.eserver.org/25736.html</guid>
		<description>In this chapter, we’ll roll up our sleeves and apply what we’ve learned &#xD;about XHTML thus far to mark up a real-world design project. The &#xD;markup we create will be partly structural, partly transitional, and &#xD;fully standards-compliant.</description>
	</item>
	<item>
		<title>Much Ado About 5K</title>
		<link>http://tc.eserver.org/25539.html</link>
		<guid>http://tc.eserver.org/25539.html</guid>
		<description>A full-fledged website under 5K? Some of the brightest people in the industry swore it could not be done. Yet hundreds of developers not only came in under the 5K budget, they built great sites in the process. Zeldman explores how the 5K Awards rocked the web.</description>
	</item>
	<item>
		<title>Tackling Usability Gotchas in Large-scale Site Redesigns</title>
		<link>http://tc.eserver.org/25536.html</link>
		<guid>http://tc.eserver.org/25536.html</guid>
		<description>Redesigns can solve old usability problems while creating new ones that must be solved in turn. From the lessons of the ALA 3.0 redesign comes this quick study in remapping content without frustrating readers.</description>
	</item>
	<item>
		<title>Why Gecko Matters: What Netscape’s Upcoming Browser Will Mean to the Web</title>
		<link>http://tc.eserver.org/25521.html</link>
		<guid>http://tc.eserver.org/25521.html</guid>
		<description>Netscape is about to unleash its new browser, built around the Gecko rendering engine. Theoretically the first completely standards-compliant web browser, Gecko enters a world where most people use IE5 (which is not completely standards-compliant). Is Netscape’s effort too little, too late? Or is it the beginning of a new and better way to create websites? Zeldman articulates The Web Standards Project&apos;s position and explains what Netscape’s browser will mean to the web.</description>
	</item>
	<item>
		<title>From Table Hacks to CSS Layout: A Web Designer&apos;s Journey</title>
		<link>http://tc.eserver.org/25518.html</link>
		<guid>http://tc.eserver.org/25518.html</guid>
		<description>Redesigning A List Apart using CSS should have been easy. It wasn&apos;t. The first problem was understanding how CSS actually works. The second was getting it to work in standards-compliant browsers. A journey of discovery.</description>
	</item>
	<item>
		<title>Why IE5/Mac Matters</title>
		<link>http://tc.eserver.org/25520.html</link>
		<guid>http://tc.eserver.org/25520.html</guid>
		<description>It complies with two key web standards. And leaves out two others. It&apos;s IE5 Macintosh Edition, the first browser on any platform to truly support HTML 4 and CSS-1. Its accessibility enhancements put the user in charge, and its clever new features solve long-standing cross-platform and usability problems. All this ... but still no XML or DOM.</description>
	</item>
	<item>
		<title>Patents, Royalties, and Web Standards</title>
		<link>http://tc.eserver.org/28362.html</link>
		<guid>http://tc.eserver.org/28362.html</guid>
		<description>We urge all ALA readers to examine the W3C Patent Policy draft, read The Web Standards Project’s opinion of same, and mail your comments to the W3C.</description>
	</item>
	<item>
		<title>Better Living Through XHTML</title>
		<link>http://tc.eserver.org/20224.html</link>
		<guid>http://tc.eserver.org/20224.html</guid>
		<description>Everything you wanted to know about converting from HTML to XHTML, including why you’d want to, tools that help, changes in the way browsers display XHTML pages, shortcuts, bugs, workarounds, and other tips you won’t find elsewhere.</description>
	</item>
	<item>
		<title>A CSS Redesign in Five Easy Pages</title>
		<link>http://tc.eserver.org/20217.html</link>
		<guid>http://tc.eserver.org/20217.html</guid>
		<description>Building a standards-compliant redesign of ALA should have been easy. It wasn’t. The first problem was understanding how CSS actually works. The second was getting it to work in standards-compliant browsers. A journal of discovery.</description>
	</item>
	<item>
		<title>Getting Paid</title>
		<link>http://tc.eserver.org/20227.html</link>
		<guid>http://tc.eserver.org/20227.html</guid>
		<description>As businesses struggle to stay in business, many are short–changing vendors or woefully delaying payment. Zeldman laments the difficulties of getting paid.</description>
	</item>
	<item>
		<title>To Hell With Bad Browsers</title>
		<link>http://tc.eserver.org/20218.html</link>
		<guid>http://tc.eserver.org/20218.html</guid>
		<description>Why does ALA look like @#$ in your 4.0 browser? Read this now.</description>
	</item>
	<item>
		<title>Why Don&apos;t You Code for Netscape?</title>
		<link>http://tc.eserver.org/20228.html</link>
		<guid>http://tc.eserver.org/20228.html</guid>
		<description>Long considered the Holy Grail of web design, &apos;backward compatibility&apos; has its place; but at this point in web development history, shouldn’t we be more concerned about forward compatibility? ALA makes the case for authoring to web standards instead of browser quirks.</description>
	</item>
	<item>
		<title>Fix Your Site With the Right DOCTYPE</title>
		<link>http://tc.eserver.org/13502.html</link>
		<guid>http://tc.eserver.org/13502.html</guid>
		<description>Per HTML and XHTML standards, a DOCTYPE (short for “document type declaration”) informs the validator which version of (X)HTML you’re using, and must appear at the very top of every web page. DOCTYPEs are a key component of compliant web pages: your markup and CSS won’t validate without them.</description>
	</item>
	<item>
		<title>SMIL When You Play That: A Gentle Introduction to SMIL + SVG</title>
		<link>http://tc.eserver.org/13266.html</link>
		<guid>http://tc.eserver.org/13266.html</guid>
		<description>SMIL is an easy-to-learn, HTML-like language for creating &apos;TV-like multimedia presentations such as training courses on the Web,&apos; according to the W3C. The current SMIL recommendation is 1.0, and you can read all about it at the W3C address cited immediately above, and at another one we’ll mention later. This is our way of avoiding adding fifty pages to this article.</description>
	</item>
	<item>
		<title>Circle Jerks</title>
		<link>http://tc.eserver.org/10889.html</link>
		<guid>http://tc.eserver.org/10889.html</guid>
		<description>Recently, on several well-known community and personal sites, familiar cries were heard: &apos;A is a sellout. B, C, and D are much better than X, Y, and Z. N, O, and P are overrated, back-scratching link whores.&apos; The web design community goes through this kind of self-examination every three months. Under the banner of honest criticism, names are named, guesses about motivation are sketched, and sometimes entire bodies of work are dismissed. Useful and reasonable criticism is often advanced in these debates. But too frequently it is overshadowed by those with the loudest voices, whose anger can sound like passionate truth to those who&apos;ve nurtured similar thoughts but been afraid to express them publicly. Undoubtedly some people sell out, some are overrated, and some use links merely to advance their careers or promote their friends. But even when the accused are guilty as charged, the accusations change nothing—they simply create turmoil.</description>
	</item>
	<item>
		<title>Naked</title>
		<link>http://tc.eserver.org/10887.html</link>
		<guid>http://tc.eserver.org/10887.html</guid>
		<description>Every content producer cowers before twin demons. On one side stands the publisher’s mandate: you must make your deadline. Readers expect it, and readers lose trust if you’re late to market. On the other side stands the editor’s prime directive: you must publish worthwhile material. Readers expect it, and readers lose trust if you publish filler simply because an issue is due. Publish junk once, and you lose a few discerning people. Do it continually, and you lose everybody.</description>
	</item>
	<item>
		<title>Fear of Style Sheets</title>
		<link>http://tc.eserver.org/10563.html</link>
		<guid>http://tc.eserver.org/10563.html</guid>
		<description>Cascading Style Sheets (CSS) save bandwidth, vastly reducing the size of your files when compared to old-style &lt;FONT FACE&gt; markup. With Styles, your sites load faster. You work faster, too. Styles shave grueling hours of grunt-work off your design workload: one brief CSS document can style an entire domain; and when it&apos;s time to redesign, you can execute site-wide changes in minutes instead of days.         Style Sheets bring genuine leading and sophisticated margination to the web, easing our readers&apos; eyestrain while bringing us the control of negative space we take for granted in other media. They offer exciting new possibilities, from absolute positioning, to interactive manipulation of text and images. And they allow us to create sophisticated layouts while doing no harm to the underlying structure of our documents – ensuring that search engines (as well as hand-held devices, web phones, and other futuristic browser morphs) can &apos;understand&apos; our pages as easily as readers do.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Zeldman,_Jeffrey.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>