@rvanlaak thanks for submitting this nice new cookbook!

Was thinking about addingmore information about the Theming and a code sample about the Twig extension, but seems like that is too much info for the cookbook article. What do you think@javiereguiluz ?

@rvanlaak I agree with you: it looks like too much information for this cookbook. I personally love short and straight-to-the-point cookbooks, so I really like your tutorial as it is now. Thanks.

Another thing, where can I find new decisions the such as the one you mentioned about not using acme examples? Could not find anything onhttp://symfony.com/doc/current/contributing/documentation/index.html and probably such decisions are made in the Google Groups, but we can not follow that the entire day 👍

I don't really know where we decided this, because I talk with doc maintainers via email, IRC and GitHub :( In any case, the#4740 PR is the one which made the biggest recent change to removeacme,demo,foo and nonsenses like those.

I'm going to check if we can add something about this in the formal document that you linked. Thanks for your comments.

@rvanlaak we don't use the Google Groups and you sure don't have to watch them in order to contribute something (these reviews are just to help you adding amazing content to the docs, it doesn't matter if your PR isn't 100% correct at first).

Decisions like this aren't really strict standards or decisions. As an important rule, it is always better using real-world examples than foobaring your examples. While being more clear, it also works as an advertisement for the framework ("wow, can I also create X with this?").

Since the best practices, we are updating the docs to follow them. One of the most important changes is to no longer recommend using multiple bundles, but just one bundle: AppBundle. We are still in the process of it, as it's a very hard task to do nicely.

Thank you for creating the pull request,@rvanlaak. It's nice work. However, I think we should start the text with a short introduction to show use cases when you might want to call a command from a controller.

I was thinking about something like:

You may have the need to execute some function that is only available in a console command. Usually, you should refactor the command and move some logic into a service that can be reused in the controller. However, when the command is part of a third-party library, you wouldn't want to modify or duplicate their code, but want to directly execute the command instead.

What do you think?

Agree with you@xabbuh , so I've updated the example to a real world use case, eg. sending the SwiftMailer spool directly from the controller. Let me know if it's fine now, so I can squash the commits into one.

Rebased the latest changes@javiereguiluz

@rvanlaak awesome! Thanks for working on this and for your infinite patience with our comments and suggestions.

@xabbuh this nice PR is now ready to be labeled asfinished, don't you think?

No problem, great way of getting known with the community guidelines 👍

Fixed the outstanding issues. Let me know if the commits are ready for a rebase 👍

👍

👍 Great work@rvanlaak!

Completed the rebase, squased all commits intorvanlaak@62ae7c3

@xabbuh anything I've got to change for this PR?

@rvanlaak I left two minor comments. After that I think it's finished.

@xabbuh nice pick, fixed and rebased it!

👍

Thanks so much@rvanlaak! This is exactly the small, targeted article that we love having. And welcome to the process and thanks for sticking with us through all the reviews.

I have now merged this into the 2.3 branch, and opened a new PR -#5299 - with a few further tweaks. If you can review that, it would be awesome.

Cheers!