Hyperlinking Documents in PageMaker

These four supertips deal with adding links to your Adobe® PageMaker® 7.0 online documents: * Learn how to create anchors and simple page-to-page links. * Explore linking to external URLs using the Hyperlinks palette. * Drag links from Netscape Navigator directly onto elements on PageMaker document pages. * Create automatic tables of contents and index links for PageMaker documents that are exported to Adobe Acrobat® PDF files.

Adobe (2003). Design>Content Management>Document Design>Adobe PageMaker

Identifying the Components of Your ROI

Identifying Return on Investment (ROI) for your content management business case begins with a thorough analysis. This article reviews the information you need to gather to identify ROI for an effective business case for content management.

Rockley, Ann. Rockley Bulletin (2004). Articles>Content Management>Assessment>Business Case

Implementing a CMS: A Game-changing Corporate Initiative  

The success of a CM project depends not just on process management, but on change management as well. Discover the ways that an organization can help its staff overcome initial resistance to change.

Hamer, Emma C. Intercom (2007). Articles>Content Management>Project Management

Implementing a Content Management System  

Before you begin a pilot project using a CMS, you must understand how it will work. Read on to learn how to define your information model, set up your folder structure, create a metadata scheme, assign roles and responsibilities, define your workflow, and measure results.

Hackos, JoAnn T. Intercom (2007). Articles>Content Management>Project Management

Implementing a Document Control System  

Document control is a major component of any quality system. To implement a document control system, first establish Policies/procedures for generating, approving, issuing, and revising documents. The next step is to design and implement forms and a filing system/data base for managing quality documents. Teamwork and established guidelines can help ease the complexities of implementing a document control system.

Matthews, Diane L. STC Proceedings (1994). Articles>Documentation>Content Management

Implementing Single Sourcing in Your Organization  

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.

Sukach, Rebecca, Robert Kennedy and Marie Devine. STC Proceedings (2002). Design>Content Management>Single Sourcing

The Implications of Single Sourcing for Technical Communicators    

Surveys four books that examine methods of single sourcing, including publishing tools, XML, and content management systems. Reviews articles describing the roles of writers and editors, the tool set and its implementation, and ways to make dynamic content more effective

Williams, Joe D. Technical Communication Online (2003). Articles>Content Management>Single Sourcing>XML

The Implications of Single Sourcing for Writers and Writing    

Argues that single sourcing puts pressures on the workforce and the very conception of 'writer' and 'document. Examines literature on change management for clues into managing the impacts of single sourcing on writers.

Carter, Locke. Technical Communication Online (2003). Articles>Content Management>Single Sourcing>Rhetoric

The Importance of Content Management System Usability

The rollout of a content management system (CMS) has the potential to impact on more users than any other system since e-mail. 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. It is these two challenges that place usability as a central issue to be raised and addressed.

Robertson, James. Step Two (2003). Design>Content Management>Usability

Incorporating Usability into Content Management

This article describes the importance of incorporating usability into all stages of implementing content management, including assessing your needs, assessing your users (of both the content and the content management system), and assessing your content. It questions the emphasis of technology in many of the current discussions about content management, and instead, advocates looking to the field of usability to form the basis of a content management implementation.

Rockley, Ann. Rockley Bulletin (2004). Articles>Content Management>Usability

Indexer Wants to Retrain

With such a considerable portion of our collective mindshare devoted to information management products these days, it's no wonder that you're lost in terminology and technology. And it's no wonder that so many of us are confused.

Byrne, Tony. CMSworks (2004). Careers>Content Management>Indexing

Information Architects and Their Central Role in Content Management

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.

Warren, Rita. ASIST (2001). Articles>Content Management>Information Design

Information Architecture of Content Management

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' and customers' 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.

Rockley, Ann. STC Puget Sound (2005). Articles>Content Management>Information Design

Information Architecture of Content Management

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' and customers' 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.

Rockley, Ann. Rockley Bulletin (2004). Articles>Content Management>Information Design>User Centered Design

Information Delivery: Single Source Documentation for Multiple Delivery Mechanisms  

