Not sure if anyone has suggested this or not, but I think this would make a great option for the blogs.

Do you mean for individual users making their own custom blog skins, or for the standard IP.Blog skin? It already will include everything for IP.Blog recolored the same way as everything else.

Do you mean for individual users making their own custom blog skins, or for the standard IP.Blog skin? It already will include everything for IP.Blog recolored the same way as everything else.

Yes, for the individual user.

Would it be possible to let someone create and import a skin that only has ip.blog customizations but without the IPB part of it? Mainly for giving members more blog skins to choose from without there being more skins overall, to cut down on space used.

Would it be possible to let someone create and import a skin that only has ip.blog customizations but without the IPB part of it? Mainly for giving members more blog skins to choose from without there being more skins overall, to cut down on space used.

Not really - it depends on what skin is being used by the board in question. If they aren't using the default skin (or a variation of it), it's unlikely anything the skin generator makes would work.

I don't mean to add in with an existing skin per say, but just be a skin that would only be for giving members another choice in the blog (since the admin can pick which skins the members can choose from for their personal blog).

I don't mean to add in with an existing skin per say, but just be a skin that would only be for giving members another choice in the blog (since the admin can pick which skins the members can choose from for their personal blog).

I agree with Wolfie. It sounds like a great idea. :)

That's not something that has anything to do with the Skin Generator, though.

Actually it does.

If you could let someone generate a color and only generate the necessary template bits/css/images for the blog, then someone could create skins for use with blogs only, but not for the rest of the board.

And that's not what the skin generator does. So no, it doesn't have anything to do with the skin generator.

It's a suggestion for making it possible to let someone do that with the skin generator.

But the skin generator changes css files, it doesn't make blog skins. If you wanted to play that card, you should expect it to make IP.Content templates. It doesn't, and won't.

As it stands, the best thing to do what you want would be to make the skin, export it, import it to your board and set it as child of the IPB default. Let members select, then you have 'blog-only' skins.

What would be the difference of creating a skin with it, importing it into IPB, then choosing to export and only choosing the blog and importing only the files generated from doing that?