- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
This question appears to be off-topic. The users who voted to close gave this specific reason:
The PHP Framework Interop Group has released a series of coding standard recommendations:
FIG's recommendations are far from an official standard, and I wouldn't even consider them a de facto standard, but they are the more coherent set of recommendations for PHP we have.
Other than FIG's recommendations, you should take a look at Zend Framework's standards, which include coding style recommendations, and PEAR's standards. Personally I tend to favour FIG's recommendations, they are a bit more coherent than every other set of PHP standards I've seen and are more widely adopted.
You should also take a look at PHP CodeSniffer. It's a tool that detects violations of a defined (and configurable) set of coding standards and can be easily automated via Phing. If you decide to follow FIG's recommendations, you could also use PHP-CS-Fixer to rewrite your code to be PSR-1 and PSR-2 compliant (with a pre-commit hook, for example).
Lastly, keep in mind that the main reason for adopting a coding style standard is consistency, you'll never find a set of standards that will make everyone in your team happy. It doesn't really matter which set of standards you'll pick, what matters is that you pick one and stick with it.
Yes, there are couple of standards used in the PHP world. Two of them deserve special recomendation.
The PEAR standard, which should be used by all PEAR packages: http://pear.php.net/manual/nl/standards.php
and the PSR standard, which is supported by some big PHP groups like Symfony, PEAR(again), Drupal, Joomla etc. https://github.com/php-fig/fig-standards
The official PHP Coding Standard can be found in the root of their project:
UPDATE: Because people are already starting to down vote my answer. Be sure to actually read the above file. It contains the coding standards for the C part of PHP and for userland code. Specifically lines 136 to 166 are of interest. Of course the rest is also interesting.
TL;DR Build your standard on top of the PHP standard and it looks exactly as the language (from a userland view) does.