<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Corbin, Michelle and Yoel Strimling</title>	<link>http://tc.eserver.org/authors/Corbin,_Michelle_and_Yoel_Strimling</link>
	<description>A bibliography of works by Corbin, Michelle and Yoel Strimling 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>Corbin, Michelle and Yoel Strimling</title>
		<link>http://tc.eserver.org/dir/Corbin,_Michelle_and_Yoel_Strimling</link>
	</image>
	<item>
		<title>Editing Modular Documentation: Some Best Practices</title>
		<link>http://tc.eserver.org/32036.html</link>
		<guid>http://tc.eserver.org/32036.html</guid>
		<description>Much has been said about the creation of modular documentation - from content management systems, to information architecture, to delivery forms, to the usability of modular content (content being easier to use, easier to understand, and easier to find), and so on. However, not much has been said about the editing of that content, and what the editor&apos;s role is in such an environment.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Corbin,_Michelle_and_Yoel_Strimling.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>