Best practices for implementing a site's administration

[eluser]Linderman[/eluser]
In these situations i feel comfortable to do the following:

/application/libraries/MY_Controller.php which Extends Controller

/application/controllers/Fronfend.php which extends MY_Controller

/application/controllers/Infopages.php which extends Frontend
/application/controllers/Gallery.php which extends Frontend
/application/controllers/News.php which extends Frontend
... and so on

for admin:

/application/admin/Admin.php which extends MY_Controller
/application/admin/Infopages.php (adding, editing ...) which extends Admin
/application/admin/Gallery.php (adding, editing ...) which extends Admin
/application/admin/News.php (adding, editing ...) which extends Admin
... and so on

Then in the view:

/application/views/page.php
/application/views/header.php
/application/views/footer.php
/application/views/index.php
/application/views/infopages/index.php (for example when viewing all the pages into a list)
/application/views/infopages/show.php ( when viewing specific infopage, like about us for example)
/application/views/gallery/index.php ( viewing all the gallery categories )
/application/views/gallery/show.php ( when in particular gallery category -> seeing images in it )
... and so on

/application/views/admin/page.php
/application/views/admin/header.php
/application/views/admin/footer.php
/application/views/admin/dashboard.php
/application/views/admin/infopages/index.php
/application/views/admin/infopages/add_edit.php
... and so on

Maybe its not the best way , but i feel comfortable in this logic.

It will be great really if some more information on Method #3 from this article: http://philsturgeon.co.uk/news/2009/07/C...odeIgniter

i mean exact examples of configuration, inheritance and url calling..