Lean content strategy
Lean manufacturing begat lean software development which in turn begat lean content strategy.
What does lean content strategy look like?
Lean manufacturing begat lean software development which in turn begat lean content strategy.
What does lean content strategy look like?
We’re about to begin the last quarter of 2015, and that means CONFERENCES. Scriptorium is attending many tech comm and content strategy events.
Will we see you at these conferences?
The roles and responsibilities in an XML (and/or DITA) environment are a little different than in a traditional page layout environment. Figuring out where to move people is a key part of your implementation strategy.
Last week I was working in my home office when I heard an odd hissing sound. Upon investigation, I found that my hot water heater had decided to empty itself onto the basement floor.
Fortunately I had some failsafes in place; the heater’s pressure release valve was doing its job by routing scalding hot water onto the floor, and my floor is slightly slanted toward a drain in the floor. This got me thinking (because my brain is oddly wired this way) about failsafes in content workflows.
Thanks to everyone who has signed up for LearningDITA.com and taken the free Introduction to DITA course. The introductory course offers a high-level overview of DITA.
Want a deeper dive into the DITA information types (concept, topic, reference, and glossary)? Today, we are releasing our second course on the DITA concept topic. The course and supporting videos were created by a Scriptorium team led by Gretyl Kinsey (with help from Simon Bate, Jake Campbell, and me).
In testing one day, I was running a set of sample content through the DITA-OT, and much to my consternation, the build was succeeding, but generating no content. The error log helped to ferret out the source of the problem; the preprocessor was attempting to extract a linktext and navtitle from an image file that could not be found.
The image in question was a keyref pulled in from a map referenced in the main map file. Everything validated, previews showed the images resolving correctly, yet the images steadfastly refused to be pulled in during preprocessing—so what was wrong?
Technical Writing is only about what software you know! Is that why every where I read any type of document, web page, or article it is FULL of misspellings, incorrect punctuation, and horrible formatting?!!
That’s what started a thread on LinkedIn that encapsulates long-running debates on the skill sets technical writers need. (The thread was removed from LinkedIn sometime after Friday, unfortunately.)
Design and automation are often positioned as mutually exclusive–you have to choose one or the other. But in fact, it’s possible to deliver content in an automated workflow that uses a stellar design. To succeed, you need a designer who can work with styles, templates, and other building blocks instead of ad hoc formatting.
More content across more devices requires scalability–and that means more automation. A strategic approach to content needs to incorporate both design and automation as constraints and find the right balance between the two.
Metadata is one of the most important factors in making the most of your DITA XML-based content environment. Whether you’re converting legacy content into DITA or creating new structured content, it’s important to know what metadata (or data about data) your files will keep track of and why. Coming up with a plan for using metadata can be tricky, so here are some tips to make the process easier.
March 2025 update: Read this article to learn about what’s new with LearningDITA. The Introduction to DITA course is still free, and you can sign up for courses at store.scriptorium.com.
Our DITA learning site, LearningDITA.com, is now live with its first course, Introduction to DITA.