One specific bit of advice in there that I disagree with is keeping just one vault. Rather, I find that having one vault per topic/project is the right approach.

The reason for having multiple vaults is simple: I find that the usability of the one big über-vault drops off sharply if you're not disciplined in maintaining organisation, and a consistent workflow, and, if you're storing a bunch of disparate things in a single vault, an organisation/workflow that's universal enough to encompass everything rapidly becomes a pain in the arse to maintain. Inversely, topic-specific vaults tend to rapidly develop their own bespoke structures and workflows that match the topic closely and are very natural to work in.

For example, I have a large vault dedicated to Blue Prince (the game). As in several hundred megs worth of screenshots, over a hundred individual .md files (most of which are almost empty, but their existence is helpful in itself), folder structure that groups information on a per-puzzle basis, and it features pervasive use of tags to encode game features)

Another vault is a cookbook. I don't cook by recipe all that often, so that one mostly has reference tables for cooking times/temps for different foods in different appliances (I don't cook pearl barley often enough to remember how much liquid to use and what rice cooker programme to set).