· Chris Hammond
Last Updated
I skinned a Community Server site, what a pain!
Learn about the challenges of skinning a CommunityServer website vs. DotNetNuke for a fresh design. Discover the differences in ease and functionality.
I've skinned, or tweaked a CommunityServer site before, but what I must admin, it's definitely not an easy process, and not something I'd want anyone to have to go through!
I just skinned Solo2.org The Ultimate Autocross Web Site tonight to get change the design. Skinning within CS has to be one of the biggest pain in the rear things to do. I've skinned many a DotNetNuke site, and though the Solpart Menu can be rather tricky, no skinning project with DNN has ever been as hard as it was just to make some simple changes to CommunityServer to make Solo2.org look like it does now. I realize Telligent says they've made skinning easier with their new release for 2007 (everyone and their mother has blogged about it over the past 4 days, twice) but I can't imagine skinning getting much easier than the skinning engine that DotNetNuke has implemented.
"Here here" to the guys (core team) who developed that engine nearly three years ago now!
I've still got a lot of work left to do with s2o, but at least it's not the plain jane site it used to be a few hours ago. Oh yeah, I actually started working on this skin for CS back in October, I quit working on it after 2-3 tries, until tonight when I crunched through the rest of it.
Take a look at the site, let me know what you think.
*disclaimer: I may be a little biased towards DotNetNuke, being my position within the DNN Team, but I do use CommunityServer on two of my largest websites, https://sccaforums.com/ and https://solo2.org/