I've just installed DNN locally to dnndev.me and all is fine.

I've also created a child site under dnndev.me

Looking at the file structure, it appears as though the child works from the same skins and containers as at parent level which is fine.

However, say I want to have a new site with it's own independent set of skins and containers (e.g. so I can customise divs / css for that particular site) I assume I need to create a new website under IIS and do another install?

If that's correct, do I just name the new website anything and it will then work via a localhost URL?

Thanks.

Thanks Clint - but am still trying to get my head around a few details.

I've installed locally as a means to develop offline before deploying to my prod account on remote host server. 

That gets me to the successful install of dnndev.me

Looking at the file structure I can see that the skins directory is located at ...\portals\default level.

Beneath 'portals' I can also see folders for '0' and '1' - which I assume are the original install demo site and the child that I created.

I'd like to leave '0' untouched as a reference site and make changes to '1'.

One change I'd like to make for '1' is to reduce the depth of the skin pane which holds the logo and menu - but I want tot do thisd without affecting the skin in relation to '0'.

If I modify the skin at \default level I'm assuming this will then affect both '0' and '1' - ?

If so, is there a way of applying mods to jsut one site? - if so what's the best practice?

Thanks.