<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Croft, Jeff</title>	<link>http://tc.eserver.org/authors/Croft,_Jeff</link>
	<description>A bibliography of works by Croft, Jeff 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>Croft, Jeff</title>
		<link>http://tc.eserver.org/dir/Croft,_Jeff</link>
	</image>
	<item>
		<title>Frameworks for Designers</title>
		<link>http://tc.eserver.org/28908.html</link>
		<guid>http://tc.eserver.org/28908.html</guid>
		<description>These days, &apos;framework&apos; is quite a buzzword in web development. With JavaScript frameworks like the Yahoo User Interface library, jQuery, and Prototype getting a lot of attention and web application frameworks like Rails and Django getting even more, it seems like everyone is using some kind of framework to build their sites. But what exactly is a framework? And are they only useful to programmers, or can we web designers benefit from the concept, as well?</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Croft,_Jeff.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>