Comments on: 10 DITA Lessons Learned From Tech Writers in the Trenches http://thecontentwrangler.com/2006/07/30/10_dita_lessons_learned/ Content is a business asset worthy of being managed Thu, 11 Mar 2010 11:29:23 +0000 http://wordpress.org/?v=abc hourly 1 By: Laurie Mann http://thecontentwrangler.com/2006/07/30/10_dita_lessons_learned/comment-page-1/#comment-24 Laurie Mann Tue, 13 May 2008 17:01:50 +0000 http://localhost:8888/ee/?p=692#comment-24 <p>If I’d had the time, I could have written a similar article about helping to move an 8,000 page docset in Interleaf to Arbortext and Docbook.  We had many of the same problems back in 1999.  I believed then that XML was going to be “the wave of the future;” it just took a little longer to get there than I’d expected! </p> If I’d had the time, I could have written a similar article about helping to move an 8,000 page docset in Interleaf to Arbortext and Docbook.  We had many of the same problems back in 1999.  I believed then that XML was going to be “the wave of the future;” it just took a little longer to get there than I’d expected!

]]> By: Robert Nagle http://thecontentwrangler.com/2006/07/30/10_dita_lessons_learned/comment-page-1/#comment-23 Robert Nagle Wed, 02 Jan 2008 23:44:40 +0000 http://localhost:8888/ee/?p=692#comment-23 <p>Wow, this is an amazingly useful article and directly relevant to my work. I’ve been investigating tools and methods and trying to anticipate problems before they arise. </p> <p> The unanswered question is at what threshhold does it makes sense to use DITA. Also, my company uses a CMS which can process XML, but it is not specifically a DITA-based CMS.  I work for a SW company, so they conceivably could produce extensions for our CMS (which is flexible and powerful).  But it would have to be an inhouse job.  </p> <p> Another issue: I’m a lone technical writer, and although I think I possess the right skillset for DITA content production, I don’t know if I have the skillset to troubleshoot a XML repository (especially if the transforms are giving me problems). </p> Wow, this is an amazingly useful article and directly relevant to my work. I’ve been investigating tools and methods and trying to anticipate problems before they arise.

The unanswered question is at what threshhold does it makes sense to use DITA. Also, my company uses a CMS which can process XML, but it is not specifically a DITA-based CMS.  I work for a SW company, so they conceivably could produce extensions for our CMS (which is flexible and powerful).  But it would have to be an inhouse job. 

Another issue: I’m a lone technical writer, and although I think I possess the right skillset for DITA content production, I don’t know if I have the skillset to troubleshoot a XML repository (especially if the transforms are giving me problems).

]]> By: Neeraja http://thecontentwrangler.com/2006/07/30/10_dita_lessons_learned/comment-page-1/#comment-22 Neeraja Thu, 11 Oct 2007 07:40:57 +0000 http://localhost:8888/ee/?p=692#comment-22 <p>Hi, <br /> Are the comments moved or deleted? I can see that there are 4 comments for the article, but do not see any when I click Comments. It’d be good if I can see what others think about it. <br /> Thanks, <br /> Neeraja </p> Hi,

Are the comments moved or deleted? I can see that there are 4 comments for the article, but do not see any when I click Comments. It’d be good if I can see what others think about it.

Thanks,

Neeraja

]]> By: ScottAbel http://thecontentwrangler.com/2006/07/30/10_dita_lessons_learned/comment-page-1/#comment-21 ScottAbel Tue, 01 Aug 2006 15:36:08 +0000 http://localhost:8888/ee/?p=692#comment-21 <p>Marcus: </p> <p> Thanks for your comment. I think your point is valid. DITA projects are XML projects. To me, the lessons learned shared in this article serve to illustrate that most documentation projects are not yet XML projects. As such, we have a long way to go as an industry until these lessons learned are common wisdom among our peers. </p> <p> Scott Abel <br /> The Content Wrangler <br /> <a href="http://www.thecontentwrangler.com" rel="nofollow">http://www.thecontentwrangler.com</a> </p> Marcus:

Thanks for your comment. I think your point is valid. DITA projects are XML projects. To me, the lessons learned shared in this article serve to illustrate that most documentation projects are not yet XML projects. As such, we have a long way to go as an industry until these lessons learned are common wisdom among our peers.

Scott Abel

The Content Wrangler

http://www.thecontentwrangler.com

]]>