Right -- the min/max/none is probably something that could be in all containers, but on some elements DNN gives the skinner the choice.

Some tokens give you spacing problems if they are disabled by the user (doesn't the print produce a nasty nobackspace?), so in some cases skinners make separate versions of each container. I have what I call "compact" or "no container" versions of my containers that give you only the menu.

In another instance, I don't include the "banner" token where I'd rather let the user insert whatever they want there. Maybe the user doesn't want banners, but on pages where they do, just use the banner module which works much better. It's hard to make a skin that allows both, or you have spacing issues.

The "logo" token doesn't usually work well either, especially if you want to use two or more different skins in a single portal. Or maybe the logo/header is in Flash. In this case, you really can't install the skin as host if you want each portal admin to be able to upload/replace their own flash header or logo.

I've actually made a skin that doesn't have the solpart menu, for accessibility reasons. Or many you want to use Flash for the menu...

It's really up to the skinner to tell you what they are doing, allow you to test the skin, give screenshots, before you buy.

---

Jason Honingford - Web & Software Developer
www.PortVista.com

I know what you're saying, there are really bad skins out there selling for really low prices. I'm sure a lot of designers would get into the market if they could sell each skin for $500+ but in order to do that, there must be some way to prove to customers you really put the time into designing the skin. This review program is only a start, but they got to start somewhere.

---

Jason Honingford - Web & Software Developer
www.PortVista.com