Leyse

The .SkinObject class in the file Default.css is the one that will affects the Search, Date, Breadcrumbs, Login, Register, Copyright, Terms, Privacy.

Since you are using VS.NET it would be easier to work directly on the .ascx file rather than HTML as ultimately those are parsed and converted to .ascx anyway, but the placeholder injecting dynamic content like date, login, menu, content etc. used for HTML and .ascx are different, for example in an HMTL file you would use [LOGIN] token and speicfy the details of that token in the XML file and for an .ascx file you spcify the @Register and user contol tag in your skin file itself, like so... <dnn:Login runat="server" id="dnnLogin" />

To get a comprehensive reference to CSS go to http://www.skinningtoolkit.com/

Read an overview of Skinning at
http://www.dotnetnuke.com/About/WhatAreModulesandSkins/SkinningandGraphicDesign/tabid/469/Default.aspx

also download the Skinning Guide and Navigation WebControls Documentation at
http://www.dotnetnuke.com/About/Documentation/ProjectDocuments/tabid/478/Default.aspx

This will help you understand the concepts much better. If you get stuck with something again then post those questions and we will try to help as much as we can...

Changes to the DNN skinning to allow more uniform management through less files means that by default all skinobjects such as the login, currentdate, user, copyright, etc are managed by the .skinobject class.  If you add a .skinobject class to your file it will override the one that exists in the _default/portal.css file. ( I believe that is the correct one by memory)

This does cause some problems with multi coloured skins so for simplicity I suggest you put in two classes like I do for my work - I call one LightBG and one DarkBG and assign the class accordingly, easily and quickly and then I don't have to bother going back to modify the ones that don't work right.

It's also pretty easy to remember.

Nina Meiers