In this screencast, we’ll explore a few different techniques to DRY up your codeigniter views by implementing a master layout file for your site. Here’s a quick start if you’d like to setup your own master model.
Simple Blog is a multi-part series. Check out The Index
In example 4, we implemented the MVC pattern for our Simple Blog app. We physically separated our data, presentation, and application logic into models, views, and controllers. In example 6, we rewrote our data logic using PDO which enabled parameterized statements and database portability. In example 7, we implemented the Smarty Template Engine to cleanup our views with a more readable syntax.
So, we’ve developed a web application written in PHP5 that follows MVC, supports multiple databases, provides object-record mapping, has a built-in template engine, and built-in caching. Many of the features we’ve implemented for Simple Blog are precisely the features offered by PHP Frameworks. So, the next logical step was to rewrite the app using a PHP Framework such as CakePHP, CodeIgniter, Symfony, Yii, or Zend which promise to deliver all of the features we’ve implemented so far and more.
In the process of researching these frameworks, I ran across CodeIgniter’s User Guide which was so well written and so well organized that I decided to start with CodeIgniter. A quick glance at codeigniter.com and we get to the promises: small footprint, exceptional performance, nearly zero configuration, and clear documentation. Well, let’s dive in and see what CodeIgniter is all about.