<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Content Management&gt;Document Design</title>	<link>http://tc.eserver.org/dir/Design/Content-Management/Document-Design</link>
	<description>A listing of the most recently indexed works about Design and Content Management and Document Design 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>Design&gt;Content Management&gt;Document Design</title>
		<link>http://tc.eserver.org/dir/Design/Content-Management/Document-Design</link>
	</image>
	<item>
		<title>What Information Developers Can Learn from Software Developers</title>
		<link>http://tc.eserver.org/35677.html</link>
		<guid>http://tc.eserver.org/35677.html</guid>
		<description>The shift in information development from a narrative to a modular writing style reflects the established shift towards modularization of source code. What can information developers learn from software developers? What are the challenges and benefits of the modular approach? </description>
	</item>
	<item>
		<title>The Right and Wrong of Quark and Adobe Strategies</title>
		<link>http://tc.eserver.org/31753.html</link>
		<guid>http://tc.eserver.org/31753.html</guid>
		<description>What distinguishes the underlying strategies of Adobe InDesign from QuarkXPress is the absence or presence of a content management system (CMS). And each company asserts that it’s following the less-traveled road. The problem is they’re both taking roads most traveled because of their respective stances towards integrated content management systems, and I’ll show you how after looking at their respective strategies.</description>
	</item>
	<item>
		<title>An Evaluation of the Effectiveness of Automated Templates</title>
		<link>http://tc.eserver.org/30269.html</link>
		<guid>http://tc.eserver.org/30269.html</guid>
		<description>Automated templates are an alternative to traditional supporting information for helping users perform complex tasks. In this study users performed tasks with and without wizard to trial and error, printed manuals, and online the use of automated templates. Results suggest that if fakes help, and examined the use of supporting information some time for users to learn to use automated templates, but in performing complex tasks. We also considered once they do, the templates help users perform tasks more whether automated templates serve an educational successfully and more quickly. </description>
	</item>
	<item>
		<title>Extracting Content</title>
		<link>http://tc.eserver.org/23135.html</link>
		<guid>http://tc.eserver.org/23135.html</guid>
		<description>How to extract content from a portion of a PDF document.</description>
	</item>
	<item>
		<title>Hyperlinking Documents in PageMaker</title>
		<link>http://tc.eserver.org/18341.html</link>
		<guid>http://tc.eserver.org/18341.html</guid>
		<description>These four supertips deal with adding links to your Adobe® PageMaker® 7.0 online documents:&#xD;* Learn how to create anchors and simple page-to-page links.&#xD;* Explore linking to external URLs using the Hyperlinks palette.&#xD;* Drag links from Netscape Navigator directly onto elements on PageMaker document pages.&#xD;* Create automatic tables of contents and index links for PageMaker documents that are exported to Adobe Acrobat® PDF files.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Content-Management/Document-Design.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>