TC Dojo Open Session 
Repurposing Content for 
Multichannel Publishing 
Liz Fraley, Single-Sourcing Solutions, Inc.
Reuse Is Not New 
We have always tried to improve efficiency and reduce effort 
• Woodblock printing 
• Illuminated pages ...
Work Is Never “Done” 
 Content always changes. 
 Errors 
 Changes 
 New feature 
 New product 
 New company 
 Chang...
Increased Efficiency Reduces Work 
 Reusing and repurposing content is all 
about improving efficiency 
 Publications st...
“Our goal is to provide the right content 
to the right person, at the right time, in 
the right format, and in the right ...
Example: Fictional Product Document 
Based on the Neuros OSD Documentation 
 About the Neuros OSD 
 An open-source media...
Images of Neuros Audio Web Pages: 
Copyright 2006 Neuros Technology International, LLC. All Rights Reserved.
Images of Neuros Audio Web Pages: 
Copyright 2006 Neuros Technology International, LLC. All Rights Reserved.
Let’s Add An Imaginary Document To The Set 
Containing information applicable to a new release 
 Hardware product specs &...
Let’s Define Desired Output Targets 
At release time 
 Online Help (back into software 
build) 
 HTML for corporate web ...
The Dimensionality Problem 
 Next 3 slides 
 Originally from “Authoring & Document 
Management at Hamilton Sundstrand” A...
Many Changes Impact Other Documentation 
40-1 40C11 40C3A 40C7EH 40C7B 
Content 
Master 
From: “Authoring & Document Manag...
One Change Affects Every Medium in Which 
the Documentation Is Delivered 
Master 40-1 40C11 40C3A 40C7EH 40C7B 
WEB 
PRINT...
The Number of Documents Impacted by Just One 
Change Is Immense 
Master 40-1 40C11 40C3A 40C7EH 40C7B 
WEB 
PRINT 
CD-ROM ...
Now What Happens When… 
 The next Neuros product arrives? 
 Overlapping source code, features, hardware 
components 
 T...
Things Suddenly Get More Complicated 
 Content shared can be n-dimensional 
 Within a book 
 Across versions of a book ...
N-Dimentional Thinking is Hard 
Image from http://www.hawking.org.uk
Content Reuse and Effort Reduction 
Guidelines 
 Develop truly architected information 
 Modular writing is “the culture...
Potential Guidelines for Content Reduction 
 Don’t worry about whether you’re starting too big 
or too small or whether e...
More Guidelines for Content Reduction 
 Docplans should include all information 
that relates to or affects the informati...
Potential Guidelines for Managing Reuse 
 Corporate-level tools vs. local tools 
 Tool team should be corporate 
 Tools...
More Guidelines for Managing Reuse 
 Use standards whenever possible 
 Know the standards you choose 
 Mailing lists ge...
Questions?
Coming up... 
• Next TC Dojo Open Session 
– Title: Where are they now? 
– Date: Monday 16 Sept 2013 
– Topic: 
Where did ...
New Dojo! 
TC Dojo Arbortext Edition 
• Open Session Coming up… 
– Title: Building your Styler stylesheet: A look at modul...
Next Master Series session – Mon 26 August 
A single conversation among a small group of peers. Attendees will have the op...
See You Next Time 
Don’t forget to vote for your choice of 
upcoming session topics 
http://svy.mk/120AaAb
Repurposing Content for Multichannel Publishing
Repurposing Content for Multichannel Publishing
Upcoming SlideShare
Loading in …5
×

Repurposing Content for Multichannel Publishing

542
-1

Published on

