[mmasterson]

@cflsystems I'm confused because the new skin approach starting in 4.4 seems quite a bit different - which appears designed to allow quick swapping between skins.

The way I understand it, files in the customer skin folder (e.g. 2-column) will overide the ones in the common_files folder. Thus, shouldn't a custom skin be implemented by modifying the files *only* in the 2-column (or better yet a copy of that folder) so that the underlying common_files are not changed?

Otherwise there would no way to swap to a different skin quickly due to the changes in common_files that would likely break other skins.