That's one way to do it, yes. Depending on what you want to do with those entities you might want to make them simpler objects, but making them content items will certainly work. It really is a question of how much you want to do with them, how much composability and extensibility you want, etc.
From: Gideon D'souza [mailto:[email protected]] Sent: Friday, June 10, 2011 9:04 AM To: [email protected] Subject: About contentITems for a new module. Hey, So I'm hoping to make a simple module here for a quizzer. Something like an author can create a quiz with N mutiple choice questions and mark the answer. An authenticated user will visit a page with a list of quizzes. He can pick one and it will display each question and score this user, also then it will keep record of the scores. Now I read a bunch of tutorials on orchard, but I'm still a wee bit confused how I'll define some of the data. Would everything be content items? I don't want orchard to throw up its own UI to create any of these objects, I want to have a separate admin menu on the dashboard which would allow a user to add and remove questions to a quiz. Also I would need a scores table. Would this also be a content item? (By this I mean would all of my models like Quiz, Question and Score derive from ContentItem?) Regards, Gideon --- You are currently subscribed to orchard-discuss as: [email protected]<mailto:[email protected]>. To unsubscribe send a blank email to [email protected]<mailto:[email protected]>. --- You are currently subscribed to orchard-discuss as: [email protected]. To unsubscribe send a blank email to [email protected].
