kenticonewbie
-
4/29/2009 3:35:44 PM
We are looking for a better kentico solution for our community site. Need your help!
We are trying to use Kentico Portal Engine to develop a community site for our client. Since we are still new to the Kentico CMS, we would like to hear some suggestions from you guys regarding what would be a better solution for our case scenario.
Here is the basic outline of the project. We are delivering a site that will provide users to submit and share veteran stories. Users do not need to sign up or register as a member to be able to submit stories. The stories won’t be published to the site until they are approved by the administer persons. The administer persons have full access to the submission data and manage them. Breaking the functionality down to the public users and the admin users, the site includes 2 modules:
1. Public site – submit and browse stories module.
The story submission involves two steps: a) Veteran Basic Info submission form – this page allows users to submit veteran’s basic information, including their name, home province, conflict etc.
b) Veteran Story submission form – this page allows users to submit veteran’s story which includes story details (long description) and related artifacts such as story photos, interview audio and even video. We would like to let the users have the ability to upload multiple image files and the images can be automatically resized before uploaded.
Users are able to browse stories sorted by veteran name, conflict and theme etc. and will be able to search for the veterans and their artifacts too.
2. Admin module.
For the admin person, we will try to let them be able to manage the stories submission data through the CMSDesk without developing an external admin tool.
What we want to look into is to know:
1. Does Kentico portal engine provide the flexibility and ability to implement the above functionality without too much .Net coding?
2. What will be a better solution to implement this with Kentico? We tried creating new document types, for example VeteranInfo, VeteranStory, VeteranStoryArtifect, to store the data, but we still don’t how to link them together establishing one to many relationship - sort of like the one to many relationship in the database. And how we handle the submission data in the backend code to store into the CMS database so they are recognized as document type items? Is kentico CMS API a right way to look into to do this?
3. We assume that we will need to create user controls for the story submission. And we will use kentico CMS API to store the data into the right database tables. Is this the right way to go? Could you provide us any of the online references to look at?
4. Does kentico provides a web part to upload multiple images files, retrieve image resolution and resize images before uploading?
|