Practice vocabulary for DITA (Darwin Information Typing Architecture) and structured writing: topic types, content reuse, and information architecture.
0 / 8 completed
1 / 8
What are the three primary DITA topic types?
DITA's three base topic types: Concept (understanding), Task (doing), Reference (looking up). This separation forces information architects to categorize content by reader intent — understanding vs. doing vs. finding.
2 / 8
What is 'content reuse' in DITA and structured writing?
DITA enables single-source publishing: write once, publish many. A 'Logging Configuration' task written once can appear in the Installation Guide, Quick Start Guide, and Admin Manual. Update it once, and it updates everywhere.
3 / 8
What is a 'DITA map'?
DITA maps are the composition layer. A 'User Guide' map references 20 concept, task, and reference topics and defines their structure. The same topics can be referenced in different maps for different publications.
4 / 8
What is 'conditional text' in DITA?
Conditional (profiling) text uses DITA attributes like @product or @audience. During publishing, you set conditions: include content where product='enterprise', exclude where product='community'. This enables one topic set to produce product-specific outputs.
5 / 8
What does 'chunking' mean in DITA output?
DITA's granularity (one topic per file) needs chunking to produce usable output. Web output often combines related topics into one page; PDF output merges everything. Chunking strategy affects SEO, navigation, and reader experience.
6 / 8
What is 'information typing' in structured writing?
Information typing is the foundation of structured writing. Robert Horn's Information Mapping and DITA both use typing to prevent 'mixed' content — a single page that is part tutorial, part reference, part concept. Typed topics are more reusable and scannable.
7 / 8
What is 'docs as code' and how does it relate to structured writing?
Docs as code brings engineering rigor to documentation: changelogs, branches, reviews, automated tests (broken link checking, style linting). It enables developer contributions and co-locates docs with the code they describe.
8 / 8
What is the difference between a 'tutorial' and a 'how-to guide' in the Diátaxis framework?
Diátaxis distinguishes by intent: tutorials build competence through structured learning (the reader may not understand why at each step). How-to guides assume competence and help accomplished users solve real problems. Mixing them creates confusion.
This exercise, "DITA and Structured Writing (English)", tests your understanding of technical writing vocabulary and phrasing through 8 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 8 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this Technical Writing exercise for?
It's designed for IT professionals and learners who want to sound natural discussing technical writing topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more Technical Writing exercises?
Browse the full Technical Writing exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.