Ready to watch this entire course?
Become a member and get unlimited access to the entire skills library of over 4,900 courses, including more Developer and personalized recommendations.Start Your Free Trial Now
- View Offline
Starting with the what and why of CodeIgniter, Jon introduces key concepts such as the MVC pattern and libraries by demonstrating how to create static pages, then storing and displaying magazine info in a database. Advanced topics like classes and helpers are explored to validate user input, upload files, and much more. By creating a complete system, you'll have the foundation to build your own applications with CodeIgniter.
- What is CodeIgniter?
- Creating a static page controller
- Generating output with a view
- What is a model?
- Saving data with Active Records
- Creating forms
- Validating user input
- Listing records in tables
- Uploading images
- Viewing and deleting records
Skill Level Intermediate
Throughout this course, I've covered a lot of base functionality. Starting with the what and why of CodeIgniter, then explored models, views, controllers, libraries and helpers. I'll be honest. It was kind of difficult to hold back and focus. There's a lot that can be done in the magazine catalog system. Here's some ideas that can be used to extend this application, in three categories. Starting with, Usability Ideas, such as adding a validator that prevents duplicate magazines and publications. Highlighting erroring fields, which is supported by Twitter bootstrap. Adding a confirmation step to deletion and sorting magazines. Then, you could do some changes to the look and feel, including adding pagination using the pagination library.
Making a thumbnail upon upload, maybe for inclusion in the list of magazines. Formatting dates using the date helper so, it excludes the day. Styling magazine covers and lists, maybe using a Hero header or three abreast instead of a table. And then finally, configuring the url without index.php with web server rewrites to make it much cleaner. Then I have a few functional ideas, including a comprehensive much more flexible navigation system that's configurable. A less manual templating system, which will save code and make it harder to forget.
Editing magazines instead of deleting and creating them manually. Publication management, because currently there's no interface for it. Summary reports, such as, you have 13 issues of Sandy Shore magazine. And users sessions and security. Because it would be optimal if access could be controlled. This might seem like a lot, but code igniter is a very flexible framework. And each of these thing I know, can be done. And these are real world tasks that I'd like to see in an application for a client.