Perils of DITA publishing, part 3: Indexing
In which we are boxed in by the limitations of DITA indexing support.
In which we are boxed in by the limitations of DITA indexing support.
Until I started working at Scriptorium, my educational and work background was in information and library science.
For remote work, file management in the cloud is way easy. Other methods, not so much…
I’ve been thinking about how time affects communication. We have constant deadlines, some of which are easier to meet than others. But there are other ways in which time affects content strategy.
This morning, I was among the many who received an email from Netflix CEO Reed Hastings. He was responding to criticisms that Netflix “lacked respect and humility in the way [the company] announced the separation of DVD and streaming and the price changes.”
Over the weekend, a friend showed me an episode of a reality show that featured some commentary by a “style expert.” This expert offered his advice while dressed in an outfit that would work well as a costume in a production of Oliver Twist (and that’s being charitable).
I have struggled to understand the keyref and conkeyref features added in DITA 1.2.
It wasn’t until we started applying them to our proposal workflow that I finally understood them. I hope this use case also helps others.
Social media is inexorably coalescing our personal and professional identities. What happens when baby pictures, political views, drinking habits, and hobbies collide with your corporate persona?
“She’s stupid.”
That’s what a shopper recently said about a coworker’s daughter, who is working a part-time retail job.
The Darwin Information Typing Architecture (DITA) is being positioned as the solution for XML-based technical content. Is DITA right for you?
This white paper describes the potential business advantages of DITA, provides a high-level overview of DITA’s most important features, and then discusses how you can decide whether to develop a DITA-based XML implementation.