Pull Skinr styles into skin sets

Yep this is definitely on our roadmap. I've covered it a bit in presentations and we've started a library here: http://fusiondrupalthemes.com/snippets

This new architecture will also make it much easier to swap out and share grids, change styles for different sections of the site, disable skins you're not using, etc etc.

Until things change more with how packaging works on d.o, this is more difficult (it's already a challenge enough for new Drupal users to install the dependencies for a Fusion theme), but we do plan to do more with styles in the sites/*/skins dir as Skinr 2.x/D7 stabilizes as well.

We will focus on this for the D7 branch next and then backport some to a Fusion 2.x for D6.

This is a great idea and should definitely be pursued where possible. It's something we've wanted to see in the Skinr community and the fusion Skins would be a perfect start. It does raise some items to be discussed as well (some of which should really be their own issues in other queues:)

1. It's likely that some of the skins might not be easy to be made standalone without the theme. Specifically in relation to grids. Not that there couldn't be standalone skins that implement or support the 960 grid system, but it would likely be a challenging area. Hopefully I can be proved wrong there.

2. Should those skins or skin sets be made into proper modules that Drupal and Skinr recognize or should they just be the skin folders to be added to /sites/all/skins or sites/foo/skins.

3. If the skins are broken out so they can reside in sites/all/skins for instance, how and where are those to be contributed and distributed. I assume we could create d.o projects for individual skins or skin sets and tag them with "Skinr, Skins, or Skin-set" but we have to consider if it would be polluting the project space. Ideally there would be another project type for Skins, but I think Skinr adoption will have to increase some more before a new custom project type is added to d.o for them. Also, we'd need to figure out what level of adoption should be required before a custom project type would be added on d.o?

4. The skin-set projects would need to provide specific instructions as to where to put the skins and noting what differentiates them from normal modules. That way it's easy for newbies or designers and themers to know to just drop the skins in to the proper location and that's it, they are done.

Thats it for now, thanks for your thoughts!

Looks like we posted around the same time, re-fixing the version.

Thanks for your additional thoughts! Looking forward to helping brainstorm and push this initiative.

Re #3: I've noticed several modules that could actually be skin sets :)

Tons of stuff happening with this in Skinr lately, and we will be updating the Drupal 7 version to use the new Ctools-based Skinr sets. .info files will no longer be supported in 7.

Need to review exactly where these are going to go in the D7 release.

This is fixed in theory from Fusion's end (skins you're not using can be disabled, like modules), as the new skin format has been committed to Fusion. But, the enabling/disabling through the UI is not working yet in Skinr.