Navigation being of the essence, there needs to be an API and a UI to allow admin and editors to control how the content is to be navigated by the end user.
Also, a lot of people will want to integrate Orchard with existing sites, or else migrate existing sites to Orchard.
The navigation modules on the gallery are locked down to essentially using the thinking of the designer of the module. For developers used to working with navigation structures provided by the sitemapprovider (or derived thereof) this is frustrating to say the least.
Ie, people have existing code that they want to reuse.
A more powerful approach would be to create a module that allows editors to structure the content to allow it to be exposed using a sitemapprovider. That way, it can be consumed by plain asp.net or asp.net mvc sites, a bit along the "One ASP.NET" thinking that is, we are told, written into ASP.NET Version Next.
awrigley created: https://orchard.codeplex.com/workitem/18701
Navigation being of the essence, there needs to be an API and a UI to allow admin and editors to control how the content is to be navigated by the end user.
Also, a lot of people will want to integrate Orchard with existing sites, or else migrate existing sites to Orchard.
The navigation modules on the gallery are locked down to essentially using the thinking of the designer of the module. For developers used to working with navigation structures provided by the sitemapprovider (or derived thereof) this is frustrating to say the least.
Ie, people have existing code that they want to reuse.
A more powerful approach would be to create a module that allows editors to structure the content to allow it to be exposed using a sitemapprovider. That way, it can be consumed by plain asp.net or asp.net mvc sites, a bit along the "One ASP.NET" thinking that is, we are told, written into ASP.NET Version Next.