13 Aug 2007
15 Nov 2011
Link to this post
Sorry you're running into me again...
Well you're right, Sitefinity themes operate similarly to ASP.NET themes, its either the one or the other. Just to make sure we're on the same page, Sitefinity uses different themes for the backend and the frontend. So when you're starting with a new theme, the backend (Sitefinity management bits) won't loose its styling.
You could also copy/paste the existing basic theme to your own theme and enhance/delete anything from there, using the basic theme as a starting point.
However using basic first and then overriding with new styles leads to double styling/clutter and results in heavy loading and sometimes glitches. (basic themes floats left for instance but you override it to float right)
Wrapper classes are unavoidable, whatever option you take. Just for fun set your font-size in the body tag to 20px and go look at what it affects. Wrappers are an intricate part of modern web design so you won't be able to avoid them.
I'm sure soon some ecommerce themes will show up on the Marketplace. With the recent release of v4.3 they've finalized the checkout process and introduced the department widgets so its just a matter of time before someone will use them in a template.
I think most people start from scratch, with a blank theme and gradually build the entire site from there. Everyone has their unique idea on how a site should look and client taste often differs between sites. Firebug's (Mozilla's awesome web developers extension) css panel will be your biggest friend.
Create the style rules you need and copy/paste in whatever you like from the basic theme. This will make sure you've got the smallest and most optimized style set for the project.