intelligent content solutions
Not quite. The purpose of the <img> is to house the image itself – referred by href, keyref or both (if the keyref can’t be resolved, the Open Toolkit can use an href as fallback so that you don’t end up with a blank space). The <fig> element is meant to hold the image itself, […]
While you can define a lot of table behaviour such as column widths within DITA itself, that approach can potentially create complexities when it comes to publishing the content, and also limit the flexibility of the content for multi-format publishing purposes. Tables that force a change in page orientation add complexity to a stylesheet, and […]
The <section> element is a great example of why DITA requires us to think and write differently. In an unstructured environment, a section can mean whatever you want it to mean – it is a handy way of describing the chunks of a document without really defining what those chunks are. For writers starting to […]
In its simplest form, abstract does exactly what you’d expect — offers a long-form summary to the topic. You can use abstract very much in the way it is used in traditional print materials. The Abstract element allows more complex markup than shortdesc, that is, there are more elements that the content model allows within […]
Used wisely, the <shortdesc> element is a great way to offer sneak peaks into a topic – useful if you need progressive revelation or have ‘readers that don’t read’. In any topic, <shortdesc> element sits between the <title> and <body>. As a general principle, its purpose is to tell the user what the topic is […]