4.4 skin strategy
 

we're about to upgrade an old site to 4.4.
so the skin needs to be completely redone.

typically we end up swapping skins a couple of times a year: for easter, christmas, halloween, seasons etc, so I need a better way of doing things. We used to swap the whole skin1 folder for each change, but because that included static page content, we would often end up with old delivery info, permissions problems, and duplicated files, wasting space.

ideally I'd like just the layout components that changed each season, in a folder, and call that css folder after the main one, so it would override the default settings.

would that work? is there an easy way of doing it? what do others do?

I had done my first dev install of 4.4 using one layout, but then decided I wanted to build upon a 3 column layout instead of 2 column. I couldn't see an easy way of upgrading the skin, so I ended up doing the whole installation again, purely to get to the skin selection section.
Is there another way of swapping the whole skin, with 4.4?

cheers
Chris

Re: 4.4 skin strategy
 

ok. just logged in to the backend and saw the new section for swapping skins.

tried swapping back to 2 column, and lo and behold, it appended a line to the css:
<link rel="stylesheet" type="text/css" href="/skin/2-columns/css/altskin.css" />

Getting there.