@xabbuh --thanks for the additional information. I'm trying out Symphony, so the info you provide (and the corrections that should come from it) should be useful. I'll submit a new pull request showing the changes that arise for me from your point about best practices.

@ownsourcing you can just add a new commit in this branch (click on the "edit" button when you're in the "files" tab of this PR). The PR will automatically be updated.

@wouterj, that approach to improving the pull request makes sense - thanks.

That said, I'm finding myself turning in circles within the documentation. I probably need more familiarity before I can reasonably reconcile the different takes on purpose of directories (there seem to be conflicting pieces of information in this doc itself).

I've submitted a notion that I think would help make the focus of this page more achievable. It may be worth considering with an open mind, or it may be that most readers can navigate the difficulties of the page.

For now I'll plow on with building familiarity (recognizing I'll soon no longer have the fresh view I currently have), then see what contributions are of use to the community and within my ability to share.

Kudos to the docs team!

@ownsourcing it might be possible that some docs are in conflict. Some weeks ago, Symfony published a "Best Practices Guide", which contained some completely new ideas on how to organize your app and do stuff. The docs are in the middle of a big update to comply with these new ideas.

@ownsourcing thanks for sending this pull request and for helping us improve the documentation. However, as pointed by@wouterj, the recent Symfony Best Practices don't recommend to put the templates insrc/ but inapp/. Sadly this means that we should close this pull request without merging it. But don't worry, I'm sure next time your pull request will get merged. Thanks!