In March 2006, Thompson Rivers University’s Instructional Development and Research Group nominated XDocs CMS for an Educational Technology User Group innovation award, following work on a structured-content management interface.
The XDocs CMS workflow behind the nomination
The university’s Instructional Development and Research Group (IDRG) had worked with XML and SGML for several years. Its structured-content process already generated formatted PDFs for print and complex websites from a common XML document. Course information maintained in SGML also served web, print and relational-database requirements.
However, the remaining difficulty was the production handoff. People had to extract XML from the existing repository and run XSL and XSL-FO transformations to create final outputs. The group wanted a content management system that could support on-the-fly web and print generation for multiple uses.
From manual intervention to a managed interface
According to the announcement, Bluestream’s native XML database and the developing XDocs CMS provided the required functionality while helping keep maintenance costs down. IDRG had been working with Bluestream for ten months to identify and describe requirements for the interface and the additional capabilities it needed.
Editorial context · October 2026
Content reuse depends on the production path
This early archive story is distinctive because reuse was already present. The group could produce different outputs from common structured content; the challenge was how that content moved through storage and transformation. Therefore, examine the handoffs surrounding a content model, rather than treating the model alone as the whole system.
- Locate the sourceIdentify where your team stores the authoritative structured content.
- Trace the handoffsRecord every extraction, transformation and manual intervention needed to produce an output.
- Define a repeatable resultSpecify what a managed process must produce and how the team will verify it.
These are editorial analysis questions prompted by the historical workflow. The nomination is evidence of the collaboration described in the announcement, rather than proof of a later award outcome.