Libraries or HMVC

[eluser]Colin Williams[/eluser]

but rather the fact that Ajax and MVC do not get along

Worst, most inaccurate, sweeping generalization I've heard on this forum thus far!

I could be wrong though.

Whew! Ok. That's better. It's hard for us to make a good recommendation—and believe me, we want to—with such a vague background of your project.

where each page gets content from several different pages and places it onto the main page

Well, is a page a unit that would be stored in a database? In that case, you just need a single page controller that queries whatever pages you want to display.

If a page is more like a widget, each coming from one of a group of widget controllers, then I think HMVC could be a good architecture for you. Although, using Libraries could work just as well. It just depends on how you want to build it.

I would have a widget controller that, among other things, communicates with a widget model to get the widget instructions, save widgets, etc. The widget controller is the widget hub. Then I would have a widget library that serves as the Widget API, and then a separate library for each widget. The Widget API library, upon loading, would load all *_widget.php libraries in the constructor. So, the widget controller would only ever speak to the Widget API, passing along instructions from the database (via the model). I hope you see where I'm going with this...