Topic types
Every topic has a type that describes its purpose. Type is metadata — it doesn't change how content renders.
Type | Purpose | Typical content | When to use |
|---|---|---|---|
Concept | Explanations, overviews, background | Paragraphs, diagrams, lists of key points | Explaining what something is, how it works, or why it matters |
Task | Step-by-step procedures | Numbered steps, prerequisites, expected outcomes | Guiding a user through an action they need to perform |
Reference | Look-up information | Tables, parameter lists, API specs, configuration options | Providing structured data users scan rather than read start-to-finish |
Custom | Anything else | Content that doesn't fit the three standard types | Tutorials, FAQs, release notes, or mixed-format content |
A good rule of thumb: if the reader's goal is to understand, use Concept. If the goal is to do, use Task. If the goal is to look up, use Reference. When in doubt or mixing goals, use Custom.
Setting the type
Set the topic type from the Properties panel in the editor. The default type for new topics is Concept.
Type in the topic list
Topic type appears as a badge on the Topics listing page. Filter by type to find all reference topics, all tasks, etc.
Type in DITA export
When exporting to DITA, the topic type determines the DITA element:
Topicary type | DITA element | DITA specialization |
|---|---|---|
Concept |
| Concept specialization |
Task |
| Task specialization (strict) |
Reference |
| Reference specialization |
Custom |
| Base topic type (unspecialized) |
See also
Create and manage topics — how to create topics and set their type
The topic-map-publication model — how topics relate to maps and publication targets
Export as Markdown or DITA — topic types determine the DITA element used during export
Glossary — definitions of topic, map, component, and other key terms