Creating Single-Sourced Information Products  

Until recently, single sourcing has been limited to the process of putting identical information into multiple information products. However, the results of a singlesourced approach need not be identical. You can customize the outputs to contain only the information that is appropriate for the specific situation. This presentation provides a high-level overview to the advantages of single sourcing and how to implement and maintain such a solution.

Stevens, Dawn M. STC Proceedings (1999). Articles>Content Management>Single Sourcing

Curing Publishing Woes with a Content Management System  

Mescan's article helps technical communication managers determine which content management solutions are best for their particular goals and problems.

Mescan, Suzanne. Intercom (2004). Articles>Content Management>Single Sourcing

Customizing the Appearance of Your Manual, Help System, and HTML Help System  

Doc-To-Help gives Help authors complete control over the look, feel, and content of a project's printed manual, Windows Help system, HTML files, and HTML Help system. Maintaining different content is controlled using Doc-To-Help's conditional text feature, which allows authors to mark content for print-only, online-only, WinHelp-only, and so on. In this article we discuss how you control the appearance of the printed manuals and Help using Word templates, and HTML output using cascading style.

ComponentOne (1999). Articles>Content Management>Single Sourcing>Documentation

Definition of Information Management Terms

There is considerable confusion in the marketplace regarding the definition of various information management terms. The scope and role of specific information systems is particularly blurry, in part caused by the lack of consensus between vendors. With the aim of lessening this confusion, this briefing provides an at-a-glance definition of terms for a range of information systems.

Robertson, James. Step Two. Articles>Content Management>Single Sourcing>Glossary

Designing an Information Set for Single-Sourcing  

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 which many outputs may be created. Designing an information set is different from designing a document. Greater structure is required, and that structure must be available to the process that creates information products as output, not simply to the reader. A good information set design involves creating a data model, mapping information relationships, and defining patterns of change.

Baker, Mark. STC Proceedings (1999). Design>Content Management>Single Sourcing

Designing Effective Single Source Materials  

People often have to create documents for different audiences and for different media, (e.g. web, Help, training). However, timelines and budgets for developing information are often tight. This means we have to find more efficient ways to develop information. One way is to consider single sourcing information for multiple users and media. While single sourcing does take more up-front planning, it can significantly decrease costs and development times once implemented.

Rockley, Ann. STC Proceedings (2000). Presentations>Documentation>Single Sourcing

Designing for Single Source  

“Single source” has come to mean many things to many different people. The basic distinctions are two: (1) distributing the same content in multiple formats and (2) distributing complementary content in the most appropriate medium. The two concepts are not mutually exclusive, i.e., you may have an information strategy that encompasses both ideas. Each methodology has its own advantages, suitability, and requirements. Distributing complementary content in the most appropriate medium requires research and planning, and often results in more effective documentation.

Florsheim, Stewart J. STC Proceedings (2000). Presentations>Information Design>Single Sourcing

Designing Single Source Materials  

Timelines for developing documentation are getting shorter and budgets are getting smaller. This means that we have to find more efficient ways of developing documentation. One way is to consider single-sourcing your information for multiple media (paper, online), multiple types of documentation (user documentation, Help, training), multiple users and reuse of information for multiple products. While this process takes a lot of up-front planning it can significantly decrease your costs and development times. This session looks at the process for designing and creating single-source materials for multiple media, users, or types of documentation.

Rockley, Ann and JoAnn T. Hackos. STC Proceedings (1999). Presentations>Content Management>Single Sourcing

Developing a Content-Management Strategy: Implications in a Multi-Language Environment  

Why we went to a single-source CMS and how we went about it.

Douma, Barbara. ComTech Services (2001). Articles>Content Management>Single Sourcing>Case Studies

Developing a Database Publishing System: A Demonstration  

We developed a database publishing system that uses raw data from a database and produces camera ready copy using Microsoft Access, FrameMaker, and Brio Publish. This type of project requires a project plan that defines the scope of the project, a complete understanding of the various relationships in the database, selection of the right tools for the task, and a sensitivity to the needs of the users who face dramatic change in their environment. This demonstration focuses on all aspects of this effort.

Cantoni, Georgina C. and Judith L. 'Judy' Glick-Smith. STC Proceedings (1995). Articles>Content Management>Single Sourcing>Microsoft Access

Developing a Single-Sourced Online Help System    

The definition of single sourcing continues to broaden in scope since its first mention in The Society of Technical Communication’s 46th Annual Conference publication. As a result, it is becoming increasingly difficult for technical communicators to understand what single source means and, more importantly, choose a definition of single sourcing that correlates with their specific task. One “type” of single sourcing involves reusing information for multiple products. Several developers at IBM have produced a single-source online help system. Unlike other single-sourcing methods that require a significant investment and a high degree of technical experience, these methods are inexpensive and require a moderate, yet creative, technical aptitude.

Vicek, Keith, Phil Menzies and Andre Evans. STC Proceedings (2002). Design>Documentation>Single Sourcing>Online

Developing and Maintaining a Large Document for Publication in Multiple Media  

This paper outlines the development of the Software Technology Reference Guide—a 500-page directory of software technologies— from the planning phase to its publication in both hard copy and HTML. It explores the problems of coordinating multiple, remotely located authors; producing frequent drafts when material is changing rapidly; managing a large documentation project; maintaining a source document for publication in multiple media; and handling the conversion of a complex hard-copy document to a usable online document.

Brune, Kimberly. STC Proceedings (1998). Articles>Content Management>Single Sourcing

