Phil is the lead developer for PyroCMS; a modular CodeIgniter Content Management System and works with CodeIgniter every day. He shares his experiences running PyroCMS. How to get things right and how to organise everybody involved.

1. Running an Open-Source CodeIgniter project
The tale of PyroCMS - an open-source Content Management
System built with CodeIgniter. What, why and how!
Phil Sturgeon
email@philsturgeon.co.uk http://twitter.com/philsturgeon
http://philsturgeon.co.uk http://github.com/philsturgeon

2. Introduction
My history in open-source

3. Introduction
My history in open-source

4. Introduction
My history in open-source

5. Introduction
What do I do these days?
Work for Mizu Design Ltd

6. Introduction
What do I do these days?
Work for Mizu Design Ltd
Creating internal CodeIgniter applications

7. Introduction
What do I do these days?
Work for Mizu Design Ltd
Creating internal CodeIgniter applications
MojoMotor Plugins

8. Introduction
What do I do these days?
Work for Mizu Design Ltd
Creating internal CodeIgniter applications
MojoMotor plugins
ExpressionEngine modules

9. Introduction
What do I do these days?
Work for Mizu Design Ltd
Creating internal CodeIgniter applications
MojoMotor plugins
ExpressionEngine modules
PyroCMS development

10. Brief history of PyroCMS
StyleDNA produces StyleCMS
We realise we need a CMS
Back in 2007 PyroCMS was first born as
StyleCMS, a basic CMS for small sites
StyleDNA fails and burns horribly
PyroCMS rises from the ashes

11. Brief history of PyroCMS
Turns out, looks matter!

12. Brief history of PyroCMS
Turns out, looks matter!

13. Basic Principles

14. Basic Principles
Clients are stupid

15. Basic Principles
Clients are stupid
“Can you put a redirect on Amazon to our
homepage?”

16. Basic Principles
Clients are stupid
"Why does 'N' come after 'L' in this
alphabetical listing?!"

17. Basic Principles
Clients are stupid
"We refuse to use this font 'Century
GOTHIC Bold'. This is a family-friendly site!"

18. Basic Principles
Clients are stupid
Hide confusing things
Make it hard for them to break the site
Control, sanitise and correct their input
WYSIWYG
MS Word!!!!
XSS Clean
CSRF protection

19. Basic Principles
Clients are stupid
Developers are lazy

20. Basic Principles
Developers are lazy
Documentation
Easy upgrades
Use a logical folder structure
addons
libraries
modules
themes
system
codeigniter
pyrocms
uploads

21. Basic Principles
Folder Structure
system
codeigniter
pyrocms
controllers
libraries
models
modules
views

22. Basic Principles
Developers are lazy
addons
helpers
libraries
modules
themes
widgets

23. Basic Principles
Developers are lazy
Packages available in CodeIgniter 2.0
addons
helpers
libraries
modules
themes
widgets

24. Basic Principles
Developers are lazy
Packages available in CodeIgniter 2.0
addons
helpers Modular Separation (BitBucket)
libraries
modules
themes
widgets

25. Basic Principles
Developers are lazy
Packages available in CodeIgniter 2.0
addons
helpers Modular Separation (BitBucket)
libraries
modules
Template library (BitBucket)
themes
widgets

26. Basic Principles
Developers are lazy
Packages available in CodeIgniter 2.0
addons
helpers Modular Separation (BitBucket)
libraries
modules
Template library (BitBucket)
themes
widgets
Crazy code, not available

27. Basic Principles
Clients are stupid
Developers are lazy
Designers are control freaks

28. Basic Principles
Designers are control freaks
Themes
Don’t mess with their HTML
Let them mess with your HTML
Don’t give them enough rope!

29. Basic Principles
Clients are stupid
Developers are lazy
Designers are control freaks
EllisLab are always “right”

30. Basic Principles
EllisLab are always “right”
Never modify the core of CodeIgniter

31. Basic Principles
EllisLab are always “right”
Never modify the core of CodeIgniter
Not enough PHP 5?

32. Basic Principles
EllisLab are always “right”
Library autoload
Call more than singletons:
$foo = new Something(‘bar’);
$bar = new Something(‘baz’);
Use some kick-ass PHP 5 syntax:
$foo = Settings::item(‘bar’);

33. Basic Principles
EllisLab are always “right”
Never modify the core of CodeIgniter
Not enough PHP 5?
Extend for the win

34. Basic Principles
EllisLab are always “right”
MY_Exceptions - Custom 404 messages

35. Basic Principles
EllisLab are always “right”
MY_Form_validation - Extra Validation

36. Basic Principles
EllisLab are always “right”
MY_Security - Allow some naughty tags through

37. Basic Principles
EllisLab are always “right”
MY_Parser - Dwoo it!
Template parser in CI blows for... pretty much everything.
{$message}
{anchor(‘controller’, ‘Some page’)}
{lang($foo)}
{if $user->group == ‘admin’)}
http://dwoo.org/
http://bitbucket.org/philsturgeon/codeigniter-dwoo

38. Basic Principles
Clients are stupid
Developers are lazy
Designers are control freaks
EllisLab are always “right”

39. Managing the Code

40. Managing the Code

41. Managing the Code
Master, Branches, Tags
Master
Same as Subversion trunk
Default “branch” of the repository
$ git clone git://github.com/pyrocms/pyrocms.git
Should always be ready to tag or download, keep it stable!

42. Managing the Code
Master, Branches, Tags
Branches
Keep code out of the way
v1.0-dev is relatively stable
v2.0-dev seriously fucked
Work on X feature independent of version Y
$ git checkout v1.0-dev

43. Managing the Code
Master, Branches, Tags
Tags
Tag each version
Marks a specific commit as a version
Automatic “Downloads” entry on GitHub
http://github.com/pyrocms/pyrocms/zipball/v0.9.9.7
http://github.com/pyrocms/pyrocms/zipball/{$variable.cms_version}

44. Managing the Code
Master, Branches, Tags
Forks
User owned copy of your repository
People do your work for you
Use it to trial new contributors