TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: Arguments for NOT using topics as parents to other topics in DITA-maps
Subject:Re: Arguments for NOT using topics as parents to other topics in DITA-maps From:Yves Barbion <yves -dot- barbion -at- gmail -dot- com> To:Martin Jonasson <martinjonassonjobbet -at- gmail -dot- com> Date:Wed, 17 Jul 2013 17:16:55 +0200
Hi Martin
I asked this question in the Yahoo dita-users group. This was the
discussion we had, back in 2007:
Meanwhile, many DITA projects later, I can say that we never use topichead
anymore because there are very good reasons to have a first-level title,
some content and then some second-level titles. We use title-only topics
because we usually include a short description <shortdesc> in the
first-level topics, which you cannot do when you use topichead. Another
good use case for using parent and child topicrefs is when you have a
first-level title, some content, and then some second-level titles which
you all want to appear on the same page in the HTML-based output. In this
case, you can use the @chunk="to-content" attribute.
Cheers
--
Yves Barbion
www.scripto.nu
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.