The art of skinning is subjective and sometimes generates as much 'controversy' as the argument of using notepad to create your projects or using a fully fledged program. Many of the discussions are centred around the background of the person who has embarked on the job of 'theming' their project.
While this site is primarily for skinning your DotNetNuke application, you'll find that there may be the introduction of other applications, modules. CMS products as we explore the concept of 'theming' which is another popular term for taking an application or program and adding your own themes to it.
We have a mixture of users with DotNetNuke and by nature this causes a direct conflict as users with different experiences in their own field look at the DotNetNuke framework and try to grasp the concept of skinning within their own skill level.
DotNetNuke has a unique and multi layered learning curve and there are times when you will be frustrated and annoyed about the fact it doesn't really do everything. That shouldn't come as a surprise but one of the primary reasons I have persisted with this application for close to 4.5 years now is that there isn't an open source product that comes close to delivering the standards in which we can develop solutions as a whole.
Some of the frustrations that an 'xhtml' purist will will experience is the application will not appreciate the fact that DotNetNuke is NOT xhtml compliant by default and does in fact require plenty of work to get it even close. More than that - start using most of the modules and there goes your xhtml compliant website down the drain. And before you blame DotNetNuke, there are some other influences that may stop your site from receiving the 'holy grail of xhtml' compliance. The framework in which DotNetNuke runs is not completely there yet. It's getting closer with the release of the .Net 2 framework, and now, with the .Net 3 framework not far away from general adoption, it is helpful to know that the importance of development, design and compatibility are getting closer than they ever have been.
Some of the specific areas to learn about 'what makes a good skinner' is listed below, and while they are only my own opinions, they really haven't changed much over the last few years, based on the research and time spent on the forums where I've picked up some common 'habits' by newcomers - that is new to DotNetNuke.
They may be completely proficient in their own areas of design or web development, but the mix of product knowledge and broad knowledge will influence how quickly someone will pickup skinning techniques.
The key elements to become a good DotNetNuke skinner are -
- Understanding the DotNetNuke Framework
- Understanding HTML
- Not everything that goes wrong can be blamed on DotNetNuke
- Understanding XML
- If you choose to code using the HTML method of skinning you will need to have an understanding of XML as this influences the output extensively.
- Understanding CSS
- You don't have to to be an expert and sometimes the more you know about CSS when beginning to work with DotNetNuke can be almost detrimental as your expectations of what can be done by default may not work.
Other benefits that might assist you in being a great DotNetNuke skinner are -
- Understanding Photoshop
- You don't have to be a graphic designer but having knowledge about Photoshop could help you in making quick changes when the final skin 'tweaks' are required to complete your project.
- Understanding ASCX
- By that I mean being familiar with working with code to put in perhaps more detailed and advanced skinning techniques that are not possible using the html / xml method of skinning. An example would be when attempting advanced Solpart Menu enhancements that required addition to the code through the ascx file which is created either manually or through the skinning engine process when using the html/xml method of skinning.
- Highly advanced skinning techniques are not possible through using html/xml alone.
So these are the basic skills you'll need to know to become proficient in creating DotNetNuke skins.
Once you master these, DotNetNuke is perhaps the most rewarding framework to work with. You can go from 'zero to hero' in a very short time, even if you've only done minor tweaks on an already existing skin - as many do, to impress your customers and colleagues. There is NO application available that offers this depth of 'theming' and 'selling the sizzle' and once you do get past the learning curve, it's really alot of fun and very rewarding.
Nina Meiers