-
Book Overview & Buying
-
Table Of Contents
Symfony 1.3 Web Application Development
One thing that I have learned in the past is to always establish coding guidelines. Following some of the eXtreme programming principles—namely, pair programming—I have learned that having a set of guidelines helps team integration and code readability.
These are some Symfony-specific guidelines:
One module is not for one page. The only time where this might be ruled out is if there is a strong possibility of the module being extended.
For instance, if you have general footer pages, these could be a part of the general module. Also, grouping functionality allows code to be refactored into a plugin during development.
Application-specific settings should always go in the app.yml file.
When using a mail plugin for sending out emails, abide by the MVC pattern.
That means use the action and templates rather than storing content inside a variable.
Keep PHP to an absolute minimum within templates.
Database table names should be plural and PHP models names should be singular.
Change the font size
Change margin width
Change background colour