Reputation: 34257
I have requirement to make parts of a dynamic web page that includes header, footer, menu, content and buttons. I require all of them to be editable/non-editable once i turn on/off editing from admin side.
I already know that DotNetNuke already does that for the developer. I like to know what are the merits and demerits if we do it without using DNN. I like to discuss this. Thanks
Upvotes: 0
Views: 1484
Reputation: 66641
Actually this dynamic editing is done with javascript on client side.
I can suggest a nice jQuery code that make editable part of the page with a click. The rest is to handle the save of this edit using some ajax calls. Very nice and simple
Look here a working demo :
http://www.appelsiini.net/projects/jeditable/custom.html
and get the code from:
http://www.appelsiini.net/projects/jeditable
Upvotes: 2
Reputation: 2851
Take a look at ASP.NET Web Parts. MSDN quote:
In a Web application scenario, you could offer a complete solution for end users to manage and personalize the application. This could include a set of Web Parts controls that provide the desired features for the site, a consistent set of themes and styles that allow end users to personalize the UI in a consistent way, catalogs of Web Parts controls from which users can select the ones they want to appear on a page, authentication services, and role-based management (for example, allowing administrative users to personalize Web Parts controls and site settings for all users).
Upvotes: 1