First of all I decided to add an Entries Model and Authors Model to the mix, primarily to get ready for when we can add new entries to our blog. This leads to where we can create new Entries; we add an Administration Module to the application with it's own distinct Layout.

He starts by making the database schema, an entries and authors table, before starting in on the models. They're made based off of the Zend_Db component's structure and they let the application interact with the data in the tables easily. His code for the modules is included as well as the controller and view for the admin module.

In [an article from Maggie Nelson in a blog entry], she remarks on the article being MySQL-oriented and how limited MySQL explain plan support is compared to Oracle. I've had some thoughts in my head for a while that are related to these points, so I finally decided to, knock on wood, put pen to paper.

Matthew talks about things he agrees with (Oracle over MySQL when it comes to hierarchal data and set operators) and some of the things that can make Oracle, with all its power, fall by the wayside. This includes its licensing, the administration costs and some of the recent developments between Sun and MySQL.

This piece covers creating a proper folder structure so that we can have a skin system. I've also created a folder for the admin section which is fully contained with it's own controllers folder and so on. Another unrelated change that has happened since the last part is sub menu logic which we will also take a look at.

They make updates to the bootstrap file to introduce another controller directory and, inside of that, create the Administrator controller and integrate it with a Smarty template to show different menu items if an admin user is logged in.

http://pear.php.net is now using jQuery for some sections of the administration area in order to view user notes/comments and that I will be starting implementing more sections over the site within the next few weeks (Of course this will all be done once we have split the code completely into templates, views, controllers, MDB2 move, etc)

He also makes some comments about the number of Javascript frameworks out there and a mention of the roadmap for the rest of the features they plan to add to the PEAR site.