Reusing Orchard's Core to build another extensibility framework

Topics: Core, Customizing Orchard
Jan 16, 2012 at 8:50 PM

I am very keen to hear opinions on this.

We are building an extensible architecture for web applications. We have a core team that builds the default product. Other dev teams take the default product and want to override/replace/extend its functionality at the code level.

We are considering using Orchard's Core to achieve this.

If we did it would probably consist of:

  • Removing everything CMS related from Orchard
  • Stripping out Orchard's database
  • Using/building on Orchard's core DLLs to create the extensible capabilities we require

One alternative to this is vanilla ASP.NET MVC extensibility.


Jan 17, 2012 at 12:19 AM
Edited Jan 17, 2012 at 12:20 AM

Orchard's core modular framework is certainly very flexible and you could build a lot of things with it. *But* you might end up having to reinvent some wheels unnecessarily if you completely strip out both CMS and database, a ton of Orchard's extensibility is designed around those two features (e.g. Migrations, Multi Tenancy, Content Parts, Placement, you will lose all those lovely extension points...) Your definition of what "CMS" means and what features you can potentially build with it might not be as loose as Orchard's. The Content Management is designed for overriding/replacing/extending functionality and UI.