XML Tools – less expensive, more abundant, and easier to use, I hope

Bluestream archive · 2007Published March 1, 2007

Barbara Stuhlemmer’s 2007 article considered a practical problem for smaller documentation teams: how to produce many related outputs without rewriting the same information each time.

From the archive · Industry perspective

XML tools became a practical business question

An attributed reading note on Barbara’s View and its early look at XDocs, XML authoring and help-authoring tools.

Original article: “XML Tools – less expensive, more abundant and easier to use, I hope,” by Barbara Stuhlemmer, ClearComm Information Design, on Barbara’s View.
Source publication: March 14, 2007.
Bluestream archive entry: March 1, 2007. The dates differ in the original records; neither has been silently changed.

A practitioner’s early look at the tool landscape

Stuhlemmer wrote about the challenge of delivering a large user manual alongside market-specific manuals, help, training and web content. She was exploring single-sourcing as a way to reduce repeated work while keeping quality and costs manageable.

After demonstrations of Bluestream XDocs with XMetaL and MadCap Flare, she saw more approachable interfaces and a wider choice of tools. She also asked where content management ended and authoring began, and which combinations suited a client’s needs. Her article remained an evaluation in progress, rather than a final selection or a current comparison of those products.

Read Barbara Stuhlemmer’s original article

Editorial context · October 2026

Evaluate responsibilities before comparing products

A useful tool review starts by assigning responsibilities. Identify the environment in which a person writes, the place that controls shared content and versions, and the process that produces each output. Then test the handoffs with the same sample rather than comparing unrelated demonstrations.

01

Create

Who writes and reviews the content, and what help do they need in the authoring interface?

02

Control

Where are ownership, versions, permissions and shared components managed?

03

Deliver

Which outputs must be produced, and who maintains their presentation and configuration?

Document the work required between those stages. A smooth demonstration is useful, but the everyday process also includes corrections, access changes, missing assets and updates to existing publications. A representative pilot makes those responsibilities visible.

This checklist is Bluestream editorial context added in October 2026. Product comparisons and opinions in the linked article remain those of its original author in 2007.

Sign-up for the latest Bluestream News

Close