http://forums.asp.net/16.aspxDiscuss and debate ASP.NET application designs. <a href="http://aspadvice.com/SignUp/list.aspx?l=8&c=17" target="_blank">Email List</a>enCommunityServer 2007 SP1 (Build: 20510.895)http://forums.asp.net/thread/1473882.aspxWed, 22 Nov 2006 18:18:47 GMT4c671506-2930-414c-a40b-8bf57ded5924:1473882flanakinflanakin0http://forums.asp.net/thread/1473882.aspxhttp://forums.asp.net/commentrss.aspx?SectionID=16&PostID=1473882Personally, I'd consider using a tool like <a class="" href="http://www.dotnetnuke.com/">DotNetNuke</a>, which already has all of this built in. This way, you can give them as little or as much control as you want and all you have to worry about is getting it setup. I admit that DNN can sometimes be a pain to get up and running the first time, but this is usually just because of not doing things correctly. Once you get experience with the product, it's almost second nature. While DNN doesn't have everything and there's probably a lot that could be done better, I try to look at it as a great starting point. If you want something changed, you can do it yourself.http://forums.asp.net/thread/1473767.aspxWed, 22 Nov 2006 16:39:04 GMT4c671506-2930-414c-a40b-8bf57ded5924:1473767BitShiftBitShift0http://forums.asp.net/thread/1473767.aspxhttp://forums.asp.net/commentrss.aspx?SectionID=16&PostID=1473767<p>I have a need to allow a few individuals in different departments of our company to edit content on our website.&nbsp; However, I want to enforce a common theme / style over each area.&nbsp; One paticular department has one main page with links to about 50-60 other static pages, each with dozens of links.&nbsp; One approach ive thought of is to replace each of the static link pages with an xml file that contains the links for that section, then have only one aspx page that lets them choose the area they want, which then loads the links from the related xml file.</p> <p>&nbsp;</p> <p>ideas ?</p>