Explicit Development

Patterns for Developing in a Team

1. Explicit Development
2. You’re Never Alone
3. Be Explicit
4. GIT Committed
5. Commit Messages • First line should act as a title • Don’t use -m • Keep messages in present tense • Answer • Why the change? • How does it address the issue? • Any side effects? • Link to an issue?
6. Branch Out
7. Gnarly Branches • feature/navigation : feature branches for core functionality • bug/unstable-dropdown : resolve some bugs • component/nav-login : css, js, php, for component functionality
8. Shared Toolbelt
9. Up a File Tree
10. CSS Class
11. Name Space CSS
12. JavaScript Patterns
13. Explicit Variables *this goes for php too.
14. No Conflict JS
15. <php? echo $audience; ?>