<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Web Design&gt;Document Design&gt;Help</title>	<link>http://tc.eserver.org/dir/Articles/Web-Design/Document-Design/Help</link>
	<description>A listing of the most recently indexed works about Articles and Web Design and Document Design and Help 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>Articles&gt;Web Design&gt;Document Design&gt;Help</title>
		<link>http://tc.eserver.org/dir/Articles/Web-Design/Document-Design/Help</link>
	</image>
	<item>
		<title>Web 2.0, and Me</title>
		<link>http://tc.eserver.org/35210.html</link>
		<guid>http://tc.eserver.org/35210.html</guid>
		<description>As help systems continue to evolve, whatever name they are called, we will increasingly have to face responsibility for their content, and bring their expertise to what we write. The new systems provide us with all the required tools that tell us the problems with their content. It is up to us to leverage that information to provide better content, and act as ambassadors for products that we write. If writers can go a step ahead, and use their help information to sell products, and reduce the burden on customer support, we would have truly arrived.</description>
	</item>
	<item>
		<title>Calling Accessible Context-Sensitive Help with Unobtrusive DOM/JavaScript: A Help Authoring Guide</title>
		<link>http://tc.eserver.org/35190.html</link>
		<guid>http://tc.eserver.org/35190.html</guid>
		<description> This Fast Track tutorial demonstrates two methods to call Context-Sensitive Help in a Web Form. We&apos;ll discover how Unobtrusive DOM/JavaScript achieves the desired result in calling Context-Sensitive help, and demonstrate how to keep the Structure, Presentation, and Behavior layers of a web page completely separate from one another ensuring good practice with current web standards and accessibility rules.</description>
	</item>
	<item>
		<title>Constructing a One-Stop &quot;Answer Station&quot; Website for Software Users</title>
		<link>http://tc.eserver.org/27658.html</link>
		<guid>http://tc.eserver.org/27658.html</guid>
		<description>The web allows us to easily provide updated documentation to our users, but why stop there? There is more to making users successful quickly than just providing documentation. By creating a complete &apos;Answer Station&apos; that is accessible from the application or product, we can not only direct users to that updated documentation, but we can also provide information about technical support, consulting, training, sales, etc.&#xD;&#xD;This article discusses writing a proposal for an Answer Station, determining content, working with other departments to gather information, designing the site, making that design work with an existing corporate website, dealing with tool issues, and finally, going live.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Web-Design/Document-Design/Help.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>