The following pages describe the broad concepts behind CodeIgniter:

Any software application requires some effort to learn. We’ve done our best to minimize the learning curve while making the process as enjoyable as possible.

Developers often desire different system behavior depending on whether an application is running in a development or production environment. For example, verbose error output

A view is simply a web page, or a page fragment, like a header, footer, sidebar, etc. In fact, views can flexibly be embedded within other views (within other views, etc.,

Models are optionally available for those who want to use a more traditional MVC approach. Page Contents

CodeIgniter is based on the Model-View-Controller development pattern. MVC is a software approach that separates application logic from presentation. In practice, it permits

The Profiler Class will display benchmark results, queries you have run, and $_POST data at the bottom of your pages. This information can be useful during development

The following page describes the coding styles adhered to when contributing to the development of CodeIgniter. There is no requirement to use these styles in your own CodeIgniter

By default, URLs in CodeIgniter are designed to be search-engine and human friendly. Rather than using the standard “query string” approach to URLs that is synonymous with

This tutorial did not cover all of the things you might expect of a full-fledged content management system, but it introduced you to the more important topics of routing, writing