{"id":219,"date":"2016-07-12T15:09:51","date_gmt":"2016-07-12T15:09:51","guid":{"rendered":"https:\/\/www.precisioncontent.com\/blog\/?p=219"},"modified":"2016-07-12T16:08:10","modified_gmt":"2016-07-12T16:08:10","slug":"a-dita-project-gone-wrong-how-to-fight-the-daleks","status":"publish","type":"post","link":"https:\/\/www.precisioncontent.com\/blog\/a-dita-project-gone-wrong-how-to-fight-the-daleks\/","title":{"rendered":"A DITA project gone wrong: How to fight the Daleks"},"content":{"rendered":"<h4>Don\u2019t let the Daleks EX-TERMIN-ATE your documentation plans. Get back on track with Precision Content.<\/h4>\n<h5><img loading=\"lazy\" class=\"wp-image-228 aligncenter\" src=\"https:\/\/www.precisioncontent.com\/blog\/wp-content\/uploads\/2016\/07\/drwho2.jpg\" alt=\"drwho2\" width=\"942\" height=\"463\" srcset=\"https:\/\/www.precisioncontent.com\/blog\/wp-content\/uploads\/2016\/07\/drwho2.jpg 1920w, https:\/\/www.precisioncontent.com\/blog\/wp-content\/uploads\/2016\/07\/drwho2-300x148.jpg 300w, https:\/\/www.precisioncontent.com\/blog\/wp-content\/uploads\/2016\/07\/drwho2-768x378.jpg 768w, https:\/\/www.precisioncontent.com\/blog\/wp-content\/uploads\/2016\/07\/drwho2-1024x503.jpg 1024w\" sizes=\"(max-width: 942px) 100vw, 942px\" \/><\/h5>\n<h5><\/h5>\n<h5>The Whoniverse<\/h5>\n<p>DITA is a wonderful documentation standard that takes technical documentation into a new world of possibilities. From re-use to multi-channel publishing, there\u2019s no doubt that DITA is a massive step forward from unstructured content. However, that massive step forward has some fundamental gaps that could leave you flailing for a foothold in a <a href=\"https:\/\/en.wikipedia.org\/wiki\/Whoniverse\">Whoniverse<\/a> without a Tardis.<br \/>\n&nbsp;<\/p>\n<h5>Enter the Daleks<\/h5>\n<p>There are a lot of factors that go into making a DITA adoption successful, from upper management support to a sound implementation, and it\u2019s not unheard of for a DITA adoption to stall and be abandoned or left to limp along.<\/p>\n<p>Some of the major gaps that DITA adopters have to deal with include<\/p>\n<ul>\n<li>lack of writing standards<\/li>\n<li>lack of consistent tag use, and<\/li>\n<li>lack of end-to-end tools and content strategy.<\/li>\n<\/ul>\n<p>Unfortunately, the Daleks are ready to swoop (OK, roll in) whenever a DITA project falters to expose its flaws and wreak utter destruction. The Daleks AKA middle management don\u2019t\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 understand the value of the project and how, by applying a little Who-vian hands-on work, things could easily be turned around.<br \/>\n&nbsp;<\/p>\n<h5>Lack of writing standards<\/h5>\n<p>There\u2019s nothing in DITA that says how you should write. There are best practices and there are lots and lots of opinions, but the writers are mostly left to figure out for themselves not only what kind of content should be in each topic type but whether or not to use some elements at all, such as the short description.<\/p>\n<p>Think of DITA as infrastructure; you can use that infrastructure to build whatever you want. But without well-thought-out direction, authors end up<\/p>\n<p>building this &#8230;<\/p>\n<p><img loading=\"lazy\" class=\"alignleft wp-image-221\" src=\"https:\/\/www.precisioncontent.com\/blog\/wp-content\/uploads\/2016\/07\/Ugly_cakewreckdotcom.jpg\" alt=\"Ugly_cakewreckdotcom\" width=\"191\" height=\"258\" srcset=\"https:\/\/www.precisioncontent.com\/blog\/wp-content\/uploads\/2016\/07\/Ugly_cakewreckdotcom.jpg 450w, https:\/\/www.precisioncontent.com\/blog\/wp-content\/uploads\/2016\/07\/Ugly_cakewreckdotcom-222x300.jpg 222w\" sizes=\"(max-width: 191px) 100vw, 191px\" \/>instead of this &#8230;<\/p>\n<p><img loading=\"lazy\" class=\"wp-image-222 alignnone\" src=\"https:\/\/www.precisioncontent.com\/blog\/wp-content\/uploads\/2016\/07\/Beautiful-Wedding-Cakes-Roses.jpg\" alt=\"Beautiful-Wedding-Cakes-Roses\" width=\"194\" height=\"259\" srcset=\"https:\/\/www.precisioncontent.com\/blog\/wp-content\/uploads\/2016\/07\/Beautiful-Wedding-Cakes-Roses.jpg 500w, https:\/\/www.precisioncontent.com\/blog\/wp-content\/uploads\/2016\/07\/Beautiful-Wedding-Cakes-Roses-225x300.jpg 225w\" sizes=\"(max-width: 194px) 100vw, 194px\" \/><br \/>\n&nbsp;<\/p>\n<h5>Lack of consistent tag use<\/h5>\n<p>Many departments don\u2019t realize they need to determine a detailed standard on how to use the tags so that each writer is using them consistently. Issues as simple as determining when &lt;wintitle&gt; is used versus &lt;uicontrol&gt;, or which types of tables to use, make a huge difference when multiplied by the number of writers and number of topics written over a few years. If everyone is doing things a little differently, your output is going to be consistently inconsistent. Once you have determined the standard, you need someone to regularly review tag use to ensure everyone actually follows the standard.<\/p>\n<p>Inconsistencies in markup become highly visible, published fodder for your Daleks to use against you.<br \/>\n&nbsp;<\/p>\n<h5>Lack of end-to-end tools and content strategy<\/h5>\n<p>DITA includes no tools and no content strategy. Departments have to patchwork assemble their assembly of tools and the content strategy that overarches them all. Improper identification of requirements or a poor content strategy can you lead you down a one-way road towards poor tool selection. Once you\u2019re locked into a poor tool (or worse, two poor tools trying to work together), the effect can be insidious. Authors may spend more time fighting with the tools than authoring content and may still not be able to reach the required goals.<br \/>\n&nbsp;<\/p>\n<h5>The Doctor<\/h5>\n<p>Precision Content was created to fill the DITA gaps and to help companies recover from DITA-saster before the Daleks come hunting with budget cuts and Microsoft Word solutions.<\/p>\n<p>Precision Content includes a detailed, usable, proven writing standard that can be intelligently modified when needed. Authors have the support they need not only to write consistent content but to write highly usable content\u2014precise and clear for those who need it most.<\/p>\n<p>Precision Content always includes not only tag use standards but also a review strategy so tag use is consistent and enforced. And reviewers too if you need them!<\/p>\n<p>The heavy lifters at Precision Content also turn their sonic screwdrivers to the tools and content strategy. It\u2019s never too late to get back on track and reach (and even identify) the goals that will keep the Daleks at bay.<\/p>\n<p>Whatever your state of DITA adoption, whether you\u2019re in mid-disaster or just starting out, Precision Content is the perfect Dalek-fighting solution.<br \/>\n&nbsp;<\/p>\n<h5>Enter the team<\/h5>\n<p>The Precision Content team works with you and your team to address and fix the damage done and determine the best path forward.<\/p>\n<ul>\n<li>Writing: They have a team of writers who can write and re-write content and content strategists to help.<\/li>\n<li>Training: Certified trainers ensure everyone understands the standards and stick around to ensure tag use and writing standards are both adhered to.<\/li>\n<li>Content Strategists: They\u00a0have architects to help you identify goals and requirements, then guide you through the process end-to-end tools selection and content strategy.<\/li>\n<\/ul>\n<p>Don\u2019t let the Daleks EX-TERMIN-ATE your documentation plans. Get back on track with Precision Content. <a href=\"https:\/\/www.precisioncontent.com\/contact\/\">Contact us<\/a> today.<\/p>\n<hr \/>\n<p>Photo references:<br \/>\nDr. Who &#8211; pictures.4ever.eu; Before &#8211; cakewrecks.com; After &#8211;\u00a0bestweddingcakesidea.com<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Don\u2019t let the Daleks EX-TERMIN-ATE your documentation plans. Get back on track with Precision Content. The Whoniverse DITA is a wonderful documentation standard that takes technical documentation into a new world of possibilities. From re-use to multi-channel publishing, there\u2019s no doubt that DITA is a massive step forward from unstructured content. However, that massive step [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":242,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false},"categories":[12,2,7,6],"tags":[],"_links":{"self":[{"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/posts\/219"}],"collection":[{"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/comments?post=219"}],"version-history":[{"count":19,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/posts\/219\/revisions"}],"predecessor-version":[{"id":247,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/posts\/219\/revisions\/247"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/media\/242"}],"wp:attachment":[{"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/media?parent=219"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/categories?post=219"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/tags?post=219"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}