Managing documents can get really complicated really fast. A single product can have a dozen models or versions and sold in over a hundred countries. Clients have cut their translations costs from $20,000 to $6700. It can be done and we can show you how.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
542
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Repurposing Content for Multichannel Publishing

  1. 1. TC Dojo Open Session Repurposing Content for Multichannel Publishing Liz Fraley, Single-Sourcing Solutions, Inc.
  2. 2. Reuse Is Not New We have always tried to improve efficiency and reduce effort • Woodblock printing • Illuminated pages • Engraving plates • Stamps • Movable type • Standard components • Mass production • Recycling
  3. 3. Work Is Never “Done”  Content always changes.  Errors  Changes  New feature  New product  New company  Changes to any one of those can trigger other changes.  Data Model  Metadata  Stylesheets  Processes
  4. 4. Increased Efficiency Reduces Work  Reusing and repurposing content is all about improving efficiency  Publications staff, support staff, and customers!  Opportunities for reuse occur everywhere information intersects customers  At all points in the authoring and publication process (creation, construction, aggregation, and production)  All across the enterprise (engineering, marketing, customer support, product/project management, training, legal)
  5. 5. “Our goal is to provide the right content to the right person, at the right time, in the right format, and in the right media.” – Lisa Fisher, IBM Content Management Strategies Conference 2007
  6. 6. Example: Fictional Product Document Based on the Neuros OSD Documentation  About the Neuros OSD  An open-source media center hardware appliance that encourages customer software development, modification, and enhancement (http://www.neurosaudio.com/)  Customer-viewable information set: Community Wiki Bug Repository Online Store Google Group Quick-start Guide FAQ Forums Corporate Website Corporate Wiki Subversion Repository Support Website Product Specs IRC Channel Software Download Legal bits
  7. 7. Images of Neuros Audio Web Pages: Copyright 2006 Neuros Technology International, LLC. All Rights Reserved.
  8. 8. Images of Neuros Audio Web Pages: Copyright 2006 Neuros Technology International, LLC. All Rights Reserved.
  9. 9. Let’s Add An Imaginary Document To The Set Containing information applicable to a new release  Hardware product specs & feature list  Sources: HW-ENG, PLM/PDM, Marketing documentation  Hardware appliance details  Sources: HW-ENG CAD files  API details  Sources: SW-ENG specifications, implementation and build systems  Outstanding bugs  Sources: Internal bug database, community bug database  Troubleshooting information  Sources: Customer Support pages, IRC transcripts, FAQ, mailing list
  10. 10. Let’s Define Desired Output Targets At release time  Online Help (back into software build)  HTML for corporate web  Text/HTML mail for mailing lists  Visio Stencil  Diagnostic application  PDF  Other compiled documents (eReader, Palm, CHM, etc.)  Wiki (both)
  11. 11. The Dimensionality Problem  Next 3 slides  Originally from “Authoring & Document Management at Hamilton Sundstrand” AUGI 2002 by Ray Hicks, Manager Tech Pubs, Hamilton Sundstrand, and Eric Helgerman, Architect, Creative Concepts  Exemplary depiction of the “Dimensionality Problem”
  12. 12. Many Changes Impact Other Documentation 40-1 40C11 40C3A 40C7EH 40C7B Content Master From: “Authoring & Document Management at Hamilton Sundstrand” AUGI 2002 by Ray Hicks, Manager Tech Pubs, Hamilton Sundstrand, and Eric Helgerman, Architect, Creative Concepts
  13. 13. One Change Affects Every Medium in Which the Documentation Is Delivered Master 40-1 40C11 40C3A 40C7EH 40C7B WEB PRINT CD-ROM From: “Authoring & Document Management at Hamilton Sundstrand” AUGI 2002 by Ray Hicks, Manager Tech Pubs, Hamilton Sundstrand, and Eric Helgerman, Architect, Creative Concepts
  14. 14. The Number of Documents Impacted by Just One Change Is Immense Master 40-1 40C11 40C3A 40C7EH 40C7B WEB PRINT CD-ROM LANGUAGE UNITED VERSION CESSNA PRODUCT From: “Authoring & Document Management at Hamilton Sundstrand” AUGI 2002 by Ray Hicks, Manager Tech Pubs, Hamilton Sundstrand, and Eric Helgerman, Architect, Creative Concepts
  15. 15. Now What Happens When…  The next Neuros product arrives?  Overlapping source code, features, hardware components  The company acquires or is acquired by someone else?  Look and feel changes, at the minimum  A third party decides to be an OEM vendor and wants to rebrand and add hardware or software?  Look and feel changes, as well as information aggregation  The company decides to add a new output target, format, or information repository?  New output format, new technology, or some other unknown factor
  16. 16. Things Suddenly Get More Complicated  Content shared can be n-dimensional  Within a book  Across versions of a book  Between multiple books  Between multiple books and across versions  Between books, across versions, and across multiple product lines  Complexity can increase exponentially  Multidimensional thinking is not easy
  17. 17. N-Dimentional Thinking is Hard Image from http://www.hawking.org.uk
  18. 18. Content Reuse and Effort Reduction Guidelines  Develop truly architected information  Modular writing is “the culture, not the tagging”  Integration and reuse requires thinking at a higher level  Understand the whole  How any particular information module fits into the overall content picture  The relationships between information  Find out why some things are reused and others are not  Develop processes that reinforce guidelines  For example, a process to justify when something can be developed for reuse or as unique content
  19. 19. Potential Guidelines for Content Reduction  Don’t worry about whether you’re starting too big or too small or whether everything’s covered  It’s not; It never will be.  Look for ways to make small improvements  Where can your stylesheet do the work?  Where can tooling improve experience or efficiency (anyone)  Refocus staff to “fill” desired roles  People who can think at the vision level start to take on Information Architect role  Change classifications as necessary to adjust requisition pool
  20. 20. More Guidelines for Content Reduction  Docplans should include all information that relates to or affects the information contained in the document that is being generated across the enterprise  What is Marketing writing?  What about Customer Support?  What don’t you have to write?  Staff members can use the time they get not writing duplicate information to keep up or take on the responsibilities of the new roles
  21. 21. Potential Guidelines for Managing Reuse  Corporate-level tools vs. local tools  Tool team should be corporate  Tools to improve efficiency should be standardized and subject to a managed release process  This does not mean that tools must all be from one vendor or of one language.  Tight vs. loose integration  Opt for loose integration!  Upgrading customized code is worse than upgrading custom code
  22. 22. More Guidelines for Managing Reuse  Use standards whenever possible  Know the standards you choose  Mailing lists get the following question all the time: "how do I do do X?”  The answer is always "use this, the spec has already done the work for you"  Keep an eye on developing standards, languages, and technology  Ever changing pool of technical availability  New output targets/channels appear every day
  23. 23. Questions?
  24. 24. Coming up... • Next TC Dojo Open Session – Title: Where are they now? – Date: Monday 16 Sept 2013 – Topic: Where did those XML projects, which you’ve heard about at conferences over the years, end up? Sure, IBM was successful, but what about the small companies? Or the companies that don’t have teams of software people that the technical publications teams can draw upon for help? Did they make it? We interviewed long-term Arbortext customers to find out where they are now, whether they realized the full potential of their solutions, what data they collected, and what lessons they learned. We’ll share it with you – Registration link: http://bit.ly/14VQbJm
  25. 25. New Dojo! TC Dojo Arbortext Edition • Open Session Coming up… – Title: Building your Styler stylesheet: A look at modules – Date: Thursday 29 August 2013 – Topic: To kick off our TC Dojo Arbortext Edition, we took your requests and decided to jump right in to Styler. In this first session, we will show you how to build your foundation for your first Arbortext Styler Stylesheet using the Single- Sourcing Solutions’ method. This is how we create new projects for our customers and this is how we coach and mentor our customers. – Registration link: http://bit.ly/16phIQt
  26. 26. Next Master Series session – Mon 26 August A single conversation among a small group of peers. Attendees will have the opportunity to present their challenges and solicit advice in a confidential supportive environment with other Master Series Members. Sign up at http://tcdojo.org
  27. 27. See You Next Time Don’t forget to vote for your choice of upcoming session topics http://svy.mk/120AaAb

×