<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>KeyContent.org</title>	<link>http://tc.eserver.org/publisher/KeyContent.org</link>
	<description>A listing of works published by KeyContent.org 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>KeyContent.org</title>
		<link>http://tc.eserver.org/dir/KeyContent.org</link>
	</image>
	<item>
		<title>Key Resources</title>
		<link>http://tc.eserver.org/34436.html</link>
		<guid>http://tc.eserver.org/34436.html</guid>
		<description>This portal (organized into categories) lists external resources for content developers, technical communicators, information architects, and web designers.</description>
	</item>
	<item>
		<title>Wiki-fying Docs: Is Using Customer-Accessible Wikis for End-User Documentation Gaining Momentum?</title>
		<link>http://tc.eserver.org/34417.html</link>
		<guid>http://tc.eserver.org/34417.html</guid>
		<description>While the effort to provide more interactivity and power to the end-user seems to suggest that we open up a wiki to allow them to add and edit content, the basic idea of a set of edited documentation is now challenged with a social network of participating customers, all of whom may now edit, add, and delete content. How social can you go? This article is an attempt to look at the process of evaluating the use of a wiki for end-user documentation, if such a thing can exist. Are the two types of customer content — wikis and end-user documentation — mutually exclusive?</description>
	</item>
	<item>
		<title>What is Social Bookmarking</title>
		<link>http://tc.eserver.org/34418.html</link>
		<guid>http://tc.eserver.org/34418.html</guid>
		<description>A discussion of social bookmarking; its use and trends.</description>
	</item>
	<item>
		<title>Limits of Automated Audio</title>
		<link>http://tc.eserver.org/29198.html</link>
		<guid>http://tc.eserver.org/29198.html</guid>
		<description>This is a list of limitations of the types of automated audio translation offered by such services as Talkr.com. Since we do not see a list in their help center, we thought we would compile our own list and offer it as a wiki page for any customers to keep a list of limitations. </description>
	</item>
	<item>
		<title>Wiki-fying Docs: Is Using Customer-Accessible Wikis for End-User Documentation Gaining Momentum?</title>
		<link>http://tc.eserver.org/29197.html</link>
		<guid>http://tc.eserver.org/29197.html</guid>
		<description>While the effort to provide more interactivity and power to the end-user seems to suggest that we open up a wiki to allow them to add and edit content, the basic idea of a set of edited documentation is now challenged with a social network of participating customers, all of whom may now edit, add, and delete content. How social can you go? This article is an attempt to look at the process of evaluating the use of a wiki for end-user documentation, if such a thing can exist. Are the two types of customer content--wikis and end-user documentation--mutually exclusive?</description>
	</item>
	<item>
		<title>Why Single-Source when you can Multi-Source?</title>
		<link>http://tc.eserver.org/28003.html</link>
		<guid>http://tc.eserver.org/28003.html</guid>
		<description>Single-sourcing allows authors to re-use content in different deliverables. This article explores using XML and a CMS (content management system) to take a different approach--multi-sourcing.</description>
	</item>
	<item>
		<title>Using a Wiki as an Organizational Portal</title>
		<link>http://tc.eserver.org/27999.html</link>
		<guid>http://tc.eserver.org/27999.html</guid>
		<description>We explain why we chose a wiki-based content management system (CMS) as the basis for the portal for KeyContent.org. We compare various tools and discuss other sites that have implemented similar software for collaborative solutions.</description>
	</item>
	<item>
		<title>How to Create an RSS Feed for any HTML Page</title>
		<link>http://tc.eserver.org/27868.html</link>
		<guid>http://tc.eserver.org/27868.html</guid>
		<description>How can you create an RSS for a specific HTML page, especially if the page-create software or web host doesn&apos;t provide an automated method. This article discusses how to use a screen scraper to quickly and easily create a RSS feed for any HTML page.</description>
	</item>
	<item>
		<title>Course Design and Content Organization: A Psychological Perspective</title>
		<link>http://tc.eserver.org/27594.html</link>
		<guid>http://tc.eserver.org/27594.html</guid>
		<description>While a lot of effort is spent on designing an effective structure of the course, individual memory is seemingly the more untouched and somehow neglected aspect of our efforts to develop effective learning solutions. There is a need to add a psychological perspective of memory and retention/recollection to the way we design learning solutions.</description>
	</item>
	<item>
		<title>Meaningful Microcontent</title>
		<link>http://tc.eserver.org/27593.html</link>
		<guid>http://tc.eserver.org/27593.html</guid>
		<description>Microcontent refers to small, granular, and possibly representative (that can provide a summary of or a navigation to a larger set of information) bits of information, typically available on the Web. An example in the domain of journalism might be headlines and news summaries, small bits of content that can be used on a front page of the news with links to more in-depth articles. The definition has grown in scope as much as in its application.</description>
	</item>
	<item>
		<title>Moving from Unstructured to FrameMaker Plus DITA</title>
		<link>http://tc.eserver.org/27595.html</link>
		<guid>http://tc.eserver.org/27595.html</guid>
		<description>This page provides some answers to the question &apos;What resources would you recommend for someone moving from unstructured Frame to Frame+DITA?&apos; Carla Martinek, Translation Coordinator/Editor, started making this list in response to a CMS question on the FrameMaker+DITA listserv, and thought it would be worth sharing.</description>
	</item>
	<item>
		<title>Content Management Glossary</title>
		<link>http://tc.eserver.org/26937.html</link>
		<guid>http://tc.eserver.org/26937.html</guid>
		<description>An interactive glossary of terms from content management systems.</description>
	</item>
	<item>
		<title>Documentation for Sarbanes-Oxley</title>
		<link>http://tc.eserver.org/26941.html</link>
		<guid>http://tc.eserver.org/26941.html</guid>
		<description>In the financial end of business, more work is being done with documentation, thanks to Sarbanes-Oxley and financial accountability.</description>
	</item>
	<item>
		<title>The Electric XML Acid Test</title>
		<link>http://tc.eserver.org/26935.html</link>
		<guid>http://tc.eserver.org/26935.html</guid>
		<description>This will be the story of my life from the time my boss came to me and said, &apos;Hey, maybe we could do that Knowledge Base in XML. I hear good things about that XML,&apos; to the time that I figured out everything I needed to know and deployed a fully functional XML knowledge base to the world.</description>
	</item>
	<item>
		<title>Process Pieces and Tools in Content Development</title>
		<link>http://tc.eserver.org/26940.html</link>
		<guid>http://tc.eserver.org/26940.html</guid>
		<description>As long as we are working with people, there will be clogs in the flow of information. As long as we are working for corporations, the bottom line will be money. With the dependence on computers and information in accessible and digital form, there is still a challenge in getting meaningful information. The tools, as advanced and automated as they are, will not fix all our problems. But we have to work with what we have, and automate as much of the production and maintenance of our content as possible.</description>
	</item>
	<item>
		<title>Review of &apos;Podcasting Solutions: Complete Guide to Podcasting&apos;</title>
		<link>http://tc.eserver.org/26938.html</link>
		<guid>http://tc.eserver.org/26938.html</guid>
		<description>I thoroughly enjoyed reading Podcasting Solutions: A Complete Guide to Podcasting by Michael W. Goeghegan and Dan Klass. I was able to digest the material quickly. The frustrating thing for me was that the title just didn&apos;t seem to fit the approachable and practical content that made the book such a treasure. For example, the subtitle &apos;A Complete Guide&apos; is a bit overstated, because it is not a compendium but a getting starting guide. Especially as time goes by and the field progresses, and more techniques and tools are developed, this book will become more out of date.</description>
	</item>
	<item>
		<title>Writing Documentation and Help for Eclipse Projects and Plugins</title>
		<link>http://tc.eserver.org/26936.html</link>
		<guid>http://tc.eserver.org/26936.html</guid>
		<description>Eclipse is an open-source community. One of its primary projects is the creation of &apos;an extensible development platform...for building software.&apos; This platform takes shape in the Eclipse workbench, a Java-based IDE (Integrated Development Environment).</description>
	</item>
	<item>
		<title>XML Authoring Group</title>
		<link>http://tc.eserver.org/26939.html</link>
		<guid>http://tc.eserver.org/26939.html</guid>
		<description>The XML Authoring Group is an informal gathering of technical communication professions in the Research Triangle Park (RTP) area of North Carolina who meet once every two months or so to discuss issues regarding the development of technical content with structure or XML tags. We are not a group of XML programmers and we are not beginners with XML either. We are using XML for developing, delivering, and maintaining technical content, not data.</description>
	</item>
	<item>
		<title>Bloom&apos;s Taxonomy in Technical Content Development</title>
		<link>http://tc.eserver.org/26933.html</link>
		<guid>http://tc.eserver.org/26933.html</guid>
		<description>Technical writers provide information enabling users to learn and apply various technologies. In the endeavor to enable users, technical writers often need to use different strategies of classification, presentation, and structuring for the different types of information. However, in most cases such classifications or decisions about the best method of presentation and optimum structure are guided by instinct and are rarely heuristic.&#xD;&#xD;In this article, we present an established classification of information called Bloom’s taxonomy (of educational objectives), which can help technical writers make decisions about content classification.</description>
	</item>
	<item>
		<title>Issues in Technical Writing</title>
		<link>http://tc.eserver.org/26474.html</link>
		<guid>http://tc.eserver.org/26474.html</guid>
		<description>Now it is very important to recognize the vital role of a technical writer and services expected to provide to justify the requirements of this profession. Since technical writer is a sub category of technical communication, that involves other categories involved in documentation, like content writer, software configuration manager, technical editor, information designer and many more.</description>
	</item>
	<item>
		<title>Review of &quot;User Interface Design for Programmers&quot;</title>
		<link>http://tc.eserver.org/26475.html</link>
		<guid>http://tc.eserver.org/26475.html</guid>
		<description>This is ostensibly a review of Joel Spolsky&apos;s book &quot;User Interface Design for Programmers&quot; by way of a comparison with Jef Raskin&apos;s &quot;The Humane Interface.&quot;</description>
	</item>
	<item>
		<title>Java Software Product Documentation</title>
		<link>http://tc.eserver.org/25877.html</link>
		<guid>http://tc.eserver.org/25877.html</guid>
		<description>This is a collaboration about the issues involved in creating documentation for Java software products. It began as correspondence between Bill Albing and Matthew Arnold Stern and includes a bit from Rick Sapir, too.</description>
	</item>
	<item>
		<title>Course Management Tools Review</title>
		<link>http://tc.eserver.org/25639.html</link>
		<guid>http://tc.eserver.org/25639.html</guid>
		<description>This is a summary of open source tools for what is variously called:&#xD;&#xD;    * distance learning&#xD;    * course management product or system&#xD;    * learning management system&#xD;    * virtual classroom &#xD;&#xD;</description>
	</item>
	<item>
		<title>Non-Traditional Roles: Case Studies</title>
		<link>http://tc.eserver.org/25638.html</link>
		<guid>http://tc.eserver.org/25638.html</guid>
		<description>This is a collaborative article with a list of case studies of technical communicators who assume new roles beyond the traditional ones like writing and editing. When they do so, they add value to their clients and organizations — as well as making themselves more valuable. This is in connection with the presentation slides from the STC Annual Conference (May 8-11, 2005 in Seattle, WA). The editor hopes these case studies will provide inspiration and encouragement for technical communicators who are looking for ways to add value.</description>
	</item>
	<item>
		<title>An Overview of Single Sourcing with an XML Content Management System</title>
		<link>http://tc.eserver.org/25378.html</link>
		<guid>http://tc.eserver.org/25378.html</guid>
		<description>Creating an XML-based Content Management System to single-source technical publications is as simple as 1 - 2 - 3. OK, maybe it isn&apos;t quite that easy, but this article discusses how it can be done.</description>
	</item>
	<item>
		<title>Documenting in N-Dimensional Space</title>
		<link>http://tc.eserver.org/25379.html</link>
		<guid>http://tc.eserver.org/25379.html</guid>
		<description>As technical communicators, we are being challenged with how to structure information in a multiple dimensional space made possible with Web technology.</description>
	</item>
	<item>
		<title>Nanotechnology: Implications for Transforming Communication</title>
		<link>http://tc.eserver.org/25380.html</link>
		<guid>http://tc.eserver.org/25380.html</guid>
		<description>The implications for transforming communication due to the development of nanotechnology is summarized.</description>
	</item>
	<item>
		<title>Authoring Content in XML</title>
		<link>http://tc.eserver.org/24650.html</link>
		<guid>http://tc.eserver.org/24650.html</guid>
		<description>XML authoring is the latest mode of electronic communication of content. XML is about freedom: freeing the content, freeing the author.</description>
	</item>
	<item>
		<title>Automating Documentation Generation</title>
		<link>http://tc.eserver.org/24649.html</link>
		<guid>http://tc.eserver.org/24649.html</guid>
		<description>The advent of automatic generation tools, that could automatically generate the information was a major step in the creation of more accurate documentation and it held the promise of saving time and money.</description>
	</item>
	<item>
		<title>The Documentation Elephant</title>
		<link>http://tc.eserver.org/24651.html</link>
		<guid>http://tc.eserver.org/24651.html</guid>
		<description>As technical communicators grapple with the changing processes and tools within which they work, we are seeing a gradual but dramatic evolution of technical writers into content developers.</description>
	</item>
	<item>
		<title>Health Risk Communication</title>
		<link>http://tc.eserver.org/24654.html</link>
		<guid>http://tc.eserver.org/24654.html</guid>
		<description>With government getting more involved with healthcare and organizations collecting information about the risks of some diseases, there is a plethora of information about heath risk that must be made accessible to the general public.</description>
	</item>
	<item>
		<title>Hurdles to Single-Sourcing</title>
		<link>http://tc.eserver.org/24653.html</link>
		<guid>http://tc.eserver.org/24653.html</guid>
		<description>LaTeX and DocBook  (and for that matter any manner of XML editors), which could be considered excellent single-sourcing tools, are almost never discussed.</description>
	</item>
	<item>
		<title>Integrating Javadoc (API Reference) with JavaHelp (Online Help): Two Approaches</title>
		<link>http://tc.eserver.org/24659.html</link>
		<guid>http://tc.eserver.org/24659.html</guid>
		<description>Although online help (either task-based or UI-centric) and API reference documents serve different purposes, there are times when you may want to at least create associations between the two or at most merge them into one system.</description>
	</item>
	<item>
		<title>Interactive Electronic Technical Manuals</title>
		<link>http://tc.eserver.org/24655.html</link>
		<guid>http://tc.eserver.org/24655.html</guid>
		<description>Advances have been made to provide that information online to the point where electronic access to the information involves nothing more futuristic than a laptop computer and access to a database.</description>
	</item>
	<item>
		<title>KeyContent.org</title>
		<link>http://tc.eserver.org/24644.html</link>
		<guid>http://tc.eserver.org/24644.html</guid>
		<description>Topics on technical communication written by experts in the field and posted online.</description>
	</item>
	<item>
		<title>The Limits of Content Management Systems</title>
		<link>http://tc.eserver.org/24652.html</link>
		<guid>http://tc.eserver.org/24652.html</guid>
		<description>The promise of content management systems as presently implemented in large corporations will never be fulfilled.</description>
	</item>
	<item>
		<title>Next Generation Microsoft Online Help</title>
		<link>http://tc.eserver.org/24658.html</link>
		<guid>http://tc.eserver.org/24658.html</guid>
		<description>Just as clothing styles change, and fall&apos;s fashion is different from summer&apos;s, so Microsoft presents it&apos;s new fall&apos;s fashion of online help to a fashion-consious entourage of software companies always eager to follow Microsoft&apos;s lead.</description>
	</item>
	<item>
		<title>Sarbanes-Oxley and Financial Accountability</title>
		<link>http://tc.eserver.org/24661.html</link>
		<guid>http://tc.eserver.org/24661.html</guid>
		<description>In the financial documentation realm, there are so many new buzz words, but they all boil down to the documentation equivalent of bean counting.</description>
	</item>
	<item>
		<title>Security Policy and Procedures Documentation</title>
		<link>http://tc.eserver.org/24660.html</link>
		<guid>http://tc.eserver.org/24660.html</guid>
		<description>With the nation intensifying its homeland security and industry focusing on computer security, the experienced technical communicator can assist with documenting procedures.</description>
	</item>
	<item>
		<title>Software Development Kit (SDK) Documents in 10 Simple Steps</title>
		<link>http://tc.eserver.org/24657.html</link>
		<guid>http://tc.eserver.org/24657.html</guid>
		<description>Here are the ten simple steps to successful software development kit (SDK) documentation.</description>
	</item>
	<item>
		<title>Sofware Development Theories</title>
		<link>http://tc.eserver.org/24648.html</link>
		<guid>http://tc.eserver.org/24648.html</guid>
		<description>The purpose of this collaboration is to collect on one portal page many of the current theories of software development, so that a technical communicator working with developers can at least be a bit familiar with these. It is by no means a thorough explanation of all the contemporary methodologies, both organic and imposed. But it should give readers some tips about what they are and where they can find more information.</description>
	</item>
	<item>
		<title>Then is Now, Small is Big: Transforming Trends</title>
		<link>http://tc.eserver.org/24645.html</link>
		<guid>http://tc.eserver.org/24645.html</guid>
		<description>This article is not really about the future; it is about the present, because the future is already upon us.</description>
	</item>
	<item>
		<title>Transforming Communication: The Dynamic Nature of Key Content</title>
		<link>http://tc.eserver.org/24647.html</link>
		<guid>http://tc.eserver.org/24647.html</guid>
		<description>Technical communication is a profession and a discipline in its own right and that it must determine whether it will be part of the game or give the reigns of thought leadership to another group outside our profession.</description>
	</item>
	<item>
		<title>Trends in Transforming Communication: Response to STC Editorial</title>
		<link>http://tc.eserver.org/24646.html</link>
		<guid>http://tc.eserver.org/24646.html</guid>
		<description>In stark contrast to the suggestion that software products are easier to use these days, I would have to say that in general they are _not_ any easier to use, _especially_ Microsoft products. While they have more features and deliver more performance, I would be careful about making a blanket statement about ease of use, especially when we know the resources to create usable products in most of the industry has been shrinking.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/KeyContent.org.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>