Coding style

For consistency, readability, and maintainability we have agreed on a coding style close to that of EllisLab. This keeps our code consistent with the code in the framework base.

Read these first:
EllisLab Developer Guidelines

Other EllisLab conventions not outlined in ELDG:

• Use tabs to indent
• Seperate functions with @// -—————————————- … @
• Security check (basepath) in every library, model, and controller
• Comment closing function tags (when a function is long or when that can improve code readability)
• Libs and classes not closed with PHP closing tag ?> (not needed and avoid headers already sent problems). Instead, we only comment that it’s end of file

Colors & design

We will use the following color palette(credits to Color Lovers )