Information for a software product is often presented in multiple places and in multiple formats, including printed manuals, quick-reference cards, online Help, online tutorials, online product information, and training materials. Delivery formats can include Acrobat Portable Document (.pdj files, he&n ( hlp) Jiles, HTML ( htm) files, PostScript Jiles, Write (wri) files, text files, and document book$les. Delivery media can include CD-ROM, floppy diskettes, magnetic tape, Web pages, and paper.

Flanders, Melanie G. and Nicole Y. Smart-Wycislo. STC Proceedings (1997). Articles>Content Management>Single Sourcing

Information Modeling  

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.

Rockley, Ann. STC Proceedings (2002). Design>Content Management>Information Design>Metadata

Information Modeling: A Practical Approach  

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.

Rockley, Ann. STC Proceedings (2003). Articles>Information Design>Content Management>Project Management

Information Process Maturity Model (IPMM)  

There are several reasons for the Information Process Maturity Model: moving beyond chaos; moving beyond the heroism of talented and dedicated individuals; moving toward a repeatable, reliable process.

ComTech Services (2000). Articles>Content Management>Workflow

Integrating Content Management with Portals: Meeting Enterprise Information Needs  

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. Given the historical deployment of these technologies, many associate the application of content management solutions to externally facing sites, serving transactional e-business needs; and the application of portals to internally facing sites for general employee access to a wide range of information sources and applications. However, both technologies can provide support for the complete information lifecycle, from information creation to management to delivery.

CAP Ventures. Articles>Content Management>Information Design

The Intranet as Ecosystem: A Model for Sustaining Development

The complexity of the intranet and the interrelationship between it and the organization’s overall environment mean that traditional methods for supporting company information technology and communication (in which geographically and administratively separate groups determined company standards and guidelines) may not be adequate for the new medium. Available resources are also inadequate; material for web 'authors' (writers, information architects, graphic artists, and programmers) usually focuses at the site level, and most academic and trade articles on intranets focus on the central internal home page or on aspects of the physical infrastructure. Resources covering the whole intranet generally focus on management issues—hiring staff, setting goals, overseeing the design process, selling ideas to upper management, and getting people to use the system once it is deployed. But support groups tasked with the everyday design and maintenance of the intranet also need to “manage” it—that is, to envision the intranet’s role in the overall communication and technological structure of the organization, design and maintain its architectural structure, and sustain it by ensuring its content is accurate, timely, useful, and usable.

Wilder, Pam. University of Washington-Seattle (2000). Books>Content Management>Intranets

Introducing a Strategic Approach to Outstanding Content Development  

Great content doesn't happen by accident. By taking a rational approach that includes careful planning, diligent implementation, and well-tested delivery, vendor teams can ensure a successful project that satisfies client needs, budget constraints, and schedule demands while meeting the business objectives of both the client and the vendor.

Sakson and Taylor (2004). Articles>Content Management

Introduction of the DocuCat Information System for the Entire Product Documentation at Unaxis Displays

In order to improve this situation, the "Integrated Documentation" project was started in the fall of 2002. Our goal was to place the entire documentation of a system in a convenient manner (on CD or via Internet) at the disposal of Unaxis Displays service technicians and customers. Special attention should be paid to the linking of important information which is required again and again during maintenance and service work. The project derived benefit from the fact that Unaxis has been shipping electronic versions of operating instructions and spare parts catalogs to a number of customers for several years. The required internal processes and the software had been developed by CPTec GmbH. To be consistent, the same company was hired in order to extend the existing spare parts catalog solution to an overall solution named "DocuCat".

Ratz, Günter. CPTec GmbH (2003). Articles>Content Management

An Introduction to Content Management  

CMS analysis and design; an implementation example.

Garrett, David and Mary Pitz. STC Region 7 Proceedings (2002). Presentations>Content Management

Introduction to Single Source, Part 1  

In the first of a two-part article, Butland examines the arguments for and against single sourcing, a method of producing documentation for several media from a single source. He also discusses the differences between manuals and help, and offers suggestions on how to conduct single source projects involving these media.

Butland, Philip. Intercom (2001). Articles>Content Management>Single Sourcing

Introduction to Single Source, Part 2  

In the second installment of a two-part article, Butland discusses obstacles to single sourcing and how to overcome them. Part 1, which explored the advantages of single sourcing and discussed the differences between manuals and help, was published in the February 2001 issue of Intercom.

Butland, Philip. Intercom (2001). Articles>Content Management>Single Sourcing