LavaCon archive · September 2016
Two sessions. One connected content lifecycle.
The announced LavaCon lineup linked DITA implementation across business areas with the movement of localized content between content management and translation systems.
DITA across verticals
Jeff Engle · Xerox Services
From CCMS to TMS
and back again
Jim Tivy · Bluestream
The 2016 announcement
Archive · Published 19 September 2016. Event invitations and roles reflect the original publication period; the event has passed.
Jeff Engle, a Solutions architect with Xerox Services, will present, “Implementing DITA Across Verticals. Xerox Services provides DITA authoring and translation services for its internal and external clients.” Jeff will look at “three different verticals, (manufacturing, HR and training content), where DITA is currently being implemented by Xerox Services.” Attend to learn more about these excellent solutions and about the role XDocs plays in them.
Bluestream CTO Jim Tivy will speak about translating content, “The Localization Lifecycle: From CCMS to TMS and Back Again” where attendees will learn, “Best practices, pitfalls, and workarounds” along with the relationship between localized content and the CCMS, the TMS, and the LSP.”
The LavaCon Conference is “a gathering place for content strategists, documentation managers, and other content professionals who are willing to share their best practices and lessons learned—both what worked, and what didn’t,” and includes “83 sessions and workshops on how to plan, produce, and manage content strategy initiatives.”
Be sure to stop by the Bluestream table in the Exhibit Hall and say hello!
Editorial context · October 2026
The sessions as announced
Jeff Engle’s presentation was described as a look at DITA authoring and translation services across manufacturing, HR, and training content. Jim Tivy’s session, “The Localization Lifecycle: From CCMS to TMS and Back Again,” was described as covering best practices, pitfalls, and workarounds involving the CCMS, translation management system, and language service provider.
Follow the handoff, not just the file
- Prepare the contentAgree which source version is ready for translation and which supporting resources belong in the handoff.
- Maintain the relationshipKeep a clear association between source material and the translated content that returns. Record unresolved questions rather than burying them in an email thread.
- Reassemble and reviewCheck the returned language in the intended publication, including links, media, and output behavior. A successful import is only one part of readiness.
Different business areas need a shared conversation
Manufacturing procedures, HR information, and training material do not have to use identical editorial rules to benefit from a discussion about structured content. Begin by identifying which responsibilities are common, such as ownership, review, and publication approval, and which vary with the audience and purpose. This creates a more useful implementation discussion than assuming one content pattern should fit every department.
Archive source: Bluestream at LavaCon, 19 September 2016.