Im developing a .net CMS, the main problem with my current system is that someone setting up a site needs to know asp.net / have access to the code to implement the design.
I want to seperate the design html from the master page - so i will create a dynamic master page loading in the html layout, finding content areas from keywords in the html and allow the user drop user controls into these areas.
( ie replicate what is done on graffitti cms )
i dont know if i should create a physical master page ( ie when they put in their UC's as save the template - save a page.master on the server or should i serialise the object and its settings and dynamically add the necessary user controls when a page is requested.
As you can see im still at an earlly stage - but basically i want to seperate the design from the .net code and allow the user controls to be configured fro the backend -any properties that they expose can be set in the admin area.
Any recomendations / info would be great.