Internal Wiki and Knowledge Base Writing (English)
Practice the vocabulary and best practices for writing internal wikis and knowledge bases: structure, discoverability, and maintenance.
0 / 8 completed
1 / 8
What distinguishes a 'knowledge base' from a 'wiki' in a corporate context?
While often used interchangeably, knowledge bases typically have more structure and editorial oversight (especially customer-facing ones). Wikis tend to be open, collaborative, and grow organically.
2 / 8
What is a 'single source of truth' (SSOT) in documentation strategy?
SSOT means each fact, process, or decision has exactly one canonical source. Duplicating documentation causes drift — one version gets updated and the other doesn't, leading to conflicting information.
3 / 8
What is 'information architecture' in the context of an internal wiki?
Information architecture determines whether your wiki is findable. Poor IA means useful content exists but nobody can find it. Good IA uses clear naming, consistent structure, and logical groupings.
4 / 8
What does 'orphaned page' mean in a wiki context?
Orphaned pages exist in the wiki but are not linked from anywhere. They are invisible to users browsing the wiki unless they search specifically. Regular wiki audits should identify and link or archive orphaned pages.
5 / 8
Which principle should guide the 'freshness' of a knowledge base article?
Knowledge bases degrade if not maintained. Displaying last-reviewed dates and flagging stale content (e.g., 'This article was last reviewed 8 months ago — verify before following') maintains reader trust.
6 / 8
What is 'progressive disclosure' in knowledge base writing?
Progressive disclosure shows summaries first and lets readers drill down for details. A wiki article might start with a one-paragraph summary, then provide a detailed guide in expandable sections.
7 / 8
What is the purpose of 'tagging' or 'labels' in a wiki or knowledge base?
Tags allow cross-cutting categorization. A page about 'deploying to production' might be tagged with both 'deployment' and 'on-call-runbook', making it findable via either tag even if its location in the wiki hierarchy is under 'operations'.
8 / 8
Which sentence is an example of good knowledge base article writing?
Good knowledge base articles are actionable: numbered steps, specific commands or actions, expected outcomes. Vague references to other pages or team leads create friction and defeat the purpose of a knowledge base.