Repurposing Content for Multichannel Publishing (Single Sourcing)

It all comes down to managing and reusing source. Recycling content (chapters, graphics, etc.) is not new. What is new here is the common set of back-end structure in XML form and the fact that more than one set of tools — including small, mission critical custom tools — are explicitly focused on the specific needs of a given project. Reusing and repurposing content is all about improving efficiency: automating, accelerating, and merging applications, systems, and processes. In a multichannel publishing environment, it is critical that content development — source development — and its management are as efficient as possible.

Fraley, Liz. Tech Writer Voices (2008). Articles>Content Management>Single Sourcing

Does Single Sourcing Content Work?

One of the more popular posts on this blog is titled DITA is not the answer and, whilst things are certainly moving forward, it’s a little sad that it is still valid. A recent comment on that post suggested that it’s not just DITA that is lacking, it’s the working realities of single source that is flawed.

McLean, Gordon. One Man Writes (2009). Articles>Content Management>Single Sourcing>DITA

Anticipating the Impact of Content Convergence  

The nature of content has been undergoing a profound shift in the past several years, beginning with single-sourcing efforts and continues as the need for portable content increases. The portability of content is not a manufactured need, but an extension of the trend to create, manage and deliver content in more efficient ways. In turn, this shift affects content development and delivery, particularly localization, which feels the impact of source-language changes exponentially.

Bailie, Rahel Anne. Multilingual (2009). Articles>Content Management>Single Sourcing>Localization

DITA: The Mechanics of a Single-Sourcing Project

The Darwin Information Typing Architecture (DITA) is an XML-based, end-to-end architecture for authoring, producing, and delivering technical information. This paper describes how DITA-based documentation was implemented at CEDROM-SNi, one of Canada's leading on-line news content aggregators. The project delivers documentation as diverse as user training materials and Web Services reference guides targeted to programmers. We focus on the benefits, how tos, and lessons learned. Technical documentation has its own unique challenges. Its deliverables range from simple reference guides and educational material to complex, multilingual procedure manuals. Critical success factors of a documentation project are numerous and diverse – usability, deadlines, cost, language, delivery media (paper, online) – all of which have their own purpose and challenges. This paper discusses these issues and provides a framework for future DITA projects.

Baril, France. IDEAlliance (2004). Articles>Content Management>Single Sourcing>DITA

A Publisher's Journey to Single Source Publishing: A Case Study

We will cover the journey taken by J. J. Keller & Associates, Inc, a safety and regulatory compliance publisher, as they transitioned to an XML-based, single source publishing environment.

Jung, Jennifer and Mark Jacobson. XML 2006 (2006). Articles>Content Management>Single Sourcing>Case Studies

Pick a Card

There are obvious benefits to single sourcing, the ones that roll off the tongue the minute single source is mentioned: multi-format publishing, consistency of information, quicker updates of common content, lowering translation costs and so on. But beyond all those, what else is there? In this guest blog post, Gordon McLean discusses just that.

McLean, Gordon. DMN Communications (2009). Articles>Content Management>Single Sourcing>Documentation

Understanding the Value of Modular Content Reuse by Examining User-Generated Music Mashups

In the field of technical communication, practitioners are being challenged to adapt to a completely new approach to creating documentation and user-assistance materials. In this rapidly-changing arena, traditional content production practices are being replaced with modular, topic-based content production practices that allow organizations to recombine content elements—often automatically or on-demand—into new, derivative products.

Content Wrangler, The (2009). Articles>Content Management>Single Sourcing>Audio

Wikis and the Holy Grail of Content Independence

The concept of having control over your help content, to update it at any time, is what I’m calling content independence. Establishing content independence in your publishing environment may be a battle that can take years. For example, at a previous job, it took five years to finally convince architecture that we needed and deserved our own independent folder on a production server. In my current situation, I’ve pursued publishing routes in infrastructure that would enable on-the-fly updating, but for two years in a row I’ve come up empty-handed. With wikis, I think I’ve finally found the holy grail of content independence.

Johnson, Tom H. I'd Rather Be Writing (2009). Articles>Content Management>Single Sourcing>Wikis

The Myth of Single-Source Authoring 

Single-source publishing is a zombie idea that revives itself periodically and refuses to stay dead. Its zombie supporters chant its purported benefits as a “write once, publish to many” promise and ploddingly follow it as their ultimate goal for mechanized authoring and machine translation. As an object-oriented writing methodology, it is as human as present-day robot technology—good only for conveyor belt assembly or specialized tasks, and always very expensive to implement. Single-source publishing lacks purpose in today’s world of information turnover and the dynamic nature of the Web 2.0 moving to Web 3.0 landscape.

Hiatt, Michael. Mashstream (2009). Articles>Content Management>Single Sourcing>Writing