Practice knowledge base taxonomy vocabulary: category hierarchies, article sections, role-based tagging, related links, and taxonomy governance.
0 / 5 completed
1 / 5
The content team designs a ___ hierarchy to organise all KB articles into parent and child categories.
A category hierarchy is the taxonomy backbone of a knowledge base — a tree structure where broad parent categories (e.g., 'Account Management') contain more specific children (e.g., 'Password Reset', 'Billing'). It determines the main navigation.
2 / 5
A contributor asks: 'Which section does this article belong to?' They are asking about the article's ___ assignment.
A section or category assignment determines where an article appears in the KB navigation. Miscategorised articles become invisible to users who browse by section rather than searching, making correct taxonomy assignment critical.
3 / 5
The KB platform uses ___ to help users filter articles by their role — administrator, end user, or developer.
Tags are metadata labels that add dimensions beyond the category hierarchy. Role-based tags (admin, end-user, developer) let users filter to articles relevant to their context, improving discoverability without restructuring the category tree.
4 / 5
The style guide requires every article to include ___ links to at least two related topics.
Related links at the bottom of an article point readers to connected topics — prerequisites, follow-up steps, or alternatives. They improve user flow through the KB and reduce dead-end experiences where a user gets an answer but needs the next step.
5 / 5
The documentation lead establishes ___ governance to prevent ad-hoc tag and category sprawl.
Taxonomy governance defines who can create new categories or tags, how they are named and described, when old ones are merged or retired, and how the hierarchy evolves. Without governance, taxonomies degrade into unusable clutter over time.