Loading config files from several places is a poor design

[Dennis Williamson]

From https://netplan.io/faq#why-netplan

"Using netplan gives a *central location* to describe simple to complex networking configurations that function from Desktop to Server and from Cloud to IoT. Specifically, for systems with networkd, this *relieves the user* from having to configure up to *three different files* per device or configuration." [emphasis mine]

From https://netplan.io/reference#general-structure

"... All /{lib,etc,run}/netplan/*.yaml are considered. Lexicographically later files (regardless of in which directory they are) amend (new mapping keys) or override (same mapping keys) previous ones. A file in /run/netplan completely shadows a file with same name in /etc/netplan, and a file in either of those directories shadows a file with the same name in /lib/netplan."

The latter paragraph contradicts the former. It also doesn't parallel the case in which configs follow a central/user/local pattern (/etc, ~, .) or similar (e.g. /usr/{,local/}bin or /etc/sudoers{,.d}, et cetera).

I think that netplan YAML files should kept in places that follow established familiar patterns instead of being scattered to the four corners.