I watched the rise of MVC frameworks' use in PHP (Mojave anyone?).
I used CodeIgnitor on a couple of projects - it was simple enough and worked fine.
I did not really understand MVC until I read Fowlers treatise on layers and n-tier in POEAA.
I understood one of the great attractions of using an MVC framework was that you would have to only edit one or two "layers" if you for example had to add a field to a form and a database.
Given that the backend of a CMS I work on is largely a front end to a CRUD operation and I wanted it highly Ajax (read 99%) controlled - I was dissatisfied with traditional MVC routing etc.
I later learned that what I actually wanted (and created) was named a SPA (Single Page Application) or to be more accurate consisted of a number of SPAs.
Have a read of this, again from Fowler, PresentationModel and maybe mock it up in PHP and see if that proffers any ideas.
I took that idea together with a PHP/JS library called Xajax, and with some enhancements, basic tablegateway mappers driven from ini files wrapping PDO as 'models' ( more like just data handlers than true models ) and some auto form generation helpers and made myself a crude PresentaionModel which as Fowler says "A view then simply projects the state of the presentation model onto the glass.".
The great thing about it is that you can maintain extremely complex state quite easily - as hinted at in the example that Fowler gives.
The other good thing is that I do most work in one single file, which is in effect a very fat controller.
Naturally there are drawbacks, a very fat controller for one, the inconsistent and piecemeal way I have built up each controller for another.
The Xajax project seems to be grinding to a halt.
Finally my point.
I am dissatisfied with what I now have largely because I suspect that features of HTML5 and client side storage options (perhaps targeting a single browser platform in the case of Web Admin Backends) along with eyeing a parallel mobile platform, will :
a) provide an even better GUI experience
b) be easier to develop for
... and by taking on these challenges I don't think looking immediately for an MVC solution should necessarily be taken as a given.