I was very happy about Orchard since from what I read it can be THE cms framework for me. Today I started to play with the latest sources and played on the admin site, and I noticed something what - as I think - is the base for every CMS...It has something
to do with the site structure.
If I get an empty CMS into my hands and like to "invent" a new site, for first I'd like to identify my content types, my content type fields. This is something what Orchard has, so far so good.
As a "next step" I'd like to define the site's logical layout, the "constraints" of how those content types related to eachother, what type can be contained by what type and so on.
1. A site can only have 1 main menu content type.
2. A main menu can contain page, blog, productscontainer, type1, type2, type3 children content types.
3. A productscontainer content type can have only product content types.
And if this structure is ready it's very easy to populate the site with content!
Maybe I am the one who does not see how Orchard approach this aspect of a CMS, or it's not there. Please give some guidance on it!
For first this seems to be a very complex framework, and very hard to locate which parts are responsible for which (MVC) action on the site. Some kind of trace or something should be a great help to locate what module, feature, view, action is responsible
for a given part of the generated view. Whay I'm raising this? I tried to hit Edit on the MenuItem content part and I got a 404...and it turned out that somehow, something is missing from the database for that item...but that was generated by a database query,
so something is wrong there.
(Repro: Manage Content Types -> Content Parts -> hit Edit for Comment Settings, Content, Menu Item, Message Settings, Site Settings, User Roles,
Also I did not found an intuitive way to create a MenuItem content type and add that to the main menu...