A Style Guide

This is a project for documenting standards for writing code.

Part of being a good steward to a successful project is realizing that writing code for yourself is a Bad Idea™. If thousands of people are using your code, then write your code for maximum clarity, not your personal preference of how to get clever within the spec. - Idan Gazit

Contents

1. General guidelines
2. Git guidelines
3. PHP guidelines

TODOs

For a list of active/queued tasks, please be sure to read the TODO.

Contributing

Before making a pull request, please be sure to read the Contributing Guide.

Changelog

For a list of all notable changes, please be sure to read the Changelog.

Acknowlegements

For a list of our heroes, please be sure to read the Credits.

Contacts

Feel free to yell at me: [email protected]