Understand the Structure of CodeIgniter Published Aug 29, 2009 Shawn McCool Web Developer | @ShawnMcCool In this screencast I attempt to explain the structure and terminology of the Code Igniter MVC PHP development framework. 1 Comments jyoseph posted... I disagree wholeheartedly with the previous commenter. It's an excellent overview for someone like myself who knew nothing about codeigniter. Thanks for taking the time to put together such a great vid. horrible posted... this tutorial is the worst i've seen. it fails on all levels. Shawn McCool posted... Thanks for the feedback, Andrew. I'm interested in any specific challenges that you face as a developer who is new to Code Igniter. Is there anything that took a while to really "click" for you or any topics for screencasts / tutorials that new CI developers could benefit from? Shawn McCool posted... Great idea for a post! I do have some strong feelings on this subject. Not necessarily with the location itself, but with ensuring flexibility over the lifespan of a website. http://shawnmccool.com/2009/11/23/managing-assets-with-codeigniter/ As a note about placement: Many people would move the CodeIgniter structure out of the web root folder, and only leave the .htaccess, index.php and assets folders. index.php can be configured to access CodeIgniter from another folder, further securing your site from the kinds of server misconfiguration that can leave your valuable data exposed. Nico posted... I can't agree more with the previous commenter. This is the most EXCELLENT tutorial about CodeIgniter that I've seen. MikkaH posted... Thank you Shawn, This is the first time I see somebody going the whole files of the framework structure and explaining it in as a whole. Lots of folks place videos nowadays, to serve their ego and try impressing "their" audience with flashy keying and too much ads. I like your style, simple and efficient. Yes it would be a nice idea to do the same with the inners files of CodeIgniter you mentionned. I use Django for some of my customers, but develop my new apps in php. And discovering CI with your help was a breeze. I like the simplicity and the lightness of CI. Some improvements has to be done in the management of errors and debugging, but generally, experienced user in php find their way easily. I save a lot of time, I can use for improving. From France, merci for your teaching. Luciano posted... I was trying to find a useful introduction to CI over the entire web(including official documentation) and this one is the only who really taught me everything I wanted to know. From Argentina, thanks a lot Shawn, you rock :) KRD posted... Shawn, Since you are soliciting suggestions for tutorials/ screencasts, I'd like to suggest a quick tutorial on where to actually place images and css files that are used and reused on a site. I've been looking around online and everyone seems to have a different suggestion. I downloaded and looked at Derek Allard's BambooInvoice and he seems to put a css folder and an images folder at the same level as the system folder and then just link to them in the views using href=css/ or href=image/. To me that seems to separate elements of the view from the view folder but I'm just a beginner. What would you suggest? By the way I'm looking forward to part 4! Kris Himalking posted... Thanx a lot for this amazing video, it's very verey useful Andrew posted... Thanks for the video it was very informative. Before watching the video, I did some googling on MVC and downloaded the codeIgnitor framework but it wasn't clear. After watching the video it all clicks. Cheers.
