Skip to main content

Enterprise Documentation Taxonomy

Summary

The taxonomy assigns each page one primary content type and any number of tags. A primary type determines structure and reader intent; tags provide secondary discovery facets.

Audience

  • Documentation authors and reviewers
  • Product owners, developers, QA engineers, and architects

Reference Content

TypeReader intentTypical content
ConceptUnderstand a domain ideaDefinitions, relationships, boundaries
ExplanationUnderstand why or how a system behavesDesign rationale and contextual analysis
TutorialLearn through a guided sequenceEnd-to-end learning path
How-ToComplete a specific taskPrerequisites, steps, validation
ReferenceLook up stable factsCatalogs, fields, states, mappings
ArchitectureUnderstand system structureContext, components, data, integrations
RunbookOperate or recover a serviceControlled procedure, validation, escalation
TroubleshootingDiagnose a known symptomCause, safe resolution, validation
Business ProcessUnderstand a verified workflowActors, states, decisions, outcomes
APIIntegrate through a service contractOperations, request/response, errors
DatabaseUnderstand persistence ownershipEntities, relationships, retention, lineage
EventsIntegrate asynchronouslyProducers, consumers, semantics, versioning
UIUse an approved interfaceNavigation, fields, states, accessibility
OperationsAdminister and monitor safelyConfiguration ownership, health, jobs

The portal’s current content_type vocabulary remains backward compatible. concept covers explanation and business-process pages until those types are added to enforced templates; reference covers API, database, events, and UI reference when a specialized type is not yet enforced.

Use only one primary type. If a page tries to serve several intents, split it and connect the pages through metadata and links.

See Also

Keywords

  • Content taxonomy
  • Reader intent
  • Documentation types

Revision Information

  • Status: Draft
  • Last reviewed: 2026-07-15
  • Review cycle: Quarterly