<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Farkas, David K.</title>	<link>http://tc.eserver.org/authors/Farkas,_David_K.</link>
	<description>A bibliography of works by Farkas, David K. 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>Farkas, David K.</title>
		<link>http://tc.eserver.org/dir/Farkas,_David_K.</link>
	</image>
	<item>
		<title>Managing Three Mediation Effects that Influence PowerPoint Deck Authoring</title>
		<link>http://tc.eserver.org/34197.html</link>
		<guid>http://tc.eserver.org/34197.html</guid>
		<description>Reviews the extreme claims that have been made about PowerPoint. Sets forth practical design ideas that are especially applicable to technical presentations. Explains three ways in which PowerPoint can subtly influence the intended meaning of deck authors and shows how these problems can be addressed.</description>
	</item>
	<item>
		<title>Understanding and Using PowerPoint</title>
		<link>http://tc.eserver.org/29700.html</link>
		<guid>http://tc.eserver.org/29700.html</guid>
		<description>The relatively new and controversial medium of PowerPoint presentations has generated much casual commentary but little careful analysis or empirical research. This rhetorical study attempts to advance our understanding of the medium and provides practical guidance regarding deck design, rehearsal, and performance. The study considers the reasons for the controversy surrounding PowerPoint, offers a taxonomy of the kinds of content that appear in decks, and looks closely at how presenters interact with individual slides, in particular the way in which they &apos;synch&apos; to each bullet point and then &apos;launch&apos; an oral gloss of that point. In addition, the study provides criteria for writing bullet points and suggests reasons why presenters include excess text on their slides.</description>
	</item>
	<item>
		<title>Explicit Structure in Print and On-Screen Documents</title>
		<link>http://tc.eserver.org/29236.html</link>
		<guid>http://tc.eserver.org/29236.html</guid>
		<description>The structure of print and on-screen documents is made explicit through headings and links. Three important concepts for understanding explicit structure are (1) the display-unit properties of each document medium, (2) the flexible relationship between explicit and implicit structure, and (3) the distinction between populated and unpopulated locations in a hierarchy. These concepts help us better understand standard print documents, structured writing, websites, help systems, and PowerPoint, as well as the potential effects of content management systems on how documents are created.</description>
	</item>
	<item>
		<title>Facilitating Research on Global Partnerships in Technical Communication Programs</title>
		<link>http://tc.eserver.org/26536.html</link>
		<guid>http://tc.eserver.org/26536.html</guid>
		<description>Discussion about fostering international relationships for academic programs in technical communication.</description>
	</item>
	<item>
		<title>Programmatic Roles in Research, Professional Development, and Ethical Responsibility</title>
		<link>http://tc.eserver.org/26534.html</link>
		<guid>http://tc.eserver.org/26534.html</guid>
		<description>Four presentations about the roles of programs in the professional, ethical, and research roles of its students and faculty.</description>
	</item>
	<item>
		<title>Academic Training for Independent Contractors and Consultants</title>
		<link>http://tc.eserver.org/26208.html</link>
		<guid>http://tc.eserver.org/26208.html</guid>
		<description>We need academic, along with, professional training, defining &apos;academic training&apos; as conceptual and theoretical, future-oriented and speculative.</description>
	</item>
	<item>
		<title>What&apos;s Happening: Theory and Research</title>
		<link>http://tc.eserver.org/26206.html</link>
		<guid>http://tc.eserver.org/26206.html</guid>
		<description>What will the &apos;document of the future&apos; look like? What will be the new balance between text and other channels of communication?</description>
	</item>
	<item>
		<title>Our Little Help Machines and Their Invisibilities</title>
		<link>http://tc.eserver.org/22927.html</link>
		<guid>http://tc.eserver.org/22927.html</guid>
		<description>This paper examines the four kinds of invisibility Johnson-Eilola associates with minimalist help systems: fast information access that reduces user reflection and questioning, impersonal writing style that assumes the Shannon-Weaver communication model, narrow scope that leads to training but not teaching, and interface designs that oversimplify user tasks. For each of the four, the paper questions Johnson-Eilola&apos;s conclusions. Ultimately, the problems with truncated online help systems may disappear, as help systems are increasingly linking to the web, where adequate conceptual information is often supplied and opportunities for a social context for help are available.</description>
	</item>
	<item>
		<title>Browse Sequence in Online Help</title>
		<link>http://tc.eserver.org/21505.html</link>
		<guid>http://tc.eserver.org/21505.html</guid>
		<description>A browse sequence enables users to navigate through a series of help topics in the sequence established by the help author. Although often omitted from help systems, the browse sequence is useful and will become essential as print documentation diminishes. Effective design&#xD;options for a browse sequence include multiple&#xD;segments, rings, branching, and the use of a browse&#xD;button to take the user to the first topic in the current&#xD;segment of the browse sequence.</description>
	</item>
	<item>
		<title>Migrating to WinHelp 4.0 for Windows ’95</title>
		<link>http://tc.eserver.org/20118.html</link>
		<guid>http://tc.eserver.org/20118.html</guid>
		<description>WinHelp 4 is the help environment for Microsoft’s Windows 95 and Windows NT operating systems. Among the&#xD;important new features of WinHelp 4 are more capable&#xD;secondary windows, shortcut buttons, the ability to integrate&#xD;multiple help files, What’s This? help, and better support for&#xD;online coaches. Help authors must understand both the&#xD;construction and the design aspects of these new features.&#xD;They must also deal with the complexities of the transition&#xD;from Windows 3.1 help to WinHelp 4.</description>
	</item>
	<item>
		<title>The Future of the User&apos;s Guide in the Documentation Set</title>
		<link>http://tc.eserver.org/18810.html</link>
		<guid>http://tc.eserver.org/18810.html</guid>
		<description>With online help rapidly becoming the central piece in&#xD;the documentation set, software companies might consider two different directions in their documentation planning. The first is to think of the user’s guide as a high-quality supplement to help. The second is to think of the user&apos;s guide as a transitional piece that will adequately support users while they make the transition to a largely online documentation set. Each of these directions carries different implications for the design of the user’s guide.</description>
	</item>
	<item>
		<title>Web Design</title>
		<link>http://tc.eserver.org/14841.html</link>
		<guid>http://tc.eserver.org/14841.html</guid>
		<description>TC 437 is a project-oriented course in website design. Implementation is not emphasized. Students receive a grounding in rhetoric, hypertext theory, user interface design, graphic design, and project management as these apply to the Web. Students also study the societal and ethical contexts of the Web and Internet.</description>
	</item>
	<item>
		<title>John Carroll&apos;s &lt;i&gt;The Nurnberg Funnel&lt;/i&gt; and Minimalist Documentation</title>
		<link>http://tc.eserver.org/13767.html</link>
		<guid>http://tc.eserver.org/13767.html</guid>
		<description>A review of the use of minimalist theory in the creation of documentation sets.</description>
	</item>
	<item>
		<title>Online Editing, Mark-Up Models, and the Workplace Lives of Editors and Writers</title>
		<link>http://tc.eserver.org/13768.html</link>
		<guid>http://tc.eserver.org/13768.html</guid>
		<description>Despite the fact that most editing is still performed on paper, there are compelling reasons to begin marking copy on the computer.</description>
	</item>
	<item>
		<title>Guidelines for Designing Web Navigation</title>
		<link>http://tc.eserver.org/10409.html</link>
		<guid>http://tc.eserver.org/10409.html</guid>
		<description>As Web sites grow larger and more complex, the challenge of designing effective user navigation increases. We offer designers (as well as those evaluating existing Web sites) a set of 12 guidelines encompassing that attempt to cover the most important and broadly relevant navigation issues. These guidelines are grouped under four topics: (1) Designing an effective link, (2) Managing large numbers of links, (3) Providing orientation information, and (4) Augmenting link-to-link navigation. With each guideline there is an example and a synthesis of the most relevant and compelling research, theory, and expert opinion. These guidelines apply to what can be broadly termed informational Web sites rather than sites for game-players, art sites, and sites intended for whimsy and fun.</description>
	</item>
	<item>
		<title>The Logical and Rhetorical Construction of Procedural Discourse </title>
		<link>http://tc.eserver.org/10366.html</link>
		<guid>http://tc.eserver.org/10366.html</guid>
		<description>A very useful perspective for understanding procedural (&apos;how to&apos;) discourse and for writing better procedures is to view procedures as a framework of actions and states. The states include desired (goal) states and unwanted states; the actions are user actions, system actions, and external events. This framework underlies all kinds of procedural discourse, including streamlined-step procedures, the model that predominates in online help systems. The components that make up streamlinedstep procedures are best understood as combinations of actions and states. Procedural discourse is also highly rhetorical in nature. We can see the rhetorical implications of actions and states in the various models of procedural discourse, and in specific strategies that writers implement. Because of its terse and rigid nature, the streamlinedstep model is not well suited for certain rhetorical strategies and cognitive goals, and so while recognizing the efficiency of the streamlined-step model, writers should not neglect more </description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Farkas,_David_K..xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>