After the CMS Implementation Project

Much effort is focused, on the selection and subsequent implementation of a content management system (CMS). While it is obviously vital to ensure that the initial implementation project is successful, this is only the beginning of an ongoing commitment to growing and enhancing the use of content management throughout the organisation.

Robertson, James. CM Briefing (2004). Articles>Content Management>Project Management>Workflow

Designing and Planning Modular Content Projects  

Modular writing involves writing, labeling, storing, and assembling content modules. Read about how to design and plan a modular writing project and how this writing system affects traditional roles and responsibilities within a publications team.

O'Connor, Virginia. Intercom (2006). Articles>Content Management>Workflow

Managing Content Hypergrowth  

To cope with a flood of assets, site owners turn to content management software. As they outgrow their “home brew” solutions, they buy packaged applications -- even though today’s products are immature.

Dalton, John P., Harley Manning and Katharine M. Gardiner. Forrester Research (2001). Articles>Content Management>Workflow

Managing Life Sciences Content

Life sciences have been called the least automated industry in the world, but some pharmaceutical companies, medical device manufacturers, and healthcare-related organizations are working to dispel that image by implementing targeted content management solutions aimed at shortening the amount of time it takes to get new products to market.

Rockley Group, The (2004). Articles>Content Management>Scientific Communication>Workflow

Requirements of Content Management Systems: Definition According to Need

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).

Ziegler, Wolfgang. tekom (2005). Articles>Content Management>Information Design>Workflow

Tools and Technology: A Work-Flow Paradigm for Single-Source Publishing  

Today's organizations must consider the effect that new tools and technologies are having on work flow. Web technology has raised the importance of information. This change in the customer/supplier market is allowing the company with the best information to have an edge. It is our responsibility as communicators to find better, faster, and cheaper ways to distribute information. An effective work flow can accomplish this. In the most common work-flow scenarios, Web technology is placed on the back end of the production schedule. All of these scenarios are flawed in different ways. Solving Web work-flow problems requires a paradigm shift.

Christner-Vorhes, Jamie and Bill Pollak. STC Proceedings (1998). Articles>Content Management>Single Sourcing>Workflow

Who is in Control?: The Logic Underlying the Intelligent Technologies Used in Performance Support    

Performance support (also called EPSS, for electronic performance support system) emerged from the instructional design and training communities because corporate enterprise systems were difficult for people to use, and the training needed to make them productive was expensive and time consuming. A good definition is that 'EPSS (Electronic Performance Support Systems) are systems that provide employees with the information, advice and learning experiences they need to get up to speed as quickly as possible and with the minimum of support from other people' (Raybould 1996). One of the issues in designing performance support is managing information overload. Two approaches are the use of agents and the presentation of information in visual form (called information visualization). The former looks for ways that computer programs can do work for users, sorting through data on their behalf; the latter looks for ways to present information so that users can directly access it through direct manipulation. You can do both, but the selection of each has an impact on the interaction style and the degree to which users can directly control the system. It is therefore an issue that any performance support system designer should consider carefully. This is a logical extension of the goal of easy-to-use programs, adding the requirement that the user interface be actively informative and helpful.

Quesenbery, Whitney. Technical Communication Online (2002). Articles>Content Management>Workflow>EPSS

Wikibility Cultural Key Drivers: Flexibility

A flexible workplace is characterized by the capability of individuals to manage not only their work, time or resources, but also the possibility to influence and operate in an active way inside the community (from team to organizational level) and for these reasons to be part of the operational process.

Cammarata, Vincenzo. Grow Your Wiki (2008). Articles>Content Management>Workflow>Wikis

The Importance of Articulation Work to Agency Content Management: Balancing Publication and Control  

This paper describes the initial results of a qualitative field study of the work required to review and approve the content on government agency web sites. The study analyzes content management work in terms of Strauss’s conceptualization of articulation. The analysis describes examples of high and low level articulation in content review and approval including using paper, personal contact, and surveillance. Study results suggest that the articulation work present in non-software based review and approval processes helps to balance conflicting agency goals of publishing content and achieving absolute oversight over published content. It also suggests that software based content management systems may prove helpful for the management of some types of content in some situations, but it hypothesizes that actors will choose paper and face to face communication mechanisms to review and approve large amounts of new content and sensitive content.

Eschenfelder, Kristin R. Hawaii International Conference on System Sciences (2003). Articles>Content Management>Organizational Communication>Workflow

Moving Toward a Content Reuse Strategy, Slowly and Carefully    

The authors of this article use their own experience in implementing a content reuse strategy to assist the reader in effectively making the changes necessary while minimizing the effect on the departments or the company as a whole.

Evans, Jeannette P. and Julianne K. Forsythe. Intercom (2008). Articles>Content Management>Content Strategy>Workflow

Reporting XML Errors: Optimizing the Workflow

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.

Allen, Sarah. IDEAlliance (2004). Articles>Content Management>Workflow>XML

Extending XML in the Enterprise

This presentation explores how recent advances in user interfaces have blurred the once clear distinction between structured and unstructured data. It examines how these tools can be used to empower a new class of user to participate in an XML workflow and a managed content environment.

Parsons, Jon. IDEAlliance (2005). Articles>Content Management>XML>Workflow

Building Efficient Multilingual Workflows    

O’Keefe gives detailed information on two technology standards that may be used in multilingual workflows: XSL and XLIFF.

O'Keefe, Sarah S. Intercom (2009). Articles>Content Management>Workflow>Translation