Conventions

History Key

  • New content
  • Removed content

Recent Versions

Choose two versions to compare, or click the link to view it.

  1. 27. almost 4 years by inparo
  2. 26. almost 4 years by inparo
  3. 25. almost 4 years by toopixel
  4. 24. almost 4 years by toopixel
  5. 23. almost 4 years by inparo
  6. 22. almost 4 years by inparo
  7. 21. almost 4 years by inparo
  8. 20. almost 4 years by inparo
  9. 19. almost 4 years by inparo
  10. 18. almost 4 years by toopixel
  11. 17. about 4 years by toopixel
  12. 16. about 4 years by toopixel
  13. 15. about 4 years by toopixel
  14. 14. about 4 years by toopixel
  15. 13. about 4 years by toopixel
  16. 12. about 4 years by toopixel
  17. 11. about 4 years by toopixel
  18. 10. about 4 years by toopixel
  19. 9. about 4 years by toopixel
  20. 8. about 4 years by toopixel
  21. 7. about 4 years by toopixel
  22. 6. about 4 years by toopixel
  23. 5. about 4 years by toopixel
  24. 4. about 4 years by inparo
  25. 3. about 4 years by inparo
  26. 2. about 4 years by inparo
  27. 1. about 4 years by toopixel
 

Coding style

For consistency, readability, and maintainability we have agreed on a coding style close to that of EllisLab.!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 )