Perhaps feeling a bit nostalgic for the summer 20 years ago that I spent on a dig in Jordan, I’ve been doing a bit of self-directed reading lately focused on lithics.
Starting with the list of references in recent academic texts, I’ve sought out oft-cited, out-of-print books by mid-century archaeological luminaries.
Closing out my conference junket for 2014, I’m at Information Development World in sunny San Jose, California. Content reuse is not the only tactic you can apply as part of your content strategy to reduce cost and improve discoverability.
How often have you proudly described the great big manual or Help system you just finished writing to your fellow tech writers, your manager, or even potential employers? But how much of that bulk was really necessary? How do you decide when you have too much content? How do you decide which content stays and which lands in the archive? Applying metrics-driven lean content principles & practices as part of your content strategy can not only save you money on maintenance and localization, but more importantly it can make your content more discoverable and usable.
In this session, I’ll provide both strategic advice on how to decide whether you need to streamline your content, as well as practical suggestions about the tools and techniques you can use to make the streamlining process successful.
EDIT: You can now see my full presentation on SlideShare.
Kicking off the conference season for 2014 in Palm Springs, California, I’m back at another WritersUA. Taking advantage of my experience across all the major content development platforms over the past 20 years, I’m presenting about the various ways writers can improve the level of reuse in their content.
Text insets, conref elements, embedded topics, variables, tokens – no matter what technology you’re using to create your content, there’s a dizzying array of options available to you to enable reuse. With all that power and so many choices at your fingertips, you can quickly paint yourself into a corner. To truly take advantage of the potential cost savings and improved consistency that reuse offers, how do you decide which techniques to use for which types of content, and at what level in your information architecture?
Though I promise this will be technology agnostic, it’s inevitable that I’ll occasionally reference the software I’m responsible for designing, developing, and delivering.