The category tree is not only navigation—it is an evolving structure. Versioning records how that structure changes over time so you can understand what was published when, and support audits or investigations that ask “what did the help desk look like then?”.
What counts as a structural change
Typical events include adding or renaming sections, reparenting a subtree, reordering siblings, or removing a node. Each meaningful change can advance the version so the platform keeps a coherent history.
How this differs from article edits
Article updates change page-level content; tree versioning captures where articles lived in navigation and how sections were organised. Both matter for compliance: the policy text and the path users took to find it.
Readers see the current tree
The help desk reflects the current published structure. Historical versions are for administrators and auditors reviewing past layouts—not for replaying old navigation to end users unless your product workflow explicitly supports that.
Operational tips
- Batch large reorganisations in a maintenance window and communicate renames that affect bookmarks.
- Keep section titles stable when possible; prefer adding a child section over renaming broad folders during peak traffic.
- Pair tree changes with article review so moved content still reads correctly in its new context.