{"id":3802,"date":"2017-03-09T00:00:00","date_gmt":"2017-03-09T00:00:00","guid":{"rendered":"https:\/\/www.globalizationpartners.com\/2017\/03\/09\/structured-writing-part-6-publishing-xml-content\/"},"modified":"2021-01-03T17:50:43","modified_gmt":"2021-01-03T17:50:43","slug":"structured-writing-part-6-publishing-xml-content","status":"publish","type":"post","link":"https:\/\/www.globalizationpartners.com\/2017\/03\/09\/structured-writing-part-6-publishing-xml-content\/","title":{"rendered":"Structured Writing Part 6: Publishing XML Content"},"content":{"rendered":"<p>Once you&#8217;ve created some <a class=\"hooked\" href=\"\/2017\/03\/03\/structured-writing-part-5-applying-dita-elements\/\">XML content using DITA<\/a>, you&#8217;re ready to publish the content to one or more outputs. The building blocks for publishing are the XML files, a DITA map and a style sheet. XML authoring programs offer a range of publishing options. Let&#8217;s look at how this works.<\/p>\n<h5>Assembling the Content Using a DITA Map<\/h5>\n<p>To assemble the XML files, you need to create a DITA map in your XML authoring program, which is a way to pull all the XML files into an organized group. A DITA map is like a table of contents in a Microsoft Word document, only you&#8217;re creating it from multiple files. In this example, the DITA map for Output A would include topics 1, 2 and 3. The DITA map for Output B would include topics 1, 3 and 6.<\/p>\n<p><img decoding=\"async\" class=\"large\" style=\"width: 600px; height: auto;\" src=\"https:\/\/uberflip.cdntwrk.com\/files\/aHViPTY0ODI0JmNtZD1pdGVtZWRpdG9yaW1hZ2UmZmlsZW5hbWU9aXRlbWVkaXRvcmltYWdlXzU4YzFkNTk4MWRmYjAucG5nJnZlcnNpb249MDAwMCZzaWc9N2Y4NTM2MDcwMjFiODQ5MDE3OWZjYWQ1MzkxNWNmZWU%253D\" \/><\/p>\n<p>You can add and delete topics at any time in a DITA map and you can have multiple DITA maps that make up a document.<\/p>\n<h5>Publishing Content<\/h5>\n<p>Once you&#8217;ve assembled your content in a DITA map, you can publish it to multiple outputs simultaneously, depending on your XML authoring tool. Some of the standard outputs include PDF, EPUB, Kindle, HTML and online help systems.<\/p>\n<p>If you&#8217;ve created some <a class=\"hooked\" href=\"\/2017\/03\/03\/structured-writing-part-5-applying-dita-elements\/\">conditional attributes<\/a> for things like product, version or audience, you select these options during the publishing step. For example, in my previous blog post, I gave an example where three products all had the same instructions called &#8220;How to Verify Package Contents.&#8221; A fourth product had an additional instruction. To add the variation for the fourth product, you&#8217;d apply the product conditional attribute to the specific element that includes the additional instruction. Then when you publish the fourth product&#8217;s instructions, you&#8217;d select that product in the conditions option. The results would look like this:<\/p>\n<table border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tbody>\n<tr>\n<td style=\"width: 213px;\"><strong>Products A, B and C<\/strong><\/td>\n<td style=\"width: 213px;\"><strong>Product D<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"width: 213px;\"><strong>How to Verify Package Contents<\/strong><\/p>\n<p>Verify the package contents before you begin.<\/p>\n<ol>\n<li>Open the box.<\/li>\n<li>Find the packing slip.<\/li>\n<li>Compare the contents to the packing slip.<\/li>\n<\/ol>\n<p>Now you&#8217;re done verifying package contents.<\/td>\n<td style=\"width: 213px;\"><strong>How to Verify Package Contents<\/strong><\/p>\n<p>Verify the package contents before you begin.<\/p>\n<ol>\n<li>Open the box.<\/li>\n<li>Find the packing slip.<\/li>\n<li>Compare the contents to the packing slip.<\/li>\n<li>Enter your product codes into our database so we can send you product updates.<\/li>\n<\/ol>\n<p>Now you&#8217;re done verifying package contents.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>So you can write content one time but add variations to it and then select those options during the publishing step. This is a big cost savings if you translate your content because once you&#8217;ve translated the core instructions, you only have to send the variations out to translation. In this case, you&#8217;re sending 14 words instead of 46. You can have a big cost savings.<\/p>\n<h5>Style Sheets Define the Formatting<\/h5>\n<p>XML authoring programs come with standard style sheets, or <a href=\"https:\/\/www.w3.org\/Style\/XSL\/WhatIsXSL.html\" target=\"_blank\" rel=\"noopener noreferrer\">XSLTs<\/a> (Extensible Stylesheet Language Transformations), which defines styles for each element in the DITA standard and each output type. You can modify the style sheet to apply your company&#8217;s styles such as font types and colors, but it does take some coding skills.<\/p>\n<h5>Conclusion<\/h5>\n<p>There are a lot of publishing options for XML-authored content such as selecting content from a variety of files and being able to publish to multiple outputs.<\/p>\n<p>Structured writing is a complex topic because it can be applied in so many different ways. In this series of blog posts, I&#8217;ve focused on how to apply structured writing in terms of technical content using a XML-based authoring program, but there are many more applications. This is my last blog post in the series on structured writing and I hope you&#8217;ve enjoyed the series.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Once you&#8217;ve created some XML content using DITA, you&#8217;re ready to publish the content to one or more outputs. The building blocks for publishing are the XML files, a DITA map and a style sheet. XML authoring programs offer a range of publishing options. Let&#8217;s look at how this works. Assembling the Content Using a [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":3803,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[280],"_links":{"self":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/3802"}],"collection":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/comments?post=3802"}],"version-history":[{"count":6,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/3802\/revisions"}],"predecessor-version":[{"id":29334,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/3802\/revisions\/29334"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media\/3803"}],"wp:attachment":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media?parent=3802"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/categories?post=3802"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/tags?post=3802"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}