This isn't a wiki. The core defining characteristics of a wiki are: Editing, Navigation, Linking, and Searching. Wikis do not have any enforced navigation str

This isn't a wiki. The core defining characteristics of a wiki are: Editing, Navigation, Linking, and Searching. Wikis do not have any enforced navigation structure. Navigation is implicit (defined by Editing and Linking). OneNote, "PerfectWiki", Teams built in "wiki", and many many others rely on a hierarchical page structure to function. This would be fine were it an optional navigation mechanism, but it rarely is. Usually this is also how content is stored and managed. This ultimately makes the content itself VERY brittle to change, very difficult to refactor, and rarely navigable for long term use. It's a much more approachable UI paradigm for beginners, but I have yet to see a large knowledgebase that didn't collapse under its own weight over time when using an enforced tree-structure to content. It's incredibly rare that knowledge fits into a hierarchical taxonomy. Doing so at a UI level creates conflict and cognitive dissonance that accrues over time.