Hello! This is a great site – I’ve learned much about skinning from here.

I thought it would be a fun little side project to make some commercial DNN skins. I have just completed my first attempt, and as this is the first complete skin package I have made, I’ve decided to give it away for free. To download it, just go to: www.webwhirlers.com/business-sleek/


 
If you do decide to check it out, I would love to hear any comments you might have on it, good or bad.

Does anyone know of a resource on the web that lists the ‘best practices’ when it comes to creating DNN skins? There are a lot of things I am unsure of.

Solpartmenu – It’s a powerful system, but a real mess to work with. I’ve noticed that most commercial skins out there uses this though.You think people would be less likely to purchase a skin If it doesn’t use the solpart menu?

Login, register, etc. – Most skins I have seen puts the login and register links prominently at the top of the design, and that’s what I did for this skin. Personally, for my corporate sites I would prefer a discrete login at the bottom, and no register at all. Any opinions?

Search – I’ve build 500+ websites, and only on a few occasions has the customer requested a search function on their site. Most professional DNN skins seems to have have the search included though. Is this a feature that you feel should be included in all skins?

Pane Structure – I have seen commercial skins with up to 20 panes in one page. This seems to me that it would just make the skin less user friendly. I tried to keep my structure simple, and create a few different templates, rather than one huge one to fit all needs. Is this a bad idea?

Color Variations and Containers – There are skins with dozens of colors and hundreds of containers. Seems to me that this would just be more confusing than anything else. Would you rather spend $30 for a smaller skin that has the color you want. Or $90 for a skin that comes with all this extra stuff?

I had a couple of more questions - if anyone has any input on the following, I would be grateful -

Width of design - many skins has a 100% widht option. Is this necessary? Would you stay away from a skin that only has a fixed width design? Personally, I like fixed designs a lot better, and I've found that my customers overwhelmingly do too. But at the same time I don't want to disqualify my skins by not including a stretching version

Html vs ascx - Is there any advantage of either? I imagine the html might be a little bit easier to edit, but then again, anyone who has enough skill to edit the html should have no problems editing then ascx either? Is there any forward compatability advantages of using html?

Thank you!

hello,

glad to hear the site is of use. - for all of those questions it always depends on the user's requirements. The problem with selling a skin template is that it needs to be flexible for everyone, whereas for a client you can adapt this skin to suit their exact needs.

So, for instance it is probably best to include the features, which then can be removed if the user does not require the search function or requires the login links to be at the bottom of the skin for example.

For pane structure, I would release several skins with different panes structures rather than one skin with a big pane structure.

Solpart menu is used because it is installed as default and it means less configuration for the users, however snapsis sell a license for their menu which allows you to include their menu with your skin as long as it is selling above a certain price, so this could be another option.

Width - This can depend on the users who are editing the content. For a beginner administrator it's wise to give them a fixed width as they are less likely to break the skin design, however for someone who is more experienced it is less likely they will break a fluid width. -   Width generally depends on the client and their own needs and their customers preferred viewing. If you are going to be selling skins, it's probably worth testing a package with a fixed width, a package with a fluid width, and a package with both and see what sells.

HTML etc. - there are no performance differences as HTML file is converted into a ascx - users editing / creating skins may find it easier to work in a HTML file rather than an ascx file as there is less code to read.

Thank you for your feedback Lee!
When looking at all the details of a skin package, I can certainly see the challenges of being a successful skin designer.
Including features and give instructions of how to remove them sounds like a good idea.

I will have a look at the Snapsis menu, and their plan for reselling. Might be a good idea for a bit higher-end skins.

I will try to overcome my personal aversion of fluid designs, and maybe make a few of each.

Thanks!

when i upload new skin. my error is:
Có lỗi nghiêm trọng xảy ra.
Could not find file 'C:\Users\son\Documents\Visual Studio 2008\WebSites\DotNetNuke\Install\Temp\elcwplvg\packagelicense.txt'.

could you help me..!

Thanks !

Can you give a few more details on how you are uploading the skin?

Is this a custiom skin?  Does your manifest refer to the packagelicense.txt file?  If so, is the file part of the skin package?