I just sat thru your Issue 28 videos. I didn't expect to learn much since I had just completed builting an xhtml compliant skin and container from your previous issues, especially issue 25.

It is interesting that we have gotton to the same place, but by different means.

You were overriding the settings from "default.css" in this skin because your content used different classes than DNN.

I had had difficulties in a previous skin making changes to list formating and some other items. Also that "Normal" is really important.  My solution was that I included much of default.css in my skin.css and modified it to my liking. This in effect override it. I also use DNN's classes where ever possible. To this css code-base I added new classes as required.  This section of css moves from skin to skin along with my data now since the data is dependant on these classes.

I used the H1-H3 container as the basis for my xhtml containers. I have placed all of the css in the skin.css since border colors etc. should match the skin.

In the skin.css I have a layout section at the top with the pane layout followed by the classes followed by a container section followed by a @media print {} section.

/DaveS

i had same problem i haven't watch latest tutorials yet but i had to move common classes to skin.css in order to make it work.

But i will look for better way.

I am actually considering hacking out parts of DNN's default.css, so that they don't get ing the way. I had real problems with lists (ul & ol) getting the margins reasonable and that was the reason that I copied sections into my skin.css. They still aren't right. I bet if I deleted them from the default.css and defined them as I wanted them, I'd be better off. An experiment for another day.

/DaveS

If you do go that route, saving a copy of the "hacked up" default.css is something that you'll want to do. It will be overwritten if you update.

Yes backup, backup, backup! -  I must admit, if I am creating a skin for a client I will just completely strip out the default.CSS file and set what I need in the skin.CSS file instead of having to play around with overriding settings.

- this is great if you are controlling the website, but of course it will cause problems if your client takes over and wishes to install other skins on the portal.

I keep a copy of most if not all files related to the skin that I have changed in the skin directory. This includes original vector artwork for the logo, favicon, gradients and I would certainly keep default.css.

And as Lee says "backup backup" I have zip files, including the database .bak file, of my production site on a daily or weekly basis for over a year. I can always roll them out on my localhost and recover a file or two if needed. My ISP maintains a few as well, but I don't count on them for more that a night or two.

The data that I find hard to keep track of is items that are changed with the languare editor such as "terms" and the 100's of possible email and other messages. Currently I just keep a list of the ones that I have edited so that I can migrate the changes to new versions of DNN.

/DaveS