Hi there, my name is Adam and this is a project I have decided to embark upon to help me understand the Symfony MVC application framework.

The concept of Model-view-controller allows a great degree of flexibility in creating web based apps. You have a data model which can be housed in a database, upon which you apply a level of control or business logic to before displaying the relevant view to the World.

What it also allows is database abstraction, as a developer you can ignore the database and focus on the business logic. Why do we need to learn the complexities of a propriety database or worry about porting an app from one database to another? With abstraction all we have to do is understand how to get the information from an abstraction layer, and in Symfony’s case it’s Propel (for now...).

In addition to database abstraction an MVC allows multiple views, but reusing the same business logic, i.e. a developers dream, less code for more output (we are all lazy people!)....

Any ways, I am not the Worlds best coder, nor am I that quick, but I do like a challenge....

Lesson 1 - Describing the problem

Lesson 2 - Describing the (original) tables and relations ←–

The following are ‘maybe’ titles...depends on how I feel at the time.

Lesson 3 - Design the new database schema

Lesson 4 - Symfony, set up and config, including database.yml

Lesson 5 - Symfony - Backend app and admin generators, linking it together...

Lesson 6 - Symfony - Frontend app and making some bits and pieces

Lesson 7 - Symfony - Making it look good, CSS (this is where Chris comes in... he just doesn’t know about it yet..)

Lesson 8 - Symfony - RSS feeds, WAP pages etc..

Lesson 9 - Symfony - Tidying everything up...

Lesson 10 - Looking back...