Hi all,

I'm new here, and have started a project to implement a DotNetNuke website. We have a client that want's to use an image map as a front-end and then subpages will have the standard menu navigation system. We can display the image on the homepage, but we'd like to disable the viewing of the menu system, because that's what the image will map to. I can accomplish this by using a pretty basic hack outside the content management system, but I'd like to know if there's a more elegant way to implement an image map front-end that links to a standard dotnetnuke menu interface and still be editable from the standard content management system.

Any ideas would be greatly appreciated,

Sam

Thanks Chris for your prompt reply,

Regarding your solution, is it possible to have a unique skin for just the homepage? Once you drill down past the imagemap homepage into the other subsections of the site, you have a typical dotnetnuke look and feel with the defaut skin. Can you have a website using multiple skins and still be editable without a problem within the content management system?

Appreciate the help,

Sammer

Every page in the portal can have a different skin applied if this is needed. This is actually one of the strengths of the DNN skinning solution.

hth

Bruce