Developing Information for Multiple Formats: You Can Get There from Here  

This paper describes the experiences of SAS Institute Inc. in developing single-source software documentation for presentation in multiple formats. The project is an ongoing team effort from all areas of the Publications Division. Our main goal is to develop online and hardcopy reference documentation. Toward this end, we set goals of using single-source files, reusing information, and tracking all information chunks and the relationships among them. To accomplish these goals we had to make decisions about the tools we are going to use, what information we are going to include, how we will design and present the modular information, linking and indexing strategies, and testing. This paper discusses the choices we made in light of our goals.

Moell, Patricia G. and Helen F. Weeks. STC Proceedings (1996). Articles>Content Management>Single Sourcing

Device Indepenence: Single Sourcing's Other Side  

Considers the possible ramifications for technical communicators of device-independent publishing.

Perlin, Neil E. Intercom (2005). Articles>Content Management>Single Sourcing

Distributed Workgroups Employing Single-Sourcing Techniques Around the Globe  

Single sourcing, which is increasingly used at the technical writer's workplace, has now reached the classroom of Technical Communication programs. This paper examines the impact of working on an XML-based single-sourcing solution on a geographically diverse graduate student team whose partners were all singlesourcing novices. It shows that managing communication within the virtual team is superordinate to managing the publication process. The paper discusses best-practice strategies for transient start-up publication teams, which rely solely on online communication, pointing to the differences between teams in the classroom and in business organizations.

Kaempf, Charlotte. STC Proceedings (2003). Articles>Content Management>Single Sourcing

Do-It-Yourself Single-Sourcing  

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.

Wersan, Fred. Intercom (2003). Design>Content Management>Single Sourcing

Does Being Technical Matter? XML, Single Source, and Technical Communication    

XML is a recent Web design language that will enable technical communicators to produce documentation that can reuse information and present it across multiple types of media for diverse audiences. However, little is understood about how XML will impact technical communication in terms of theory, academic research, and pedagogy. In this article, I argue that XML requires more interdisciplinary approaches toward the teaching and research of technical communication, particularly with respect to the integration of technical and rhetorical knowledge.

Sapienza, Filipp. Journal of Technical Writing and Communication (2002). Articles>Technology>Single Sourcing>XML

Dynamic Content Management  

Until recently, technical communicators created static content--content that is created in a specific way for a specific purpose (e.g., user guides and help) and that remains the same until the technical communicator deliberately changes it. As single sourcing has made it possible to write information once and use it many times, technical communicators have begun to create static customized content, which is designed to meet the specific needs of the user, the materials to be developed (such as user guides, reference guides, and training), and the delivery media (paper or online). The content is customized for a particular requirement at a particular time but cannot be changed without being regenerated by the author. Now, the ability to create dynamic content will change the way technical communicators envision, create, and distribute information.

Rockley, Ann. STC Proceedings (2002). Design>Content Management>Single Sourcing>Web Design

Dynamic Content Management  

Introduces dynamic content, a method of single sourcing that 'meets individual users' needs by assembling a series of information objects in response to the userís requests or requirements.' She walks readers through a mock project involving the creation and delivery of dynamic content.

Rockley, Ann. Intercom (2001). Articles>Content Management>Single Sourcing

E-Learning, Single Sourcing and SCORM  

E-learning is a highly effective way of providing training to widely dispersed audiences. Single sourcing (information reuse) provides the facility to create and store reusable content from a single source, and delivers that content to multi-channel information products for learners. SCORM is the Sharable Content Object Reference Model; it’s an initiative of the ADL (Advanced Distributed Learning Network). This session provides an understanding of how you can create effective e-learning materials using single sourcing or SCORM.

Rockley, Ann and Steve Manning. STC Proceedings (2002). Articles>Education>Single Sourcing>Online

Echoes from the Past: DITA, Help, Single-Sourcing Tools — Looking from the 60s to Today

The historian of technical communications, R. John Brockmann, researched efforts to document products going back centuries. He finds that some of today’s hottest new documentation ideas were present in the work of those creating, documenting, and selling the technology of manufacturing just after the revolutionary war.

Ng, Daniel. I'd Rather Be Writing (2008). Articles>Content Management>Single Sourcing>History

Editing in a Single-Source Environment  

The trend in the technical documentation community is toward single-sourcing: reusing common bits of information. This paper examines the role of the editor in this process, and the effect it has on traditional editorial practices.

Gelb, Janice. STC Proceedings (2001). Presentations>Editing>Single Sourcing

Editing Single-Sourced Projects

This article does not address the (important) questions of when a single-sourcing methodology is a good solution to an information delivery problem ('good' here meaning saving time and money while maintaining or improving the quality of the resulting deliverables). Instead, I'm looking only at the editor's involvement in the project.

Hollis Weber, Jean. Technical Editors Eyrie (2002). Articles>Editing>Single Sourcing

Eliminating the END GAME from Electronic Deliverables

While executive management may sometimes believe that anyone can write and that a technical writer's job is to "Just Publish It", it may be time for technical writers to look at what they can do to improve the "end game" process, which Porter describes as "All the steps needed to create the desired output format – HTML, PDF, online help system, etc. – from the source content." By taking a closer look at the publishing process, without regard to content, technical communicators may discover ways they can streamline the steps it takes to get content published and ready for the end consumer.

Porter, Alan J. Writing Assistance (2005). Articles>Content Management>Single Sourcing>Online