If you're new to the DotNetNuke world, in the area of skinning, (and modules but we're not covering that here) there are some differences in the behaviour and implementation of skins. Some of the differences are subtle, but the skins design here for free download have been created/updated/managed to be true DotNetNuke 3 skins, and what this means is that trying to install on an earlier version - eg. DNN2 will throw an error. The reason for this is the key area of DotNetNuke's success in skinning is the way it creates *skin objects* - functions that implemented into a html file by using what is called TOKENS. These are single word instructions like [LOGIN] [USER] [MENU] that are place ONCE ONLY (no duplicate entries here) and when uploaded to the server, are then parsed (executed) and the DotNetNuke references are then applied.But for all these references, how are they read? What happens to them? When read in the address bar - such as the one you're reading now, they are aspx files - that's the actual output name for the files using the .NET technology, which DotNetNuke is based on.. Standard, non dynamic files will have .html extensions and are the most commonly used in static web page design by website developers who do not do dynamic websites. (dynamic - run using server sided technology that allows for faster pages, database managed or extra scripting that involves more than pictures and words on a page) These TOKENS cannot be made up. They need to exist as part of the DotNetNuke infrastructure. Some of these TOKENS are new to DotNetNuke 3 and some have had a name change to grow into better management of a site, and therefore, if you attempt to use a DotNetnuke 3 skin in a different version, it can't find the file and will throw an error which is usually a red line of text at the top of the page, and the default skin showing because it cannot complete displaying the page. The skins provided here have the [SEARCH] function to take full advantage of the new features of DotNetNuke. Skins provided here are written in ascx mode, it's a more advanced mode, but as a free skin that's what I have time to do. If you write skins in htm/html mode, which is often a good place to start, you need to provide the xml code if you wish to customise a skin. I will cover this more in an article shortly.