<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Quinn, Laura S.</title>	<link>http://tc.eserver.org/authors/Quinn,_Laura_S.</link>
	<description>A bibliography of works by Quinn, Laura S. 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>Quinn, Laura S.</title>
		<link>http://tc.eserver.org/dir/Quinn,_Laura_S.</link>
	</image>
	<item>
		<title>Designing for Limited Resources</title>
		<link>http://tc.eserver.org/33362.html</link>
		<guid>http://tc.eserver.org/33362.html</guid>
		<description>Even in an ideal world, designs must optimise both the user experience and the business return. When resources are limited, the design must be optimised to make the best use of all resources as well. To account for this complexity, it is important to have a clear understanding of both sides of the design equation--what you have to work with and what you are trying to build.</description>
	</item>
	<item>
		<title>Comparing Open Source CMSes: Joomla, Drupal, and Plone</title>
		<link>http://tc.eserver.org/33217.html</link>
		<guid>http://tc.eserver.org/33217.html</guid>
		<description>Open source content management systems (CMS) are particularly attractive to the nonprofit community because of their cost-efficiency, but what do these systems actually do? And what are the differences between the most common CMSs? We’ll compare Joomla, Drupal, and Plone for typical nonprofit needs.</description>
	</item>
	<item>
		<title>Designing for Limited Resources</title>
		<link>http://tc.eserver.org/21751.html</link>
		<guid>http://tc.eserver.org/21751.html</guid>
		<description>When resources are limited, the design must be optimized to make the best use of all resources. To account for this complexity, it is important to have a clear understanding of both sides of the design equation—what you have to work with and what you are trying to build.</description>
	</item>
	<item>
		<title>Defining Feature Sets Through Prototyping</title>
		<link>http://tc.eserver.org/21333.html</link>
		<guid>http://tc.eserver.org/21333.html</guid>
		<description>Defining requirements and features can be a daunting task under the best of circumstances. The Vision Prototype allows the user-centered vision to be seen—and discussed—by all team members and then easily translated into a set of functional requirements.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Quinn,_Laura_S..xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>