Technical writers call this "information architecture". Hierarchical organization is tough. E.g. if you're working on a docs site, and you have a multi-level n

Technical writers call this "information architecture". Hierarchical organization is tough. E.g. if you're working on a docs site, and you have a multi-level nav, what's the best way to organize that nav? Same problem with organizing the directories in a company's intranet. One idea that is influential within the technical writing community is to "treat every page as page one" [1]. Because of Search, you never know how people will first access your docs. So you always structure every page to handle one topic, and only one topic, thoroughly. And then link profusely to other docs that the user might be interested in. [1] https://everypageispageone.com/the-book/ https://everypageispageone.com/the-book/