Create (imitation) Skin in DotNetNuke == (very) easy

As every Web Applications, every object related to appearance (html, image, css, ...) in DotNetNuke is transfered to client.
It will make easy for making imitation Skin/Container from a Site Powered by DotNetNuke

How about Legality aspect ? Hhhhmmm....

For example in my site at http://www.sudirman.biz
There are some Skins in fact imitation Skin/Container from a DotNetNuke sites.

Let's look at http://home.sudirman.biz/sdr-vista-windows-s

It imitates http://packaged.salaro.com/vistawindows/Home/tabid/394/Default.aspx

What about http://www.microsoft.com/windows ?

How to ::

• visit a site that has interesting Skin/Container
• Save Page as... (Html file)
• Use Frontpage for analyzing. "Reformat HTML" feature helps a lot.

Next ::

• create 2 files (skin.xml and container.xml) according to Html file.
• Example of skin.xml and container.xml could be seen at standard Skin/Container of DotNetNuke installation

How is it too easy ?

• Hhhhmmm... all about Web Application. Every object is transfered to client (of course it is. So, how to make a fancy appearance if thas is not ?).
• But there is another factor that accelerates making imitation Skin/Container. That is Component Oriented of ASP.NET. That characteristic will help us decide, whether a HTML block is DotNetNuke Module or can be placed in skin.htm file

Challenge :

• Possible because of Save Page as... by Browser, .css file can have image. For example "background-image: url(images/m_bg.gif);" then we should take that image from the site manually. The file location should be accessed relative to the .css file. ex. /Portals/_default/Skins/SDR_s002_2/skin.css. m_bg.gif is in /Portals/_default/Skins/SDR_s002_2/images/m_bg.gif
• Creating skin.xml file. When to use RootMenuItemRightHtml in [MENU]