<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.8.2" -->
<rss version="0.92">
<channel>
	<title>Author Max: Great DITA, Great Documentation</title>
	<link>http://methodm.com/blog</link>
	<description>for people who write and edit content everyday</description>
	<lastBuildDate>Wed, 28 Dec 2011 11:03:01 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>The DITA Project #11:  Book map or DITA map?</title>
		<description>Bookmaps enable users to organize their DITA information into front matter, parts, chapters, and back matter. Typically, publications are created from a bookmap while DITA maps are used for simpler documents, or to group topics for reference from a book map or from another DITA map.
Group topics in DITA maps
  </description>
		<link>http://methodm.com/blog/2011/12/28/the-dita-project-11-book-map-or-dita-map/</link>
			</item>
	<item>
		<title>The DITA Project #10: Group topics in DITA maps</title>
		<description>The DITA Project #10: Group topics in DITA maps
Referring to DITA maps from a book map or from another DITA map provides a great way for grouping topics. Refer to the DITA map in the bookmap whenever you want to include the collection of topics in the bookmap.
 
Tip: You ...</description>
		<link>http://methodm.com/blog/2011/12/07/the-dita-project-10-group-topics-in-dita-maps/</link>
			</item>
	<item>
		<title>The DITA Project #9: nesting topics under a topic or under a topichead?</title>
		<description>The best practice, in general, is to reference a
 DITA map from the &#38;lt;part&#38;gt; element. This allows easy reuse of the
 collection of topics, and allows editing of the DITA map for the part in
 parallel to editing of the bookmap. In this example the &#38;lt;chapter&#38;gt; element
 references a DITA ...</description>
		<link>http://methodm.com/blog/2011/11/30/the-dita-project-9-nesting-topics-under-a-topic-or-under-a-topichead/</link>
			</item>
	<item>
		<title>The DITA Project #8: when to use the part element in a bookmap</title>
		<description>For publications that have two or more very different kinds of
 information, use &#38;lt;part&#38;gt; to divide a document's chapters into logical
 groupings.
 &#60;note type="other" othertype="Example"&#62;In a document that contains
  both procedures and reference information, you can define two parts, one
  containing the how-to procedures and the other containing ...</description>
		<link>http://methodm.com/blog/2011/11/24/the-dita-project-8-when-to-use-the-part-element-in-a-bookmap/</link>
			</item>
	<item>
		<title>The DITA Project #7: referencing a map or a topic from the chapter? element?</title>
		<description>Referencing a
 DITA map from the &#38;lt;chapter&#38;gt; element enables allows easy reuse of the
 collection of topics in the chapter, and allows editing of the DITA map for the
 chapter in parallel to editing of the bookmap. In this example the
 &#38;lt;chapter&#38;gt; element references a DITA map.
 &#60;codeblock&#62;&#38;lt;chapter href="intro.ditamap" format="ditamap"/&#38;gt;&#60;/codeblock&#62;
In ...</description>
		<link>http://methodm.com/blog/2011/11/17/the-dita-project-7-referencing-a-map-or-a-topic-from-the-chapter-element/</link>
			</item>
	<item>
		<title>The DITA Project #6: organizing topics</title>
		<description>Topics, taken alone, are generally just part of larger units of information.  To organize your topics meaningfully, you can:

	arrange topics into chapters and parts in the bookmap,
	group topics in DITA maps, and
	nest child topics under parent topics (sometimes called super topics, super tasks, or chapter maps).
	nest topics under topic headings

In the coming ...</description>
		<link>http://methodm.com/blog/2011/11/09/the-dita-project-6-organizing-topics/</link>
			</item>
	<item>
		<title>The DITA Project #4 Polygamous or Monogamous Topics</title>
		<description>The DITA Project #4 Polygamous or Monogamous Topics
Embedding multiple topics inside one topic file.  Markers for this phenomenon are use of &#60;title&#62; more than once in a
topic.
The golden rule is one topic, one idea. If you need more than one &#60;title&#62;, with the obvious exception of titles for
images or tables, ...</description>
		<link>http://methodm.com/blog/2011/11/09/the-dita-project-4-polygamous-or-monogamous-topics/</link>
			</item>
	<item>
		<title>The DITA Project #5 choices or choicetables?</title>
		<description>Why use &#60;choices&#62; or &#60;choicetables&#62; instead of &#60;ol&#62; or &#60;ul&#62; in a task topic when you need to choose what to do next?

The benefit is that the markup is semantic!  When you use &#60;choices&#62; or &#60;choicetables&#62;, the machine (and the writer!) understands explicitly if we are talking about:

	&#60;choices&#62; where ...</description>
		<link>http://methodm.com/blog/2011/11/09/the-dita-project-5-choices-or-choicetables/</link>
			</item>
	<item>
		<title>The DITA Project #3: Definition Lists or Tables?</title>
		<description>Writers are conditioned to using tables.

Get past it. Table invite endless tampering with settings for column width.  In most cases, get over it and get past it.  Go for &#60;dl&#62;, definition lists.

The key point here is "most cases". Most, but not all. If it's absolutely critical that you display content ...</description>
		<link>http://methodm.com/blog/2010/09/07/the-dita-project-3-definition-lists-or-tables/</link>
			</item>
	<item>
		<title>The DITA Project #2 Just Say No: when reference topics distract</title>
		<description>To describe a procedure (such as setting up display, removing a panel, etc. ), use a task topic.
To describe what you can do, or what options are available, use a reference topic.

A good rule of thumb is that users tend to need, and prefer, step-by-step procedures in task topics to ...</description>
		<link>http://methodm.com/blog/2010/08/26/the-dita-project-2-just-say-no-when-reference-topics-distract/</link>
			</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.250 seconds -->

