Database controlled CMS Plugin Architecture
Posted: Wed Jun 03, 2009 8:25 am
This thread extends the one in General chat regarding plugin architecture. Didn't want to hijack.
I'm writing a new CMS for our company and I want to be able to add new plugin modules as and when.
To start off with I'm going to have blog, news, page content editor plugins but I want to be able to extend the number of plugins depending on which site I'm using the CMS with.
I also want to have this controlled by the database so that ultimately we can centralise our client's CMSes and control them from one location eg, add/remove features.
Has anyone ever done anything similar or got any tips on how to implement this?
I've got a few hazy ideas at the moment myself but could do with some input.
I'm writing a new CMS for our company and I want to be able to add new plugin modules as and when.
To start off with I'm going to have blog, news, page content editor plugins but I want to be able to extend the number of plugins depending on which site I'm using the CMS with.
I also want to have this controlled by the database so that ultimately we can centralise our client's CMSes and control them from one location eg, add/remove features.
Has anyone ever done anything similar or got any tips on how to implement this?
I've got a few hazy ideas at the moment myself but could do with some input.