Seminar archive · 5 March 2018
A structured-content journey starts with the right questions.
The original one-day seminar at Napatech in Denmark invited technical communicators to explore the move to XML and DITA through the experiences of organizations that had made the transition.
The 2018 announcement
Archive · Published 4 January 2018. Event invitations and roles reflect the original publication period; the event has passed.
Join us for this free one-day knowledge-sharing seminar to learn more about XML/DITA and learn about the journey to XML/DITA.
Hear directly from companies that have made the transition to structured content as they share their own personal experiences.
- Why structured content, and what is it?
- How do you prepare for the transition?
- How can you make sure you succeed?
- How do you select the right tools?
- How can you pilot a system?
- What does the future hold?
Don’t miss this opportunity!
Discover what innovations are on the horizon and what plans you should be making today for a successful tomorrow—and Network with fellow technical communication professionals.
Monday, March 5, 2018
9:30 am – 4:00 pm
Location Napatech A/S Tobaksvejen 23 A DK-2860 Soeborg Denmark
Places are strictly limited, so please register your interest early to avoid disappointment.
The original registration invitation and embedded form have been retired because this March 2018 event has passed.
Editorial context · October 2026
The day as announced
The announced questions covered the meaning of structured content, preparation for change, success factors, tool selection, pilot projects, and future planning. The event is historical; its registration form has been retired from this archive.
Turn the original questions into a pilot brief
- Name the problemChoose a specific source of friction, such as maintaining the same instruction in several places. Describe who feels that problem and where it occurs.
- Select representative contentInclude a task, its supporting information, a reusable piece, and at least one real publishing requirement. Avoid a sample that is so simple it cannot expose the hard decisions.
- Define the evidenceAgree what you will inspect: correctness, editorial effort, review clarity, output completeness, and the ability to maintain the sample after a change.
- Review the operating modelAsk who will own content structure, reusable information, tool configuration, and ongoing contributor support once the pilot ends.
Tool selection follows the working model
A useful pilot should reveal how content will be created, reviewed, reused, and maintained. List those responsibilities before choosing a feature demonstration. Otherwise, an attractive authoring interface can distract from an unresolved question about ownership, release control, or delivery. The original seminar’s sequence of preparation, tools, and piloting remains a productive way to frame that discussion.
Archive source: The Structured Content Journey, 4 January 2018.