Diff for What is your DITA Quotient (D.Q.)?
Fri, 2008-04-18 01:14 by Bob Doyle | Fri, 2008-04-18 01:19 by Bob Doyle | ||
---|---|---|---|
< previous diff | next diff > | ||
Changes to Body | |||
Line 12 | Line 12 | ||
</p>
| </p>
| ||
<p>
| <p>
| ||
- | You will receive a printable list of your answers, which outline the main DITA capabilities.
| + | You will receive a printable list of your answers, which outline the main DITA capabilities and provide a checklist of your priorities for DITA.
|
</p>
| </p>
| ||
<h3>
| <h3>
| ||
Line 20 | Line 20 | ||
Do you manage your content using a content management system?</em>
| Do you manage your content using a content management system?</em>
| ||
</p>
| </p>
| ||
- | <p>
| + | <ul>
|
- | <br />
| + | <li>
|
- | Yes <br />
| + | Yes</li>
|
- | No<br />
| + | <li>
|
- | </p>
| + | No</li>
|
+ | </ul>
| ||
<h3>
| <h3>
| ||
Is structure important?</h3>
| Is structure important?</h3>
| ||
Line 30 | Line 31 | ||
<em>
| <em>
| ||
Do you structure your content? Do you have an information architecture (e.g., a taxonomy)? Do you have a document architecture (e.g., content model)? </em><br />
| Do you structure your content? Do you have an information architecture (e.g., a taxonomy)? Do you have a document architecture (e.g., content model)? </em><br />
| ||
- | <br />
| ||
- | Information architecture and document architecture<br />
| ||
- | Information architecture (e.g., taxonomy)<br />
| ||
- | Document architecture (content models)<br />
| ||
- | Unstructured content<br />
| ||
</p>
| </p>
| ||
+ | <ul>
| ||
+ | <li>
| ||
+ | Information architecture and document architecture</li>
| ||
+ | <li>
| ||
+ | Information architecture (e.g., taxonomy)</li>
| ||
+ | <li>
| ||
+ | Document architecture (content models)</li>
| ||
+ | <li>
| ||
+ | Unstructured content</li>
| ||
+ | </ul>
| ||
<h3>
| <h3>
| ||
Is content reuse important?</h3>
| Is content reuse important?</h3>
| ||
Line 41 | Line 47 | ||
<em>
| <em>
| ||
How much of your content gets reused in other contexts?</em> <br />
| How much of your content gets reused in other contexts?</em> <br />
| ||
- | <br />
| ||
- | A lot<br />
| ||
- | Some<br />
| ||
- | A little<br />
| ||
- | None<br />
| ||
</p>
| </p>
| ||
+ | <ul>
| ||
+ | <li>
| ||
+ | A lot</li>
| ||
+ | <li>
| ||
+ | Some</li>
| ||
+ | <li>
| ||
+ | A little</li>
| ||
+ | <li>
| ||
+ | None</li>
| ||
+ | </ul>
| ||
<h3>
| <h3>
| ||
Is single-sourcing important?</h3>
| Is single-sourcing important?</h3>
| ||
Line 52 | Line 63 | ||
<em>
| <em>
| ||
Do you publish content to multiple output formats and channels (e.g., web/HTML and print/PDF)? </em><br />
| Do you publish content to multiple output formats and channels (e.g., web/HTML and print/PDF)? </em><br />
| ||
- | <br />
| ||
- | Yes <br />
| ||
- | No<br />
| ||
</p>
| </p>
| ||
+ | <ul>
| ||
+ | <li>
| ||
+ | Yes</li>
| ||
+ | <li>
| ||
+ | No</li>
| ||
+ | </ul>
| ||
<h3>
| <h3>
| ||
Is translation/localization important?</h3>
| Is translation/localization important?</h3>
| ||
Line 61 | Line 75 | ||
<em>
| <em>
| ||
Is your content multi-lingual? </em><br />
| Is your content multi-lingual? </em><br />
| ||
- | <br />
| ||
- | Yes <br />
| ||
- | No<br />
| ||
</p>
| </p>
| ||
+ | <ul>
| ||
+ | <li>
| ||
+ | Yes</li>
| ||
+ | <li>
| ||
+ | No</li>
| ||
+ | </ul>
| ||
<h3>
| <h3>
| ||
Do you markup your content?</h3>
| Do you markup your content?</h3>
| ||
Line 70 | Line 87 | ||
<em>
| <em>
| ||
Does your content have metadata? </em><br />
| Does your content have metadata? </em><br />
| ||
- | <br />
| ||
- | Semantic, structural, and style tags <br />
| ||
- | Structural and style tags <br />
| ||
- | Style/format/presentation/layout tags only<br />
| ||
</p>
| </p>
| ||
+ | <ul>
| ||
+ | <li>
| ||
+ | Semantic, structural, and style tags</li>
| ||
+ | <li>
| ||
+ | Structural and style tags</li>
| ||
+ | <li>
| ||
+ | Style/format/presentation/layout tags only</li>
| ||
+ | </ul>
| ||
<h3>
| <h3>
| ||
Is your content modular?</h3>
| Is your content modular?</h3>
| ||
Line 80 | Line 101 | ||
<em>
| <em>
| ||
Is your content created in small chunks/topics? </em><br />
| Is your content created in small chunks/topics? </em><br />
| ||
- | <br />
| ||
- | Yes. (content is readable in any order, like help topics) <br />
| ||
- | No. (content is long linear narrative)<br />
| ||
</p>
| </p>
| ||
+ | <ul>
| ||
+ | <li>
| ||
+ | Yes. (content is readable in any order, like help topics)</li>
| ||
+ | <li>
| ||
+ | No. (content is long linear narrative)</li>
| ||
+ | </ul>
| ||
<h3>
| <h3>
| ||
Is your content conditional?</h3>
| Is your content conditional?</h3>
| ||
Line 89 | Line 113 | ||
<em>
| <em>
| ||
Do you serve different content to different audiences?</em> <br />
| Do you serve different content to different audiences?</em> <br />
| ||
- | <br />
| ||
- | Yes <br />
| ||
- | No<br />
| ||
</p>
| </p>
| ||
+ | <ul>
| ||
+ | <li>
| ||
+ | Yes</li>
| ||
+ | <li>
| ||
+ | No</li>
| ||
+ | </ul>
| ||
<h3>
| <h3>
| ||
Is your content task-oriented and minimalist?</h3>
| Is your content task-oriented and minimalist?</h3>
| ||
Line 98 | Line 125 | ||
<em>
| <em>
| ||
Do you follow these documentation best practices? </em><br />
| Do you follow these documentation best practices? </em><br />
| ||
- | <br />
| ||
- | Minimalist and task-oriented <br />
| ||
- | Task-oriented <br />
| ||
- | Minimalist <br />
| ||
- | Neither<br />
| ||
</p>
| </p>
| ||
+ | <ul>
| ||
+ | <li>
| ||
+ | Minimalist and task-oriented</li>
| ||
+ | <li>
| ||
+ | Task-oriented </li>
| ||
+ | <li>
| ||
+ | Minimalist </li>
| ||
+ | <li>
| ||
+ | Neither</li>
| ||
+ | </ul>
| ||
<h3>
| <h3>
| ||
Is standardization important?</h3>
| Is standardization important?</h3>
| ||
Line 109 | Line 141 | ||
<em>
| <em>
| ||
Do you want to use practices that are shared in your industry/profession? </em><br />
| Do you want to use practices that are shared in your industry/profession? </em><br />
| ||
- | <br />
| ||
- | Yes <br />
| ||
- | No.
| ||
</p>
| </p>
| ||
+ | <ul>
| ||
+ | <li>
| ||
+ | Yes</li>
| ||
+ | <li>
| ||
+ | No</li>
| ||
+ | </ul>
| ||
What is your DITA Quotient (D.Q.)?
The idea behind the DITA Quotient is a rough but quantitative numerical estimate of the applicabilty of DITA to your content. You simply answer ten questions and get an estimate of the value of DITA for your organization.
DITA News will publish the average numbers for everyone filling in the questionnaire, so you will be able to compare yourself to others. And we will track the average answers for the ten questions over time, to see how DITA is being adopted and how its various capabilities are being utilized.
Below is the questionnaire content. The questionnaire is anonymous. No information about your organization is collected.
To estimate your D.Q., fill in the online form at DITA News.
You will receive a printable list of your answers, which outline the main DITA capabilities and provide a checklist of your priorities for DITA.
Is content management important?
Do you manage your content using a content management system?
- Yes
- No
Is structure important?
Do you structure your content? Do you have an information architecture (e.g., a taxonomy)? Do you have a document architecture (e.g., content model)?
- Information architecture and document architecture
- Information architecture (e.g., taxonomy)
- Document architecture (content models)
- Unstructured content
Is content reuse important?
How much of your content gets reused in other contexts?
- A lot
- Some
- A little
- None
Is single-sourcing important?
Do you publish content to multiple output formats and channels (e.g., web/HTML and print/PDF)?
- Yes
- No
Is translation/localization important?
Is your content multi-lingual?
- Yes
- No
Do you markup your content?
Does your content have metadata?
- Semantic, structural, and style tags
- Structural and style tags
- Style/format/presentation/layout tags only
Is your content modular?
Is your content created in small chunks/topics?
- Yes. (content is readable in any order, like help topics)
- No. (content is long linear narrative)
Is your content conditional?
Do you serve different content to different audiences?
- Yes
- No
Is your content task-oriented and minimalist?
Do you follow these documentation best practices?
- Minimalist and task-oriented
- Task-oriented
- Minimalist
- Neither
Is standardization important?
Do you want to use practices that are shared in your industry/profession?
- Yes
- No