<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
categoryallspace2-Design Content Management
<channel>
	<title>Design&gt;Content Management</title>	<link>http://tc.eserver.org/dir/Design/Content-Management</link>
	<description>A directory of resources about design and content management in the field of technical communication.</description>
	<language>en-us</language>
	<atom:link href="http://tc.eserver.org/dir/Design/Content-Management.xml" rel="self" type="application/rss+xml" />
	<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</title>
		<link>http://tc.eserver.org/dir/Design/Content-Management</link>
	</image>
	<item>
		<title>Reusability 2.0: The Key to Publishing Learning</title>
		<link>http://tc.eserver.org/31352.html</link>
		<guid>http://tc.eserver.org/31352.html</guid>
		<description>What would you do if you had to develop and deliver personalized training to 900,000 employees, located in 34,000 different locations globally with a complex set of variables that changes training on a location-by-location basis? The key is reusability 2.0. While technology-delivered training has become mainstream in many organizations, most are still not fully leveraging the power of reusable learning content to meet their instructional needs.</description>
	</item>
	<item>
		<title>Companies Struggling with Unstructured Content</title>
		<link>http://tc.eserver.org/31272.html</link>
		<guid>http://tc.eserver.org/31272.html</guid>
		<description>Firms wrestling with unstructured data such as emails and spreadsheets don&apos;t see enterprise content management as the answer to their problems.</description>
	</item>
	<item>
		<title>Requirements of Content Management Systems: Definition According to Need</title>
		<link>http://tc.eserver.org/31141.html</link>
		<guid>http://tc.eserver.org/31141.html</guid>
		<description>In all companies, the requirements of an editorial system are worked out individually from the analysis of existing functioning and the definition of editorial and publication processes required in the future. The first important criteria for analysis are change frequencies and degree of reuse of the published information. The description of the information types as well as translation sequences constitute another starting point for the definition of a modular work process (single-source principle) and publication options (cross-media publishing).</description>
	</item>
	<item>
		<title>Let&apos;s Learn How Not To Mess Up With Your Web Site Content</title>
		<link>http://tc.eserver.org/30771.html</link>
		<guid>http://tc.eserver.org/30771.html</guid>
		<description>Every web site is conceived and designed keeping in view a particular purpose to serve. The aim of web site may vary: some web site intends to showcase products or services of the company it belongs to, some provides information to its target audience, or some just exposes its company on the web in a brand building exercise. This is to note that whatever be the nature of web site, web copy plays it own crucial role in furthering the interest of the site. It is imperative that web content is easy-to-read, easy-to-find, and easy-to-understand.</description>
	</item>
	<item>
		<title>To Structure or Not to Structure</title>
		<link>http://tc.eserver.org/30685.html</link>
		<guid>http://tc.eserver.org/30685.html</guid>
		<description>Behind all the questions about how to model something is a bigger question: do you model it at all? When is it obvious to structure some content, and when do you just throw it into the &apos;WYSIWYG pile&apos;?</description>
	</item>
	<item>
		<title>ATAG (Authoring Tool Accessibility Guidelines) Assessment of WordPress</title>
		<link>http://tc.eserver.org/30604.html</link>
		<guid>http://tc.eserver.org/30604.html</guid>
		<description>This document assesses WordPress 2.01 against the Authoring Tool Accessibility Guidelines 1.0.</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>Enterprise Architecture Essentials, Part 6: Manageability</title>
		<link>http://tc.eserver.org/30258.html</link>
		<guid>http://tc.eserver.org/30258.html</guid>
		<description>Organizations today face the challenge of two important enterprise architecture requirements: the need for agility and the overhead of regulatory governance. These requirements can be seen as mutually antagonistic -- if business processes must be flexible, then governance of those processes may be difficult. This article, part six in a six-part series, explores the notion of using manageability as a key enterprise architecture (EA) quality attribute to solve this problem. EA development is an ongoing process, and the central idea of this article is that by applying manageability as an EA attribute, the organizational processes, systems, and software become manageable.</description>
	</item>
	<item>
		<title>Ensuring A Successful CMS Implementation</title>
		<link>http://tc.eserver.org/30199.html</link>
		<guid>http://tc.eserver.org/30199.html</guid>
		<description>The single most important factor in a successful CMS implementation lies with you and your people. Your staff members are the principal users of the system, and the SMEs in your organization are the secondary users. It is their adoption of the new processes and governance structures that makes or breaks a CMS implementation. According to some, process and cultural change accounts for 90%, while technology contributes only 10% to the success of a CMS.</description>
	</item>
	<item>
		<title>Web Two-Point Uh-Oh</title>
		<link>http://tc.eserver.org/30121.html</link>
		<guid>http://tc.eserver.org/30121.html</guid>
		<description>The problem with many Web 2.0 applications is the assumption that the community&apos;s motives are good, or at least neutral. Perlin&apos;s column explores how one of the drawbacks of Web 2.0--potential loss of control over information--has manifested itself.</description>
	</item>
	<item>
		<title>The Meaning of Knowledge Management</title>
		<link>http://tc.eserver.org/29995.html</link>
		<guid>http://tc.eserver.org/29995.html</guid>
		<description>We hear the term knowledge management bandied about. It sounds suspiciously like a trendy new phrase for what we used to call &apos;documentation.&apos; In truth, knowledge management is more than documentation. It encompasses documentation, data management, library management, and information design. Knowledge management is increasingly important; as the amount of content has increased, the task of locating the information in the content has become more difficult. You see, information is different from content. And knowledge is something that derives from information.</description>
	</item>
	<item>
		<title>Moving to an XML-Based Web Site</title>
		<link>http://tc.eserver.org/29973.html</link>
		<guid>http://tc.eserver.org/29973.html</guid>
		<description>In early 2007, I started the task of reworking the ageing HyperWrite Web site. The site was originally created in 1995. It underwent a major rework (to a frames-based design) in 1997, and was reworked in 1999, 2000 and 2002. In the decade since the Web site was launched, not only has Web technology moved on, but HyperWrite&apos;s activities, focus and business direction are now quite different. Time and budget were set aside to renovate the site to better serve HyperWrite&apos;s business needs, and to serve as a practical example of the company&apos;s capabilities.</description>
	</item>
	<item>
		<title>Information Modeling: A Practical Approach</title>
		<link>http://tc.eserver.org/29913.html</link>
		<guid>http://tc.eserver.org/29913.html</guid>
		<description>Information models are a critical component of single sourcing, enterprise content management, and dynamic content management. The information model is your blueprint for the effective writing, structuring, and delivery of reusable content. This session explains how to design information models, including information product models and element models. It also explains the role of metadata and how to effectively design it.</description>
	</item>
	<item>
		<title>Blog 101: An Overview of Weblog Technologies</title>
		<link>http://tc.eserver.org/29742.html</link>
		<guid>http://tc.eserver.org/29742.html</guid>
		<description>A weblog or &apos;blog&apos; is a Web site with content consisting of a series of discrete postings added sequentially and presented in reverse chronological order. Historically used for personal Web sites, blogs in fact represent a form of lightweight content management that can be adapted to virtually any topic, including technical communication. The recent explosion of blogs is in part a result of the availability of publishing tools that simplify their creation. These tools vary significantly in capability, setup, and ease of use, and each offers advantages and disadvantages.</description>
	</item>
	<item>
		<title>What is Wiki?</title>
		<link>http://tc.eserver.org/29544.html</link>
		<guid>http://tc.eserver.org/29544.html</guid>
		<description>Wiki is a category of web server software that allows users to contribute content. Collaboration is the key to Wiki, which is designed as a powerful system for online communities to build web pages and web sites. Unlike blogs and forums, all users are allowed to contribute and edit existing content. Wiki is derived from the Hawaiian term &quot;wiki wiki&quot; meaning &quot;quick&quot;. The concept behind a Wiki is that collaboration on projects will move it along quicker.</description>
	</item>
	<item>
		<title>Reusable Information Object Strategy: Definition, Creation Overview, and Guidelines</title>
		<link>http://tc.eserver.org/29397.html</link>
		<guid>http://tc.eserver.org/29397.html</guid>
		<description>Cisco Systems recognizes a need to move from creating and delivering large inflexible training courses, to database driven objects that can be reused, searched, and modified independent of their delivery media. This effort is called the Reusable Information Object Strategy. This strategy defines the standards and process for designing and developing Reusable Information Objects (RIOs) at Cisco Systems.</description>
	</item>
	<item>
		<title>MarthaStewart.com: Making the Case for Customer-Centric Content Management</title>
		<link>http://tc.eserver.org/28946.html</link>
		<guid>http://tc.eserver.org/28946.html</guid>
		<description>When you hear the term &quot;customer centric content management&quot;, you might think we&apos;re talking about marketing content. We&apos;re not. We&apos;re talking about managing the delivery of all types of content, including marketing content. And, we&apos;re specifically talking about providing individuals -- people -- both existing and prospective customers, with only the content that is relevant and of interest to them. You may think you already do a good job at this task, but in most organizations, there is significant room for improvement. Most of the problems are caused by one very big mistake: failing to listen.</description>
	</item>
	<item>
		<title>Better Content Management through Information Architecture</title>
		<link>http://tc.eserver.org/28933.html</link>
		<guid>http://tc.eserver.org/28933.html</guid>
		<description>Content Management Systems promise so much: content is easier to publish, easier to update, and easier to find and use. Lots of promises, but do CMSs really deliver? Masood Nasser examines why Content Management Systems often fail and shows how Information Architecture can come to the rescue.</description>
	</item>
	<item>
		<title>Structured Content Management in the Enterprise</title>
		<link>http://tc.eserver.org/28562.html</link>
		<guid>http://tc.eserver.org/28562.html</guid>
		<description>As other areas within organizations begin to consider structured content for the same reasons as technical communication departments, technical communicators have a golden opportunity to assist others in their move toward structured CM.</description>
	</item>
	<item>
		<title>Which Hosted Wiki Is Right for You?</title>
		<link>http://tc.eserver.org/28306.html</link>
		<guid>http://tc.eserver.org/28306.html</guid>
		<description>A look at three hosted wiki services that are free or relatively cheap to use and provide easy tools to set up your wiki within minutes.</description>
	</item>
	<item>
		<title>Structuring Your Documents for Maximum Reuse</title>
		<link>http://tc.eserver.org/28184.html</link>
		<guid>http://tc.eserver.org/28184.html</guid>
		<description>A major topic among information development managers these days is single sourcing--writing information once and using it many times. Structured documents are critical for single sourcing. So, let&apos;s explore: what we mean by structuring documents; why structuring is useful; some of the concerns that writers have about structuring documents.</description>
	</item>
	<item>
		<title>Enterprise Portals: Tip of Which Iceberg?</title>
		<link>http://tc.eserver.org/28131.html</link>
		<guid>http://tc.eserver.org/28131.html</guid>
		<description>Summarizing recent CMS Watch research on portal software, Janus Boye finds that portal technology represents just the tip of the enterprise information iceberg. But given the diversity of portal scenarios, you should ask yourself which iceberg you&apos;re on.</description>
	</item>
	<item>
		<title>Dealing with Images in Content Management Systems, Part 1</title>
		<link>http://tc.eserver.org/27853.html</link>
		<guid>http://tc.eserver.org/27853.html</guid>
		<description>Most web-based content management systems offer a variety of tools to help contributors enter text. When it comes to graphics, content contributors are usually expected to provide web-ready images to the system. This means that either editorial users needs to know about image optimisation and web image formats, or additional staff are required to make web-ready images out of raw materials. This article demonstrates a technical solution to this problem.</description>
	</item>
	<item>
		<title>Information Architecture of Content Management</title>
		<link>http://tc.eserver.org/27104.html</link>
		<guid>http://tc.eserver.org/27104.html</guid>
		<description>When people think about content management, they generally think about it from a systems perspective, focusing primarily on tools and technology. While it is true that content management usually requires a technological solution, it also requires that content be designed for reuse, retrieval, and delivery to meet your authors&apos; and customers&apos; needs. Content management requires that tools be configured to support authoring, reviewing, and publishing tasks, but first, those tasks must be designed. Designing content and the processes to create, review, and publish it is what information architecture is all about.</description>
	</item>
	<item>
		<title>Ajax and Your CMS</title>
		<link>http://tc.eserver.org/27044.html</link>
		<guid>http://tc.eserver.org/27044.html</guid>
		<description>If a modern day Rip van Winkle woke up after just a year&apos;s sleep, he would be stunned by the buzz around Ajax today. Technology is moving very quickly in this space and whether you are a web author, a CMS developer, or a regular web user, Ajax will make some exciting changes to your world.</description>
	</item>
	<item>
		<title>Storage and Enterprise Content Management</title>
		<link>http://tc.eserver.org/26742.html</link>
		<guid>http://tc.eserver.org/26742.html</guid>
		<description>Almost one-third of the users reported that more than 40 percent of the storage spending is for unstructured documents and information--I think that percentage will continue to grow annually. Further, AIIM President John Mancini, who prepared the report, found that larger organizations especially are aggressively pursuing consolidation and rationalization of their storage and archiving strategies--but that cost is not the prime motivation behind those activities.</description>
	</item>
	<item>
		<title>XML Repositories: An Idea Whose Time has Finally Come</title>
		<link>http://tc.eserver.org/25981.html</link>
		<guid>http://tc.eserver.org/25981.html</guid>
		<description>This white paper discusses the role of an XML repository into today’s enterprise infrastructure. Virtually every database and repository provide some degree of XML support; however, there are important distinctions between support for XML as a data type and the role of a repository whose architecture and operations are optimized to support the broad family of XML recommendations and standards. Specifically, this white paper will explore: The nature and extent of XML use across the enterprise, cost and quality of service implications of an infrastructure with, and without, an XML repository, the evolution of XML repositories from both a technology and a market segment perspective, criteria to determine when an XML repository would add significant value to an existing infrastructure, and capability and packaging recommendations for XML repository functionality that can be used to evaluate specific offerings.</description>
	</item>
	<item>
		<title>Dynamic Websites: What Are They and Do You Need One?</title>
		<link>http://tc.eserver.org/25941.html</link>
		<guid>http://tc.eserver.org/25941.html</guid>
		<description>If you&apos;re thinking about getting, or updating, a website, chances are that you&apos;ll run into a web designer who will try to sell you on the idea of a &apos;dynamic site.&apos; Here&apos;s what you need to know in order to decide if such an approach is for you. </description>
	</item>
	<item>
		<title>A Quiet Revolution in Website Maintenance</title>
		<link>http://tc.eserver.org/25934.html</link>
		<guid>http://tc.eserver.org/25934.html</guid>
		<description>We&apos;re on the verge of a similar revolution in the area of website maintenance.</description>
	</item>
	<item>
		<title>Content Management Systems</title>
		<link>http://tc.eserver.org/25755.html</link>
		<guid>http://tc.eserver.org/25755.html</guid>
		<description>Content management systems are key to running an efficient website. Keep the development group out of the loop on updating content, and you will move ever so much faster. &apos;Content&apos; doesn’t need the same kind of source control that scripts and templates need. Specific design suggestions follow.</description>
	</item>
	<item>
		<title>The O&apos;Reilly Radar Blog</title>
		<link>http://tc.eserver.org/25562.html</link>
		<guid>http://tc.eserver.org/25562.html</guid>
		<description>The O&apos;Reilly Radar blog will track what we&apos;re tracking, and turn the blips into conversations.</description>
	</item>
	<item>
		<title>Rich Web Text Editing with Kupu</title>
		<link>http://tc.eserver.org/25567.html</link>
		<guid>http://tc.eserver.org/25567.html</guid>
		<description>Kupu is an open source application, written in JavaScript, that implements a flexible, full-featured HTML editor that runs in a web page without any special plugins. Its primary use is as an embedded editor in content management systems (CMS), like Zope or Plone, where it allows users to create their own web pages. Its design is flexible enough so that you can embed it into pretty much any web application without too much difficulty.</description>
	</item>
	<item>
		<title>Characteristics of Web Site Content</title>
		<link>http://tc.eserver.org/25064.html</link>
		<guid>http://tc.eserver.org/25064.html</guid>
		<description>Web site content must be recrudescent, repositorial, refluent, and rectilinear. What? Here&apos;s an innovative treatment of the essential attributes of online text.  Find out why great web site content generally has these 14 characteristics that start with a &quot;R&quot;.</description>
	</item>
	<item>
		<title>Graphic Designer Needs a Web CMS</title>
		<link>http://tc.eserver.org/24626.html</link>
		<guid>http://tc.eserver.org/24626.html</guid>
		<description>While you can create very powerful content management solutions with most open-source packages -- they have a much steeper learning curve than you experienced with HTML or Flash.</description>
	</item>
	<item>
		<title>My CMS Ate My Search Engine Rankings</title>
		<link>http://tc.eserver.org/24620.html</link>
		<guid>http://tc.eserver.org/24620.html</guid>
		<description>A dynamically-delivered site in and of itself need not denigrate your search engine rankings. Google and other spiders can follow dynamically-generated pages, up to a point. The key is to have links elsewhere on the site pointing specifically to those pages. If each page results from a purely dynamic query (e.g. using session variables), then you could be in trouble.</description>
	</item>
	<item>
		<title>Seeking a More Dynamic Website</title>
		<link>http://tc.eserver.org/24625.html</link>
		<guid>http://tc.eserver.org/24625.html</guid>
		<description>Putting content in a database will not inherently make your website more dynamic. Making sure that content providers keep information fresh, interesting, and relevant will  make your website more dynamic -- and ultimately more useful.</description>
	</item>
	<item>
		<title>STC and the W3C</title>
		<link>http://tc.eserver.org/24199.html</link>
		<guid>http://tc.eserver.org/24199.html</guid>
		<description>As technologies like XML, content management software (CMS), and single sourcing continue to seep into technical communication, they bring demands for cost-effective development, faster time-to-market, and automation. Meeting these demands will require standards for coding, language, metadata, and other such elements. The good old days of &apos;winging it&apos; in documentation are coming to an end.</description>
	</item>
	<item>
		<title>Content Management Systems: Don&apos;t Automate the Misery</title>
		<link>http://tc.eserver.org/23992.html</link>
		<guid>http://tc.eserver.org/23992.html</guid>
		<description>Few organizations have seen much good come of content-management BPR initiatives so far. Of the many reasons for these failures, one stands out: these BPR initiatives—and the systems they spawn—are focused on realizing organizational objectives without sufficient regard for the context, habits, and goals of the people who will actually use the system. </description>
	</item>
	<item>
		<title>Designing for Web Services</title>
		<link>http://tc.eserver.org/23818.html</link>
		<guid>http://tc.eserver.org/23818.html</guid>
		<description>Many technology companies, consultants, and academics are hyping the future of Web services. But how will this background transfer of data between applications affect the user experience?</description>
	</item>
	<item>
		<title>Website Automation: or, How I Saved My Sanity at the Last Minute</title>
		<link>http://tc.eserver.org/23695.html</link>
		<guid>http://tc.eserver.org/23695.html</guid>
		<description>If there&apos;s one thing I can&apos;t stand, it&apos;s maintaining a website. The design is the fun part— solving problems, incorporating a brand, meeting user needs. That&apos;s what we live for. But maintenance? Yuck.&#xD;&#xD;So I surveyed the technologies available; what could I automate to ease the burden on myself and other volunteers? This article presents the results of this undertaking. It focuses mainly on the processes and their results. I discuss details of the tools and technologies where relevant, but this is not a tutorial on any tools or technologies; I&apos;ll provide resources for further information.</description>
	</item>
	<item>
		<title>Information Architecture of Content Management</title>
		<link>http://tc.eserver.org/23636.html</link>
		<guid>http://tc.eserver.org/23636.html</guid>
		<description>When people think about content management, they generally think about it from a systems perspective, focusing primarily on tools and technology. While it is true that content management usually requires a technological solution, it also requires that content be designed for reuse, retrieval, and delivery to meet your authors&apos; and customers&apos; needs. Content management requires that tools be configured to support authoring, reviewing, and publishing tasks, but first, those tasks must be designed. Designing content and the processes to create, review, and publish it is what information architecture is all about. The Information Architecture section of The Rockley Report will focus on the different aspects of information architecture for content management. This article introduces you to some of the components of information architecture that we will cover in The Rockley Report over time.</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>Calculating the Cost of a Large-Scale Web Site</title>
		<link>http://tc.eserver.org/23056.html</link>
		<guid>http://tc.eserver.org/23056.html</guid>
		<description>A well-designed information architecture with intuitive organization, labeling, navigation, and indexing systems can significantly reduce the amount of time that users spend blundering through the hierarchies of Web sites and intranets. How much is this time-savings worth? The case is clearest for intranets where the users are your employees.</description>
	</item>
	<item>
		<title>Content Management Systems</title>
		<link>http://tc.eserver.org/22648.html</link>
		<guid>http://tc.eserver.org/22648.html</guid>
		<description>In this White Paper, we examine the benefits of automated content management, and demonstrate where efficiencies can be gained within your organization.&#xD;&#xD;&#xD;Web sites with more than a few information pages may benefit from content management systems (CMS). Content management systems are automated tools that allow for web site content to be created and administered on a recurring basis. The result puts the responsibility for content development into the hands of the authors (where it belongs) and out of the hands of the programmers.</description>
	</item>
	<item>
		<title>CMS Wiki</title>
		<link>http://tc.eserver.org/22443.html</link>
		<guid>http://tc.eserver.org/22443.html</guid>
		<description>CMS Wiki is a knowledge base for Content Management. </description>
	</item>
	<item>
		<title>Content Management and Information Architecture</title>
		<link>http://tc.eserver.org/22441.html</link>
		<guid>http://tc.eserver.org/22441.html</guid>
		<description>Content management is information architecture writ large.</description>
	</item>
	<item>
		<title>Information Architects and Their Central Role in Content Management</title>
		<link>http://tc.eserver.org/22414.html</link>
		<guid>http://tc.eserver.org/22414.html</guid>
		<description>The process of content management begins when an organization comes to the realization that it needs a system to manage content. While the interpretation of the term content management  (CM) can be as simple as a set of guidelines for organizing and maintaining content, more typically today it means a sophisticated software-based system. A full-featured content management system (CMS) takes content from inception to publication and does so in a way that provides for maximum content accessibility and reuse and easy, timely, accurate maintenance of the content base.</description>
	</item>
	<item>
		<title>Sources of CMS Uncertainty</title>
		<link>http://tc.eserver.org/22086.html</link>
		<guid>http://tc.eserver.org/22086.html</guid>
		<description>Not all aspects of a content management system (CMS) project are equally easy. While some elements can be installed  &apos;out of the box&apos;, others have proved difficult to implement. The starting point for improving the management of CMS projects is to recognise the sources of uncertainty, and how these affect project outcomes.</description>
	</item>
	<item>
		<title>Managing the Complexity of Content Management</title>
		<link>http://tc.eserver.org/21748.html</link>
		<guid>http://tc.eserver.org/21748.html</guid>
		<description>Content management systems suck. Or so you would think from the strife heard from analysts and practitioners alike. And yet, many websites regularly publish vast amounts of information with superior control and ease compared to manually editing pages.</description>
	</item>
	<item>
		<title>Greymatter, RSS, and Syndication</title>
		<link>http://tc.eserver.org/21103.html</link>
		<guid>http://tc.eserver.org/21103.html</guid>
		<description>Greymatter is an excellent web content management system. After you install it, you can begin to syndicate your content using XML. This article gives you an explicit step-by-step overview of how I created RSS 1.0 and RSS 0.92 files using Greymatter. It is assumed that you have some knowledge of HTML and XML, and that you have already installed Greymatter. Many examples and references are provided to help you along the way.</description>
	</item>
	<item>
		<title>The WebWord Content Management System</title>
		<link>http://tc.eserver.org/21108.html</link>
		<guid>http://tc.eserver.org/21108.html</guid>
		<description>The WebWord content management system is not technical, it is human. In fact, the technology is minimal and the web site works because a human understands and maintains the content using very simple tools. While this approach consumes a lot of time, it is simple and cost effective. Small and medium web sites can get along without using content management systems.</description>
	</item>
	<item>
		<title>Designing an Information Set for Single-Sourcing</title>
		<link>http://tc.eserver.org/20747.html</link>
		<guid>http://tc.eserver.org/20747.html</guid>
		<description>The single source in a robust single source system is not any one of the outputs that may be created from that source. The single source is an information set from&#xD;which many outputs may be created. Designing an&#xD;information set is different from designing a document.&#xD;Greater structure is required, and that structure must be&#xD;available to the process that creates information products&#xD;as output, not simply to the reader.&#xD;A good information set design involves creating a data&#xD;model, mapping information relationships, and defining&#xD;patterns of change.</description>
	</item>
	<item>
		<title>Database-Driven Navigation Bars Using Text and Images</title>
		<link>http://tc.eserver.org/20488.html</link>
		<guid>http://tc.eserver.org/20488.html</guid>
		<description>Okay, we&apos;ve all fiddled with NavBars. In fact, MM&apos;s built-in Navigation Bar Builder is pretty sweet for creating NavBars with onMouseOver and onMouseOut behaviors giving your site that professional look. But what if your site changes frequently? One option is to bag the images and stick with a database-driven NavBar that uses a repeat region. We&apos;ll look at that approach first. Then we will see how we can replace UltraDev&apos;s hardcoded NavBar image behaviors with database-driven links and images.</description>
	</item>
	<item>
		<title>Defining &apos;Value-Adding Work&apos; of In-House Information Development Groups</title>
		<link>http://tc.eserver.org/20294.html</link>
		<guid>http://tc.eserver.org/20294.html</guid>
		<description>Many in-house information development groups are redefining their role (or seeking to justify their existence) around the concept of &apos;value-adding work.&apos; But which tasks are value-adding? Finding an answer to this question is critical for the survival of information development groups. Unfortunately, there is no easy, &apos;one size fits all&apos; answer, because the response depends largely on your point of view. Thus, deciding what is and isn&apos;t value-adding may require technical communicators&#xD;to do more project-by-project task, audience, and media analysis than ever before.</description>
	</item>
	<item>
		<title>Evolving Client Content</title>
		<link>http://tc.eserver.org/20235.html</link>
		<guid>http://tc.eserver.org/20235.html</guid>
		<description>Content management systems are only as good as the content they manage. Garrity explores the care and feeding of low-budget clients who need high-quality content.</description>
	</item>
	<item>
		<title>Single Sourcing:  It&apos;s About People, Not Just Technology</title>
		<link>http://tc.eserver.org/19813.html</link>
		<guid>http://tc.eserver.org/19813.html</guid>
		<description>Cautions that failing to focus on the people in the organization may diminish the success of a single-sourcing initiative. Covers changes that need to occur in the organization to support a single-sourcing initiative and ways to address issues of change.</description>
	</item>
	<item>
		<title>Creating a Corporate Electronic Information Delivery Solution</title>
		<link>http://tc.eserver.org/19788.html</link>
		<guid>http://tc.eserver.org/19788.html</guid>
		<description>Tandem Computers Incorporated developed a new electronic information delivery system and changed internal publishing processes to achieve greater eficiency and customer satisfaction. We were able to move over 1,000 manuals and 11,000 pieces of support documentation along with education material from two different CD-ROM delivery products to one corporate viewer that supports publishing on both CD-ROM and the World Wide Web. The project included creating a new viewer using industry-standard components, creating new publishing tools, and establishing new corporate relationships and processes.</description>
	</item>
	<item>
		<title>Do-It-Yourself Single-Sourcing</title>
		<link>http://tc.eserver.org/19641.html</link>
		<guid>http://tc.eserver.org/19641.html</guid>
		<description>In recent years, countless articles and conference workshops have touted single sourcing as the Holy Grail of technical writing. Countless articles and conference workshops have also told us that XML is our means to achieving the Grail. However, in the absence of any off-the-shelf products that facilitate XML and single sourcing in our current work environments, I suspect that most people, particularly in smaller companies, believe that implementing XML is too technically daunting, too expensive, or both.</description>
	</item>
	<item>
		<title>Meet Me in RIO: Implementing Reusable Information Objects</title>
		<link>http://tc.eserver.org/19495.html</link>
		<guid>http://tc.eserver.org/19495.html</guid>
		<description>Reusable information objects and reusable learning objects are the building blocks of e-learning courseware and e-documentation. A strong business case can be&#xD;made for implementing a single-source content&#xD;repository for RIOs/RLOs to achieve reusability between&#xD;enterprise applications.&#xD;Keys to achieving reusability include: an effective metatagging&#xD;scheme, appropriate levels of granularity, and&#xD;adherence to standards such as the SCORM.</description>
	</item>
	<item>
		<title>Dynamic Content Management</title>
		<link>http://tc.eserver.org/19373.html</link>
		<guid>http://tc.eserver.org/19373.html</guid>
		<description>Until recently, technical communicators created static&#xD;content--content that is created in a specific way for a&#xD;specific purpose (e.g., user guides and help) and that&#xD;remains the same until the technical communicator&#xD;deliberately changes it. As single sourcing has made it&#xD;possible to write information once and use it many times,&#xD;technical communicators have begun to create static&#xD;customized content, which is designed to meet the&#xD;specific needs of the user, the materials to be developed&#xD;(such as user guides, reference guides, and training),&#xD;and the delivery media (paper or online). The content is&#xD;customized for a particular requirement at a particular&#xD;time but cannot be changed without being regenerated by&#xD;the author. Now, the ability to create dynamic content will change the way technical communicators envision, create, and distribute information.</description>
	</item>
	<item>
		<title>Post-Implementation - Most Important</title>
		<link>http://tc.eserver.org/19319.html</link>
		<guid>http://tc.eserver.org/19319.html</guid>
		<description> You would be forgiven for thinking that the lifespan of the typical usability project ends with final implementation and a product or website&apos;s release into the market. In one sense it does - the user-centred design process is over, and presumably the result is an easy-to-use product or site that is already yielding results. All well and good - but sometimes even the best interfaces cannot meet the changing requirements of the typical workplace. In this case, post-implementation user testing can pick up the difficulties that were not picked up first time around.&#xD;&#xD;At this point the client may quite rightly be wondering why these problems weren&apos;t spotted before deployment. The reason lies in the way in which the user has developed alongside the product. First impressions, whether favourable or not, may turn out to be misleading after an extended period of use.</description>
	</item>
	<item>
		<title>A Better Approach: Requirements-Focused CMS Selection</title>
		<link>http://tc.eserver.org/19155.html</link>
		<guid>http://tc.eserver.org/19155.html</guid>
		<description>Your organisation is unique, and as such, has a unique set of content management system (CMS) requirements.&#xD;&#xD;There is also no single &apos;perfect for everyone&apos; content management system. Each product has its own set of strengths and weaknesses, and distinctive design principles.&#xD;&#xD;Unfortunately, the selection process followed by many organisations doesn&apos;t recognise this, leading to the purchase of a CMS which does not match business needs.&#xD;&#xD;Selecting a CMS does not have to be a lottery. By following a requirements-focused methodology, instead of a features-driven approach, the right CMS can be identified, and the business risks minimised. </description>
	</item>
	<item>
		<title>A Consumer Survey of CMS Vendor Websites</title>
		<link>http://tc.eserver.org/19150.html</link>
		<guid>http://tc.eserver.org/19150.html</guid>
		<description>In March 2003, an online survey was conducted of consumer opinion about CMS vendor websites. This was extensively promoted through the CMS mailing lists, and on key CMS websites such as CMS Watch, the Intranet Focus and Step Two Designs sites.&#xD;&#xD;In total, 168 responses were made to this survey, representing consumers from across the globe, and in every type of organisation.&#xD;&#xD;This briefing provides a high-level summary of the results of the survey.</description>
	</item>
	<item>
		<title>A Content Management Project Presents Unique Challenges</title>
		<link>http://tc.eserver.org/19153.html</link>
		<guid>http://tc.eserver.org/19153.html</guid>
		<description>At a basic level, implementing a content management system (CMS) is like deploying any other large software package.&#xD;&#xD;Fundamental project management principles must be followed, along with best practice technical guidelines.&#xD;&#xD;Beyond this, however, a CMS project presents a number of unique challenges. These must be recognised and addressed for the project to be successful. </description>
	</item>
	<item>
		<title>The Importance of Content Management System Usability</title>
		<link>http://tc.eserver.org/19146.html</link>
		<guid>http://tc.eserver.org/19146.html</guid>
		<description>The rollout of a content management system (CMS) has the potential to impact on more users than any other system since e-mail.&#xD;&#xD;More crucially, the success of a CMS depends entirely on how much it is used, whether it is authors creating content, or users accessing the published site.&#xD;&#xD;It is these two challenges that place usability as a central issue to be raised and addressed. </description>
	</item>
	<item>
		<title>The Two Faces of Intranet Success</title>
		<link>http://tc.eserver.org/19149.html</link>
		<guid>http://tc.eserver.org/19149.html</guid>
		<description>There are two fundamental aspects that must be satisfied if an intranet is to succeed: the intranet must meet staff needs; sufficient content and functionality must be created to meet these needs.&#xD;&#xD;These are the &apos;two faces&apos; of the intranet, one looking towards staff and organisational needs, the other at the infrastructure and processes needed to meet it.</description>
	</item>
	<item>
		<title>Manual Labor</title>
		<link>http://tc.eserver.org/19032.html</link>
		<guid>http://tc.eserver.org/19032.html</guid>
		<description>Back when having a website was more important than having a sound business plan, Web content management systems were a must-have for large companies. IT managers bought into the idea that they needed an all-in-one system that would help them generate content, structure it, design it and publish it. But new research suggests these systems largely failed to live up to their promise.&#xD;&#xD;According to a recent report by Jupiter Research, 61 percent of companies that have deployed Web content management software still update their websites manually.</description>
	</item>
	<item>
		<title>Needle in a Haystack</title>
		<link>http://tc.eserver.org/19033.html</link>
		<guid>http://tc.eserver.org/19033.html</guid>
		<description>In most organizations, data is piling up by the minute: e-mails, names, addresses, transactions, you name it. As a result, finding what you need when you need it is becoming increasingly complicated, which is why more companies are deploying enterprise search tools. According to a recent report by Boston-based Yankee Group, 75 percent of businesses with more than 100 employees have some sort of enterprise search technology in place.&#xD;&#xD;The study also found that the bigger the organization, the more likely it is to invest in search technologies, as 91 percent of companies with more than $1 billion in annual revenue report having enterprise search capability. In 2001, a similar Yankee Group survey found that 63 percent of businesses employed search technology. In that year, enterprise search vendors generated $400 million in revenues. </description>
	</item>
	<item>
		<title>Putting Content in Context</title>
		<link>http://tc.eserver.org/19034.html</link>
		<guid>http://tc.eserver.org/19034.html</guid>
		<description>Digital asset management (DAM) software stores and organizes images, audio, video and other digital objects, making them easier to find, transform and reuse. And many companies are using DAM to provide a centralized way for employees and partners to locate and manipulate content-a big time-saver for all.</description>
	</item>
	<item>
		<title>Implementing Single Sourcing in Your Organization</title>
		<link>http://tc.eserver.org/18987.html</link>
		<guid>http://tc.eserver.org/18987.html</guid>
		<description>Single sourcing is more complex than buying a new software application. To ensure a successful migration, you must carefully understand the documentation development processes in your organization, what single sourcing is, and what software is available to facilitate it. Because you must change the way your organization creates and maintains documentation, you must sell your organization on the changes and their cost. Finally, you must develop training to help transition writers to your single sourcing methodology.</description>
	</item>
	<item>
		<title>Information Modeling</title>
		<link>http://tc.eserver.org/18985.html</link>
		<guid>http://tc.eserver.org/18985.html</guid>
		<description>Information models are a critical component of single-sourcing, enterprise content management, and dynamic content management. This session explains how to design information models, including information product models and element models. It also explains the role of metadata and how to effectively design it.</description>
	</item>
	<item>
		<title>Localization of Single-Source Content</title>
		<link>http://tc.eserver.org/18913.html</link>
		<guid>http://tc.eserver.org/18913.html</guid>
		<description>One of the key motivators of adopting a single-source&#xD;approach for documentation is the potential cost savings&#xD;available through the reduced cost of translation. By&#xD;consolidating multiple documents, version updates, and&#xD;similar products, translations may be leveraged across&#xD;components.&#xD;By creating single-source content with translation in&#xD;mind, authors are able to create documents that are easy&#xD;to localize, increase consistency, and reduce costs. The&#xD;article below provides a summary of the translation&#xD;benefits of single-sourcing and offers advice for designing a single-source strategy from a localization perspective.</description>
	</item>
	<item>
		<title>Selecting a Content-Management System</title>
		<link>http://tc.eserver.org/18896.html</link>
		<guid>http://tc.eserver.org/18896.html</guid>
		<description>Your output requirements will drive many of your decisions when selecting a content-management system. An abbreviated version of the checklist from JoAnn&#xD;Hackos’s book, Content Management for Dynamic&#xD;Delivery, follows to aid you in defining your output&#xD;requirements.</description>
	</item>
	<item>
		<title>SGML: More than &apos;Just Do It!&apos;</title>
		<link>http://tc.eserver.org/18903.html</link>
		<guid>http://tc.eserver.org/18903.html</guid>
		<description>The Technical Publications department of DSC Communications Corporation decided to use SGML as a method of information creation, storage, and management; obtained buy-in from management and appropriate personnel; selected and trained a team; created and implemented a project plan for an SGML prototype project.</description>
	</item>
	<item>
		<title>Single Source Tools: An Integrated Solution</title>
		<link>http://tc.eserver.org/18894.html</link>
		<guid>http://tc.eserver.org/18894.html</guid>
		<description>Tools are a key component for the success of single sourcing. Tools should be selected to support the information model and development processes. This session reviews the types of single&#xD;source tools (authoring, XML, content management, output, and&#xD;dynamic content engines) that are available to you today.&#xD;The session presentation will review the available tools&#xD;Note that the tools mentioned in this paper may change by the time of the presentation.</description>
	</item>
	<item>
		<title>Single Sourcing: Our First Year</title>
		<link>http://tc.eserver.org/18874.html</link>
		<guid>http://tc.eserver.org/18874.html</guid>
		<description>Single sourcing creates multiple documents from a single content file. Developing single-source content is an efficient way to produce documentation. This topic has stirred considerable interest among technical writers the last few years and more and more departments are adopting the process. The following experiences and advice, based upon our use of FrameMaker and WebWorks Publisher Professional, are meant to assist a documentation department that is about to begin a single-source process or is considering making this transition.</description>
	</item>
	<item>
		<title>What Every Technical Communicator Should Know About Metadata</title>
		<link>http://tc.eserver.org/18838.html</link>
		<guid>http://tc.eserver.org/18838.html</guid>
		<description>Technical Communicators who begin working with&#xD;content management systems, knowledge bases, portals,&#xD;data warehouses, or information retrieval systems&#xD;discover they are expected to know how to work with&#xD;metadata. Metadata is “data about data.” It can&#xD;describe data or content (databases, data modeling, data&#xD;access and reporting, data movement, data stewardship,&#xD;data quality);organizations (business rules, process&#xD;stewardship, data users, project management); content&#xD;management and information retrieval (document&#xD;properties, revision and change control, reference and&#xD;navigation, document standards); and business&#xD;intelligence (decision support, competitive intelligence).&#xD;Metadata management can positively impact productivity and the quality of web and documentation projects.</description>
	</item>
	<item>
		<title>Avoiding the Content Silo Trap™, Enterprise Content Management</title>
		<link>http://tc.eserver.org/18805.html</link>
		<guid>http://tc.eserver.org/18805.html</guid>
		<description>Organizations frequently fall into the content silo trap, multiple authors creating similar information, in many areas of the organization. Authors rarely share their information (they work in silos) or are even aware that this information already exists elsewhere in the organization. Technical communicators have been single sourcing for years, this session looks at how to move beyond technical publications to assist your organization with enterprise content management.&#xD;This session includes a case study from Eli Lilly.</description>
	</item>
	<item>
		<title>An End-to-End Multilingual Content Management System</title>
		<link>http://tc.eserver.org/18800.html</link>
		<guid>http://tc.eserver.org/18800.html</guid>
		<description>This article will not try to answer why there&apos;s no end-to-end content management solution that supports the whole process from single-source authoring to multilingual publishing. At least, it cannot be bought off-the-shelf. Only companies with the size of J.D.Edwards are able to integrate the various components. They will even find the resources and the necessary expertise to implement vital components that are not readily available on the market (e.g. multilingual terminology management system).</description>
	</item>
	<item>
		<title>Use and Abuse of Reusable Learning Objects</title>
		<link>http://tc.eserver.org/18779.html</link>
		<guid>http://tc.eserver.org/18779.html</guid>
		<description>The term Learning Object, first popularized by Wayne Hodgins in 1994 when he named the CedMA working group &apos;Learning Architectures, APIs and Learning Objects,&apos; has become the Holy Grail of content creation and aggregation in the computer-mediated learning field. The terms Learning Objects (LOs) and Reusable Learning Objects are frequently employed in uncritical ways, thereby reducing them to mere slogans. The serious lack of conceptual clarity and reflection is evident in the multitude of definitions and uses of LOs. The objectives of this paper are to assess current definitions of the term Learning Object, to articulate the foundational principles for developing a concept of LOs, and to provide a methodology and broad set of guidelines for creating LOs.</description>
	</item>
	<item>
		<title>From Web to Print</title>
		<link>http://tc.eserver.org/18388.html</link>
		<guid>http://tc.eserver.org/18388.html</guid>
		<description>The Web is WYSIWYG. What you see is what you get. What you see on the monitors and via the connections - and what you use for beta testing - is what your work will look like to all those who check out your URL. What&apos;s on your screen will be pretty close to what&apos;s on their screens.&#xD;&#xD;Print is a different matter altogether. Once your files leave your computer, there&apos;s a whole wonderful road they have to journey along to make it into print. You do everything you can to make sure they&apos;re ready for their adventure, but just as you&apos;re likely to forget your toothbrush or your favorite socks when you take a trip, your files often go to print missing a vital item. You can only hope that the thing you forgot about is easy to correct and not a big expensive mistake that blows your deadline and your budget. Getting your files through your service bureau (where your files are turned into negatives so that your negatives ultimately become the finished product) and to the printer is like taking up the gauntlet. Best case scenario, you&apos;ll be winded; worst case, you&apos;ll be pounded to a bloody pulp. I fear I&apos;m showing my bias toward the Web.</description>
	</item>
	<item>
		<title>Add Functionality to Quick, Easy Site Deployment</title>
		<link>http://tc.eserver.org/18330.html</link>
		<guid>http://tc.eserver.org/18330.html</guid>
		<description>More than a Web content management system, Octigon President James Smith calls Octane8 a deployment platform. What exactly can you deploy with Octane8? To name a few: public Internet sites, private intranet and extranet sites; sites for the group you&apos;ll be collaborating with for the next two weeks; sites with pages that sell; and sites with pages that inform.</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>
	<item>
		<title>Webworks Publisher Tutorial: Better Jumps to Topic Titles</title>
		<link>http://tc.eserver.org/18323.html</link>
		<guid>http://tc.eserver.org/18323.html</guid>
		<description>By default Webworks Publisher uses file names and paragraph numbers as hyperlink targets, e. g. &amp;lt;a href=&apos;filename.html#55555&apos;&amp;gt;. Most web browsers try to position the paragraph with the corresponding name anchor &amp;lt;a name=&apos;55555&apos;&amp;gt; at the top of the screen if possible. If you jump to the top of a scrollable topic, any content above the title line (e.g. navigation graphics) is hidden. There are a few easy countermeasures.</description>
	</item>
	<item>
		<title>WebWorks Publisher Tutorial: Useful Meta Tags</title>
		<link>http://tc.eserver.org/18324.html</link>
		<guid>http://tc.eserver.org/18324.html</guid>
		<description>If you are using Webworks Publisher to create HTML pages which will be published for the WWW, you may want to place additional useful meta tags in your pages to be found and indexed by search engines and thus be found by interested persons.</description>
	</item>
	<item>
		<title>Capturing Feedback: Building a Tighter Net</title>
		<link>http://tc.eserver.org/15097.html</link>
		<guid>http://tc.eserver.org/15097.html</guid>
		<description>Describes how to use Microsoft FrontPage and Access to build a system for organizing and retrieving feedback from reviewers. The article is intended for those with some experience with Web and database design.</description>
	</item>
	<item>
		<title>Managing and Delivering Your Content as Data</title>
		<link>http://tc.eserver.org/14604.html</link>
		<guid>http://tc.eserver.org/14604.html</guid>
		<description>Houser describes several options for organizations interested in data-oriented publishing--the delivery of discrete, independent pieces of information that can be selected, manipulated, and presented to meet the needs of different audiences with different characteristics and different goals.</description>
	</item>
	<item>
		<title>Fuzzy Matching as a Retrieval-Enabling Technique for Digital Libraries</title>
		<link>http://tc.eserver.org/14593.html</link>
		<guid>http://tc.eserver.org/14593.html</guid>
		<description>This paper advocates an often-neglected search-support technique, approximate or &apos;fuzzy&apos; matching of user search terms. When properly deployed, fuzzy matching can significantly enhance the benefits of other, more common approaches to end-user answer retrieval from online reference collections. We compare crude with more sophisticated approximation techniques to explain how astute fuzzy-match software can convert many different near-miss situations (such as those involving faulty prefixes or suffixes, character misplacement, nonstandard word stems, or unanticipated redescription of concepts) into more adequate results. We also suggest practical ways to overcome fuzzy matching&apos;s own major drawbacks (namely, problems with search speed, search imprecision, and misinterpretation of search results). The resulting analysis clarifies how to deploy fuzzy matching for maximum effectiveness. We conclude that appropriate fuzzy matching enables more frequent, more flexible search success than do ordinary retrieval-improvement techniques used without it.</description>
	</item>
	<item>
		<title>“Hand It To Them On A Silver Platter: Meeting Researchers Needs In The Electronic Age”</title>
		<link>http://tc.eserver.org/14584.html</link>
		<guid>http://tc.eserver.org/14584.html</guid>
		<description>This paper describes the Electronic Resource Library (ERL) at&#xD;http://plutonium-erl.actx.edu. This is a web-based, subject-oriented digital&#xD;library on the topic of plutonium and its ancillary disciplines. Previous research&#xD;analyzing differences in the information-seeking behavior of scientists and&#xD;engineers is reviewed and lessons learned applied to this digital library model.&#xD;Special consideration has been given to recommendations in the SATCOM&#xD;report from the National Academy of Sciences/National Academy of&#xD;Engineering Committee on Scientific and Technical Communication. This&#xD;report strongly advocated the development of “specialized need-groupservices”&#xD;to support the work of the engineer and practitioner.</description>
	</item>
	<item>
		<title>Designing Wearable Performance Support: Insights from the Early Literature</title>
		<link>http://tc.eserver.org/14246.html</link>
		<guid>http://tc.eserver.org/14246.html</guid>
		<description>According to Gery (1991), an electronic performance support system (EPSS) is an electronic environment available to and easily accessible by employees that is structured to provide online access to all information to permit them to do their jobs with minimal intervention by others. Why do we assume that this support must be provided on a computer? If effective performance support must be &apos;available&apos; and &apos;easily accessible,&apos; how can designers provide support to people whose jobs require mobility? Such jobs include (but certainly are not limited to) supervising a manufacturing operation, inspecting foods, and repairing equipment. A designer for any EPSS being developed to support jobs such as these would have to take the employees&apos; mobility into account.</description>
	</item>
	<item>
		<title>Choices and Challenges: Considerations for Designing Electronic Performance Support Systems</title>
		<link>http://tc.eserver.org/14225.html</link>
		<guid>http://tc.eserver.org/14225.html</guid>
		<description>Introduces the breadth of decision-making required in EPSS design. Explores choices and challenges facing designers in the design process, performance cycle, technology constraints, use of storytelling techniques, evaluation, and success factors.</description>
	</item>
	<item>
		<title>CoRR: A Computing Research Repository</title>
		<link>http://tc.eserver.org/14219.html</link>
		<guid>http://tc.eserver.org/14219.html</guid>
		<description>This paper describes the decisions by which the Association for Computing Machinery integrated good features from the Los Alamos e-print (physics) archive and from Cornell University&apos;s Networked Computer Science Technical Reference Library to form their own open, permanent, online “computing research repository” (CoRR). Submitted papers are not refereed and anyone can browse and extract CoRR material for free, so CoRR&apos;s eventual success could revolutionize computer science publishing. But several serious challenges remain: some journals forbid online preprints, the CoRR user interface is cumbersome, submissions are only self-indexed, (no professional library staff manages the archive) and long-term funding is uncertain. </description>
	</item>
	<item>
		<title>Integrating Content Management with Portals: Meeting Enterprise Information Needs</title>
		<link>http://tc.eserver.org/14175.html</link>
		<guid>http://tc.eserver.org/14175.html</guid>
		<description>Effective communication is a top priority for most businesses. To help create, manage, and access information that is used to conduct e-business, technologies such as content management (CM) and enterprise information portals (EIP) are dominating IT and CIO discussions. We will review how these rapidly evolving technologies come together to provide benefits for enterprise implementers.&#xD;Given the historical deployment of these technologies, many associate the&#xD;application of content management solutions to externally facing sites, serving&#xD;transactional e-business needs; and the application of portals to internally facing&#xD;sites for general employee access to a wide range of information sources and&#xD;applications. However, both technologies can provide support for the complete&#xD;information lifecycle, from information creation to management to delivery.</description>
	</item>
	<item>
		<title>Web Content Management: Market Overview </title>
		<link>http://tc.eserver.org/14174.html</link>
		<guid>http://tc.eserver.org/14174.html</guid>
		<description>The content management market comprises systems designed specifically to drive Web sites, including capacity planning, site design/layout, look/feel navigation, content development, production, content delivery, session tracking, and site evolution. The core focus of these products is empowering business users to create Web site content, providing processes to ensure the approval of all content and maintain its consistency/life-cycle management (B2C, B2B, B2E). WCM does not extend to the display, personalization, or associated transactions. This category expands to include Web developers, Webmasters, and site creators as well as business users. Increasingly, overlap exists with portal and other unstructured content categories (e.g., software configuration management, digital asset management, document management).</description>
	</item>
	<item>
		<title>Words Drive Action: An Interview with Gerry McGovern</title>
		<link>http://tc.eserver.org/14196.html</link>
		<guid>http://tc.eserver.org/14196.html</guid>
		<description>Gerry McGovern is a world-renowned content-management expert and author of the books, &apos;Content Critical&apos; and &apos;The Web Content Style Guide&apos;. User Interface Engineering&apos;s Christine Perfetti and Josh Porter recently talked with Gerry about the importance of an editorial perspective in a web development process. Here is what Gerry had to say about his experiences.</description>
	</item>
	<item>
		<title>Content Repurposing with FrameMaker+SGML and XML</title>
		<link>http://tc.eserver.org/14082.html</link>
		<guid>http://tc.eserver.org/14082.html</guid>
		<description>We see content repurposing as taking marked-up content and automatically transforming it for presentation in multiple applications.&#xD;For example, one of our clients asked us to help them convert existing Word documentation&#xD;into structured FrameMaker+SGML files, and then export it to a well-formed and&#xD;valid XML instance. The structured FrameMaker+SGML documents would be used to&#xD;create user manuals (both print and PDF), and the XML instance would be used for online&#xD;documentation on PDAs or cell phones.&#xD;Portions of the content would be applicable for only the printed documents, while other&#xD;potions of the content would be used only for online display.</description>
	</item>
	<item>
		<title>An Introduction to Single-Sourcing</title>
		<link>http://tc.eserver.org/14084.html</link>
		<guid>http://tc.eserver.org/14084.html</guid>
		<description>A brief, high-level introduction to single-sourcing.</description>
	</item>
	<item>
		<title>The Joy of Single-Sourcing</title>
		<link>http://tc.eserver.org/14079.html</link>
		<guid>http://tc.eserver.org/14079.html</guid>
		<description>At MYOB® (Mind Your Own Business) Australia, we have just finished our first single-sourcing project using mif2go to convert FrameMaker source files to HTML Help *.chm files. These files are also the source of our printed user guide and the hyperlinked PDF of the user guide placed on the distribution CD.&#xD;&#xD;There was considerable once-off pain setting up conversion templates (including CSS files) and conversion options but our next project will be much faster. The converted files do not require any hand tweaking -- we just hand over to the release people to put the *.chm file on the installer CD.&#xD;&#xD;Our testing and support people are rapt, and consider the new help far better than the old help. It has a navigation pane with Contents, Index, Search, and Favorites tabs, a toolbar with Hide [navigation pane], Prev, Next, Back, Forward, Print, Options, and Welcome (custom Home) buttons. An outsider would have no inkling that the help was converted from FrameMaker source files as the appearance is completely different from the printed book and hyperlinked PDF. You, too, can single-source successfully provided you plan beforehand and your team understands the process.</description>
	</item>
	<item>
		<title>Making a Business Case for Single Sourcing</title>
		<link>http://tc.eserver.org/14081.html</link>
		<guid>http://tc.eserver.org/14081.html</guid>
		<description>As we learned in the February 2001 issue of Best Practices, in JoAnn Hackos&apos; review of the book, &lt;i&gt;The Balanced Scorecard,&lt;/i&gt; selling innovative ideas to upper management is important. The Balanced Scorecard approach includes a customer perspective, an internal-business-process perspective, and a learning and growth perspective, in addition to the financial perspective. A solid and balanced business case allows you to gain management support and reach your goal.</description>
	</item>
	<item>
		<title>Managing Enterprise Content: A Unified Content Strategy</title>
		<link>http://tc.eserver.org/13820.html</link>
		<guid>http://tc.eserver.org/13820.html</guid>
		<description>Today&apos;s businesses are overwhelmed with the need to create more content, more quickly, customized for more customers and for more media than ever before. Combine this with decreasing resources, time, and budgets and you have a stressful situation for organizations and their content creators. To reduce the costs of creating, managing, and distributing content and to ensure content effectively supports your organizational and customer needs, organizations can benefit from a unified content strategy. A unified content strategy is a repeatable method of identifying all content requirements up front, creating consistently structured content for reuse, managing that content in a definitive source, and assembling content on demand to meet your customers&apos; needs.</description>
	</item>
	<item>
		<title>Web Content Meets Records Management</title>
		<link>http://tc.eserver.org/13821.html</link>
		<guid>http://tc.eserver.org/13821.html</guid>
		<description>While the Web has forever changed the way we gather information, communicate and conduct business, it&apos;s the highly dynamic and personalized Web content and the transactions performed on the Web that present records managers with the greatest challenge.</description>
	</item>
	<item>
		<title>Rapid Web Development: How to Create Flexible Sites Quickly Using Standards Like CSS and XHTML</title>
		<link>http://tc.eserver.org/13656.html</link>
		<guid>http://tc.eserver.org/13656.html</guid>
		<description>What do you do when you need to have a Web site done &apos;yesterday&apos;? This article answers that question, showing you how to create sites quickly and flexibly using Web standards like cascading style sheets (CSS), structural HTML, and server-side includes. It contains examples that demonstrate how rapid Web development not only streamlines the process, but also makes updating easier.</description>
	</item>
	<item>
		<title>Smarter Content Publishing: Building A Semantic Website to Increase the Efficiency and Usability of Publishing Systems</title>
		<link>http://tc.eserver.org/13660.html</link>
		<guid>http://tc.eserver.org/13660.html</guid>
		<description>The web is not print. The need to create hypertext within pages requires more control over documents. Another is that web pages can also be applications, so access to the &apos;guts&apos; of the page is needed to insert programming code. And ideally, we would like to separate presentation from content, enabling us to format the content in different ways for different purposes. How can we achieve all this with the efficiency and usability we&apos;ve come to expect of other publishing tools?</description>
	</item>
	<item>
		<title>Moving from Information Transfer to Knowledge Creation: A New Value Proposition for Technical Communicators</title>
		<link>http://tc.eserver.org/13602.html</link>
		<guid>http://tc.eserver.org/13602.html</guid>
		<description>&apos;What do technical communicators do?&apos; asks the ambitious question on the Society for Technical Communication&apos;s FAQ Web page (STC 2001). The answer lists typical job titles for technical communicators and then says, &apos;All these professionals take technical information and make it understandable to those that need it.&apos; This description is consistent with the way that many technical communicators describe their role, that of transferring information from those who have it (subject matter experts or SMEs) to those who need it, and they define the value of the technical communicator as packaging that information to be more accessible and more readily understood by the user. This article first reviews the current literature that addresses the value of the technical communicator. Whereas those discussions focus on what is delivered to the user (reader), this article examines the value the technical communicator adds by creating organization (internal) knowledge. The article then examines the philosophical underpinnings that support any discussion of knowledge and defines the role of technical communicators as creators of knowledge. Finally, it offers an expanded value proposition for technical communicators and examines its practical implications.</description>
	</item>
	<item>
		<title>Manage Your Content with PHP</title>
		<link>http://tc.eserver.org/13601.html</link>
		<guid>http://tc.eserver.org/13601.html</guid>
		<description>In this article we&apos;ll build a simple, template-driven site that separates style, content, and structure in your website. We&apos;ll create a cross-browser stylesheet switcher that remembers the user&apos;s preferences, touching on PHP variables, cookies, if statements, and including pages with require_once.</description>
	</item>
	<item>
		<title>Creating An Information Model</title>
		<link>http://tc.eserver.org/13591.html</link>
		<guid>http://tc.eserver.org/13591.html</guid>
		<description>An Information Model provides the framework for organizing your content so that it can be delivered and reused in a variety of innovative ways. Once you have created an Information Model for your content repository, you will be able to label information in ways that will enhance search and retrieval, making it possible for authors and users to find the information resources they need quickly and easily.</description>
	</item>
	<item>
		<title>Single-Sourcing with FrameMaker</title>
		<link>http://tc.eserver.org/13588.html</link>
		<guid>http://tc.eserver.org/13588.html</guid>
		<description>As a technical writer, you may be exploring single-sourcing--producing multiple document outputs from a single information source--as a possible option for easing document development and production. Although solutions such as databases, SGML, and XML are available that can enable you to reuse information to produce multiple outputs, single-sourcing doesn&apos;t have to involve such complex solutions, expenses, and learning curves. Instead, if your single-sourcing needs are relatively simple, you can effectively single-source using a tool that technical writers commonly have available: FrameMaker.</description>
	</item>
	<item>
		<title>Beyond the Buzzword: Single Sourcing</title>
		<link>http://tc.eserver.org/13552.html</link>
		<guid>http://tc.eserver.org/13552.html</guid>
		<description>Single sourcing, which has been a buzzword in technical communication for several years, is now emerging as a practical, efficient, and cost-effective method for creating multiple deliverables. You&#xD;might want to consider single sourcing if&#xD;you have some documentation projects&#xD;that repeat, if not every one of your projects&#xD;is a one-off, if you reuse some of&#xD;your content, and if your budget planning&#xD;includes more than just the very&#xD;next project.</description>
	</item>
	<item>
		<title>Simple Content Management</title>
		<link>http://tc.eserver.org/13540.html</link>
		<guid>http://tc.eserver.org/13540.html</guid>
		<description>DON’T BE FOOLED by the title: this article covers the implementation of a complete, expandable, client-side content management system using REBOL. This system makes it easy for any website operator, regardless of experience, to update site content while keeping markup valid and consistent and ensuring that links stay pertinent. Why another CMS? I’m not a fan of the client-side content management provided by FrontPage or Dreamweaver, and server-based systems rely on server OS and software and are vulnerable to the restrictions of hosting packages. This CMS will work on any desktop system.</description>
	</item>
	<item>
		<title>Content Management Systems and the Single Web Designer</title>
		<link>http://tc.eserver.org/13359.html</link>
		<guid>http://tc.eserver.org/13359.html</guid>
		<description>Content Management is the next step in separating structure from design. What began with Cascading Style Sheets and was furthered by XML, is exploding with the CM environment, where billions were spent last year and more billions are expected to be spent in the years ahead.&#xD;&#xD;CM Systems come in many shapes: They can be huge or small, simple or very complex. They range from the very expensive (almost $300,000 for enterprise–wide systems like Vignette or Interwoven and $43,000 per server processor for Microsoft’s CMS to almost free (less than $1,000 for Manila and nothing for Zope).&#xD;&#xD;But they are all based on the same idea: CM allows designers to focus on design by building templates. Subject experts build content in a separate environment. The server takes the content, inserts it into the correct template and sends it all, neatly wrapped up, to end users.</description>
	</item>
	<item>
		<title>The End of Homemade Websites</title>
		<link>http://tc.eserver.org/13355.html</link>
		<guid>http://tc.eserver.org/13355.html</guid>
		<description>Web services will free individual site designers from having to program and design common features. This will decrease business costs, increase usability, and let designers focus on and improve features that are unique to each site.</description>
	</item>
	<item>
		<title>Document (re)Presentation: Object-orientation, Visual Language, and XML</title>
		<link>http://tc.eserver.org/10423.html</link>
		<guid>http://tc.eserver.org/10423.html</guid>
		<description>This article demonstrates how the combination of object-orientation and Horn&apos;s notions of visual language morphology, syntax, semantics, and pragmatics may be used to analyze and describe the mapping of marked-up XML files onto user documents. The article also raises the question of whether—or to what extent—the coupling of object-orientation and visual language might be exploited more directly for design purposes in a document production paradigm based on XML. </description>
	</item>
	<item>
		<title>Tips for Online Content Businesses in 2001</title>
		<link>http://tc.eserver.org/10240.html</link>
		<guid>http://tc.eserver.org/10240.html</guid>
		<description>The online content industry has experienced its first real shakeout. Good! It toppled many high-profile online content venues and left others reeling, scrambling, and retrenching -- but it was absolutely necessary. 2001 should be an especially exciting and interesting year for the online content industry. The need for quality online content continues to expand with the Internet&apos;s popularity. However, the online content industry doesn&apos;t work like traditional media. Also, it has become painfully obvious that you really must have a solid business model to succeed in this field. Time to stop clinging to outdated assumptions about media, and to take a hard look at how online media really works. As food for thought, here are Amy&apos;s top tips for online content businesses in 2001.</description>
	</item>
</channel>
</rss>