My builds classically look something like this (1 x home and 1 x settings root node), and I know I'm not alone. I'd be interested in exploring putting site config in its own section, as they are generally for a different type of editor. I'm thinking more about config-based values (e.g. Google Analytics ID) rather than shared content such the footer or blocks. I'm aware that Umbraco comes with some in-built security to control access, but I feel a separate section would be better UX. Has anyone ever done anything like this, or have a view on how it could be best achieved without fighting the system too much. https://cdn.discordapp.com/attachments/1197122072200085564/1197122072372072469/image.png?ex=65ba1dcf&is=65a7a8cf&hm=ca0c46883fbe05c1ae2ba326e636213948b546283f53600ed4255d7f96ac2b93&

You could do this with Umbraco UI Builder and setting it all up in a seperate section while storing the values in a database table. I'd probably still use the content section though, it comes with a lot of niceness out of the box that will take a while to remake. And with content start nodes you could limit access for certain user groups anyways

That's a pretty decent point (where the licensing allows). A custom table is perhaps more suitable where it isn't content.