Where Source Development Meets Documentation or, Efficiency is in the Tools

Presentation to CMS/DITA NA 2005

The Desktop Publishing boom of the mid-80s changed the face of industry by removing the split between content and layout. On the small scale, the desktop publishing revolution was a positive change. This change was not free: The long term cost of 80s-style desktop publishing approach to document creation is that the resulting documents are by and large isolated from the larger pool of documents and the information used to create them.

Recycling content is not a new concept. What is new here is the common back-end structure in XML form and the fact that more than one set of tools, including small, mission-critical custom tools that are explicitly focused on the specific needs of a given project. There is no longer any need for one tool to address all of the needs of every company that purchases a license. Instead we have a community of tools that is easy to expand or customize without long term lock in or breaking of the model.

With only a small amount of custom tools, Juniper Networks has managed to do convert documents to multiple formats from one initial set of XML source documents and a single publishing workflow using PTC’s Arbortext Epic Editor and E3 Publishing Server. These tools have included post-processing add-ons to create .PDB and .LIT binary files and source files that are aggregated directly into the software source code for their proprietary routing platforms.

Special attention is given to specifics of the Juniper Networks implementation.

Presented by: Liz Fraley, Single-Sourcing Solutions, Inc.

Presented at: 10th Annual Arbortext User Group International Conference (AUGI 2005)

Presentation Materials:

Note: Arbortext was purchased by PTC in 2005

 

Branched Libraries and Rapid Release Single-Source Environment Implementation

“Branched Libraries and Rapid Release Single-Source Environment Implementation”
Presented by: Liz Fraley, Single-Sourcing Solutions, Inc. (formerly: Juniper Networks)
Co-authored by: Brenda DePaolis, Single-Sourcing Solutions, Inc. (formerly: Juniper Networks)
Audience: Developers

This presentation highlights the way PTC’s Arbortext Epic Editor has been implemented within the technical publications organization at Juniper Networks, focusing on the successful rollout of the editor and support systems. This document also details some of the proposed enhancements for continued Arbortext integration. Finally, it describes some of the challenges in deploying the Arbortext suite of tools and how those challenges were met.

The Arbortext project at Juniper Networks is a major technical publications initiative designed primarily to convert existing documentation and author new documentation in a single-sourcing environment. By authoring in an XML environment, we are able to make use of vast areas of overlapping information. Through information reuse, we can effectively increase the efficiency of our entire technical publications staff, an ever-increasing goal as demands for documentation increase while staffing and resource challenges persist.

The single-sourcing project had several initial requirements that had to met. These ranged from the successful conversion of Framemaker files to Epic files to the integration of Interwoven to provide a viable source control environment.

Presented by: Liz Fraley, Single-Sourcing Solutions, Inc. (formerly: Juniper Networks)

Presented at: 8th Annual Arbortext User Group International Conference (AUGI 2003)

Presentation Materials

Note: Arbortext was purchased by PTC in 2005