I don't see why not. Just establish a dependency between the features in the manifest.
-----Original Message----- From: Mauro Servienti [mailto:[email protected]] Sent: Thursday, November 11, 2010 8:26 PM To: [email protected] Subject: RE: Trying to understand something Hi Bertrand, first of all thanks for the response, yes Articles are Pages, so we do not need another content type, we can use that or even extend it from the dashboard. For the relation Section/Category we were wondering if it's possible to have this kind of relation (one-to-many) between stuffs in different modules, and if it makes sense. Cheers, .m ___________________________________ Mauro Servienti | Microsoft MVP - Visual C# MCTS /MCPD | IM: [email protected] -----Original Message----- From: Bertrand Le Roy [mailto:[email protected]] Sent: venerdì 12 novembre 2010 00:45 To: [email protected] Subject: RE: Trying to understand something Also, you might want to check this out as it seems fairly close to what you're trying to do: http://orchardchapters.codeplex.com/ -----Original Message----- From: Bertrand Le Roy [mailto:[email protected]] Sent: Thursday, November 11, 2010 12:02 PM To: [email protected] Subject: RE: Trying to understand something Hi, Articles look very much like pages. I'm not sure why you'd need a separate type for that. Documentation on shapes is coming but for the moment, you can watch the latest screencast (http://orchardproject.net/LiveMeetings/Latest/Orchard.0.8.Screencast.mp4). Lou's part has a great demo of shapes. To create one to many relationships, you can follow the example of blogs to blog posts, or posts to comments. Does this help? -----Original Message----- From: Mauro Servienti [mailto:[email protected]] Sent: Thursday, November 11, 2010 5:54 AM To: [email protected] Subject: Trying to understand something HI, sorry for the subject, but we are currently trying to extricate ourselves from the Orchard jungle :-) Let's start trying to define our scenario: we need to build a "site" on top of Orchard, currently it's a spike to investigate the platform, defining these three main concepts: - Articles: an article is basically a page really similar to a blog post, has comment, tags, routing; - Categories: a category is an hierarchical aggregator of articles; - Sections: a section is a flat non-hierarchical aggregator of categories, has routing and menu support as we need a section to appear in the main menu; The first thing we did has been to build a "Sections module" and a "Categories module" (using Shapes: is there any docs that deeply discuss Shapes & Drivers?), currently we have those modules running and from the dashboard we can manage Sections and Categories. Now the first question is: which is the best way to create a one-to-many relationship between Sections and Categories? And obviously which steps should we follow to integrate the two editors? Regards, .m ___________________________________ Mauro Servienti | Microsoft MVP - Visual C# MCTS /MCPD- | IM: [email protected] --- You are currently subscribed to orchard-discuss as: [email protected]. To unsubscribe send a blank email to [email protected] --- You are currently subscribed to orchard-discuss as: [email protected]. To unsubscribe send a blank email to [email protected] --- You are currently subscribed to orchard-discuss as: [email protected]. To unsubscribe send a blank email to [email protected] --- You are currently subscribed to orchard-discuss as: [email protected]. To unsubscribe send a blank email to [email protected]
