Over the years, the strategy for skins has changed somewhat. In order to reuse skins where I have an 'Enterprise' license I can load them to the host level and reuse them as often as I want.

But customer requirements vary and sometimes I have to tweak the skin or css to provide a certain look for a particular customer.  I used to rename a copy of the skin (which had it's share of problems). But since the portalid-system directory was created, I just load a copy of the skin to the portal skins directory and then modify it as necessary. It works, but it takes up a little bit more disk space.

Is this the optimal way of handling it now on DNN 9.1.1+? Or is there a better way?