I was waiting for this issue and it didn't disappoint me.
The process of moving the content around on the page was easier than I thought. I was wondering if you could have placed all of the absolute positioned items in a single div and just positioned it.
This was a much of a video on skin design as it was on making CSS skins SEO friendly. It was good to see your thought process.
I did notice a couple of items to comment on.
You called content pane “contentpane” while DNN uses “ContentPane”. While IE and FireFox don’t see any difference when displaying, I have been burned when I had JavaScript that was going to operate on the “ContentPane”. It appears that JavaScript in FireFox is case sensitive. As a result I recommend that people name their “divs” with the same case as DNN uses.
On the last video talking about how “skinname.css” only needs the differences from “skin.css”, it reminded me of a question about “print.css”. Does “print.css” only need the diffs, or must contain the whole css file with the few changes that you need for printing like margins, removing the menu, dealing with links etc?
As you were duplicating #dnn_contentpane’s attributes, I was reminded that I find it much better group like items together and just and the id and class names to the list. In fact, for colors I move all of the color statements to a common place and then I can easily tweak them as required.
Again thanks for the great video!
/DaveS - www.agingSafely.com
|