Modulated Templated CMS system

[eluser]a&w[/eluser]
Thanks. I'm getting a better picture now. Thanks for elaborating so well. Please note, that I think in Post#2 your directory structure is different, hence my seeking clarification on the structure. Your 'home' folder is not inside 'modules'.

I had not even considered nesting the modules folder, where you've shown it being a child folder. Interesting. Not sure when it would ever come to practice, but good to know.

What is the difference between modules::load and modules::run? A cursory look at the code looks like run also loads the module passed.

With reference to the line below, do you check if data['current_action'] isset in your index method of the controller then?

Code:

$this->data['current_action']=$method; //used inside my modules

This next part is probably application specific, nonetheless, anything interesting to note with the following snippet?

Code:

$content = ($module=='admin')?modules::run($module, $this->data, $method):modules::run($module, $this->data, 'index');  
        }
        else
        {
            redirect('');
        }

I didn't quite follow you when you say you use a custom library to load all the options inside the data array upon initialization and then just array_merge. I'm a bit rusty on CI (took a sabatical for a few months learning javascript), but I thought when libraries were loaded, CI automatically checked for a similarly named config file. Seems like there would be a way befitting of the "CI way" to have the modules check for a config file and to load that. So when a module is loaded, go ahead and load the config array associated with it. Not sure if that would connect to the module, or maybe one of the views.