title: Documentation for large or small Projects with PHP?
body: <p>we are talking a lot about documentation for programmers in the moment. How do you handle this part?</p>
  
  <p>What is the best method to introduce a new team guy into an "large" PHP Project. What does a new guy need?</p>
  
  <p>My thoughts so far:</p>
  
  <ul>
  <li><strong>good source code</strong> </li>
  <li>api documentation generated through phpdoc</li>
  <li>clear coding style / guideline</li>
  </ul>
  
  <p>Some kind of paper/wiki.. with information about the infrastructure (database, firewalls..)</p>
  
  <p>What else do you provide if you have to hand over your project to someone else (possible not as good as you in php)..</p>
  
  <p>Do you create something like " to add an function to read out server data, put in Model xYZ?"</p>
  
  <p>sorry for my poor english :)</p>