I am really excited about the skin set feature in skinr 2.0 and and wondering how everyone is thinking they will use it.
With skinr 1.5 I tended to create 2 types of skins:
- My everyday set - These were common elements I used all the time, such as rounded corners, menu styles, typographical changes, etc...
- 2) Site specific block/panel-pane/view styles - I would take all of the elements of a specific commonly used block type on a particular site and have a set of items for that site, sort of like the sites own style library. I put an example skin set like this at the fusion code snippet library page http://fusiondrupalthemes.com/snippet/skin-set/social-media-block
Along with how I break these up I am also thinking of how to organize my skin set broad categories - That I am planning on using as the skin group...
I currently am putting all of my skin sets in the following buckets:
- Administration
- Blocks
- Layout For layout and and Formatting
- Lists
- Menus Primary and secondary menu formatting
- Tabs I have a large set of these so wanted to separate them
- Typography For Typography & Font Stacks
I was also thinking of adding one for specific module formatting, but am undecidedt. Currently, when formatting things like views calendar, I include the css overrides directly into the style.css of my theme. I think that modularity could be added to these if they were stored in the skins folder. I have not tested that idea yet, and currently don't use skinr for this, but if anyone has how has it worked out?
So that is three questions in one, but I would love to get feedback on the above, and/ or find out how everyone else is doing this!