Project Description
Using the zevenseas Classic Theme solution, you can enable the 'old' functionality of SharePoint themes to your site. Using this, you have control over the .css and images you want to include.. just like the theming engine in SharePoint 2007 and 2003..

Who is a fan of the way how themes were being used in SharePoint 2003 and 2007? I know, I am! In my opinion the theming support in SharePoint 2010 is ok but it lacks the the level of customization which could be achieved by the previous implementation of themes in SharePoint. What you might wonder, first and foremost you had the ability of creating your own .css file. Next, while adding the theme to your SharePoint farm, you could apply the theme to every site in your farm (the question there is, do you want that in the first place, but that’s a whole other topic ;).
You could have the option of using the AlternateCSS, but that option is only available in publishing environments which means that it’s not available for SharePoint foundation environment. Plus, maybe you don’t want to enable the publishing features on a collaboration site. You might wonder.. ok Robin.. now what? Well, luckily the good ‘ol theme engine of 2003/2007 is still available (on the filesystem, in the API) we only need a way of exposing this in the UI. So that’s why I developed the Classic Theme solution! Great Scott!
So what does it do then..
1. Gives you the ability to apply a theme to your site
2. Gives you the ability to administer which themes are available in which webapplication
3. Gives you the ability to deploy your custom theme in a supported way (by not overriding the spthemes.xml file)
If you are reading my blog in the last couple of years than you probably know that I created a solution already to support bullet no2 and 3 ( so it was just a matter of blowing the dust off that solution, make it ready for SharePoint 2010 and add the functionality to apply an ‘old’ theme to your site.

Last edited Aug 21, 2010 at 9:28 AM by robin_meure, version 2