Reputation: 196539
i have a website where i want to allow the users to manage the content. There are a few main pages:
i want to allow non tecnical users the ability to format and change the content in the welcome page (almost like its a blog or a wysiwyg WIKI to the user) but i want this content (the resulted html) to be included in the website.
any best practices for this?
Upvotes: 0
Views: 532
Reputation: 30234
You asked about best practice, and if you are interested in best practice I would recommend you download a decent content management system (Umbraco is a good .NET CMS) and use that.
If you want to do something quick and dirty, that's possible too. Like you said you can easily use something like TinyMCE or FCKeditor to knock up an app with the functionality you require, allowing users to update certain pages. (Note with a CMS you could achieve this by controlling access to certain pages anyway).
If you were after the simplest solution (that money can buy :P), you could even look at an out of the box solution like Adobe Contribute for example.
Upvotes: 1
Reputation: 65391
You need a Content Management System (CMS). You can combined published pages with programmed pages. Or place web controls on published pages so that you get a page that combines published information with programmed functionality.
If you go for a free solution I would recommend dotnetnke http://www.dotnetnuke.com/
Another alternative is to store the texts in a table. Allow the users to go to "edit mode" to change the texts. Each place where a text is used must have it's own ID which is the key used in the table.
We have used both of these approaches on projects, both have worked fine.
Upvotes: 1
Reputation:
Have you looked at the microsoft open source asp.net MyWebPagesStarterKit? [http://mywebpagesstarterkit.codeplex.com/]
Upvotes: 0
Reputation: 3768
What you need is a CMS. A collection of free and free-ish ASP.NET CMS systems is available at opensourcecms.com, but there are good COTS options as well.
You definitely don't want to get into the business of writing your own quasi-CMS for this one project: you'll waste a lot of time on figuring out how to make a friendly UI, store and manage the content, sanitize input, etc. Those wheels have already been invented ;)
Upvotes: 1