Group items tagged

If a help ID should provide a list of related topics, those topics are shown as separate <relcell> entries in the corresponding <relrow>:

<relrow id=”h4444444″>

This encoding approach takes care of the DITA source side of the context-sensitive help. You’ll need to build a DITA Open Toolkit plugin that processes the relationship table and creates the appropriate mapping files.

What is a content strategy? A content strategy reveals who the end users are, the goals they are pursuing and what tasks they must do to reach the goals. The content strategy explicitly describes what type of information end users need to do the tasks, which gives us the content to include and not include in a manual and how to organize it to make content searchable. A content strategy shall answer a number of questions (for example, open the document via link "information design questions" On http://www.sesam-info.net/planning.htm). The answers are sometimes referred to as the information model.

The content strategy shall also deal with areas such as metadata, reuse strategy, creation and release processes, publishing mechanisms, content ownership and responsibility, tools etc.

Let us elaborate two types of content creation organizations within the technical communication domain: Explicit and implicit organizations.  In the implicit organization there are no content strategy written down. Each member (technical writer, SME etc) has their own view on what content they believe end users need. In the best of worlds these views are aligned without the members having discussed it. In other implicit organizations an information designer has taken the role to plan and design the content (together with the team or not). But the strategy and principle that the information designer is following may not be communicated or understood by the technical writers or SMEs. So the information designer has to be consulted every time a new manual is developed or a macro content change is proposed in an existing manual. In explicit organizations the strategy and principles are written down and communicated.

Content that is personalized, easily found, appropriately scoped, and pleasant to interact with has a name: Adaptive Content

content should adapt to the reader as well as to the device.

Among its high points for alignment with direct-to-Web content delivery solutions, DITA provides: Close affinity to Web page writing conventions and length Intentional similarity of inner content markup names (p, ul, ol, dl, etc.) A close match in its title, short description, and body structure to the way most Web CMS tools manage their content. Maps that work so very well for representing collections of content.