I was asked to give a short presentation on Umbraco at a Microsoft Innovation Center (MIC) in Belgium. I was invited by a pro-Microsoft and SharePoint aholic and was asked to mention Orchard compared to what Umbraco can propose.
Orchard is MVC-based while the current version of Umbraco is Web Forms-based. Though important that consideration is (Umbraco 5 is being refactored in MVC), Orchard is described as Module-oriented where everything can be plugged in while Umbraco is package-oriented.
Could you help me to make the distinction clear? I do not want to denigrate Orchard, but I'd like to better understand the point of view of the Umbraco community concerning the conceptual difference Module - Package.
I'm not really sure what you're looking for here. A Module is a way which Orchard allows external functionality to be packaged up and added to any site, in the same way that a Package works for Umbraco.
One of the main distinctions between Umbraco and Orchard (or any other CMS really) is that Umbraco is really unstructured about how to go about adding functionality. There's a few things to be done when adding something like a new Umbraco application (implementing a Tree for example) but generally speaking there's not a lot of enforced standards.
What I am looking for is some information that contrast Orchard and Umbraco based on what I read from the Orchard website and my own experience of Umbraco. There is an interesting debate where Niels took part of:
As I said I was invited to present Umbraco and one Microsoft's alternative. I want to figure out in what areas both CMS are different. I mean with accurate words.
When I was learning Umbraco I read some good tutorials and one of them (wrote by a core team member) touched on the fact that module-based approach is fine in terms of facility but more complex to program and to start off. This echoes what you said above: "Umbraco is really unstructured about how to go about adding functionality".
Always cool to have the opinion of a core team member :p
Umbraco and Orchard: Module vs. Package
I have been using Umbraco for a few months.
I was asked to give a short presentation on Umbraco at a Microsoft Innovation Center (MIC) in Belgium. I was invited by a pro-Microsoft and SharePoint aholic and was asked to mention Orchard compared to what Umbraco can propose.
Orchard is MVC-based while the current version of Umbraco is Web Forms-based. Though important that consideration is (Umbraco 5 is being refactored in MVC), Orchard is described as Module-oriented where everything can be plugged in while Umbraco is package-oriented.
Could you help me to make the distinction clear? I do not want to denigrate Orchard, but I'd like to better understand the point of view of the Umbraco community concerning the conceptual difference Module - Package.
Thanks.
Roland
I'm not really sure what you're looking for here. A Module is a way which Orchard allows external functionality to be packaged up and added to any site, in the same way that a Package works for Umbraco.
One of the main distinctions between Umbraco and Orchard (or any other CMS really) is that Umbraco is really unstructured about how to go about adding functionality. There's a few things to be done when adding something like a new Umbraco application (implementing a Tree for example) but generally speaking there's not a lot of enforced standards.
Does that elaborate on what you're looking for?
Thanks for answering Slace.
What I am looking for is some information that contrast Orchard and Umbraco based on what I read from the Orchard website and my own experience of Umbraco. There is an interesting debate where Niels took part of:
http://weblogs.asp.net/bleroy/archive/2010/08/05/orchard-0-5-is-out.aspx
As I said I was invited to present Umbraco and one Microsoft's alternative. I want to figure out in what areas both CMS are different. I mean with accurate words.
When I was learning Umbraco I read some good tutorials and one of them (wrote by a core team member) touched on the fact that module-based approach is fine in terms of facility but more complex to program and to start off. This echoes what you said above: "Umbraco is really unstructured about how to go about adding functionality".
Always cool to have the opinion of a core team member :p
Its probably past your talk, but for others who stumble upon this topic, take a look at this series by Aaron:
http://www.aaron-powell.com/orchard-umbraco
is working on a reply...