I believe this was the guideline, but it was never written somewhere. As lots of people are struggling with it, I think it's a good idea to document it. While doing this, I've also snake_cased all template paths in the currently updated book articles.

@javiereguiluz What do you think? We've never talked too much about this directly. The negative to underscoring everything is that templates aren't the same as their controllers anymore - PostAdminController::createPostAction would be in post_admin/create_post.html.twig.

We're just talking about a recommendation here - not life or death - but let's think about it. The old upper-camel case was done without really thinking, to support the @Template magic (because we were all very used to having this from 1.x). If we break from this, then @Template won't work, and even if we update it, trying to transform from createPostAction to create_post.html.twig could be buggy.

What do guys think?

In this moment, my thinking is that the old way seems the best, as it's very simple: everything just matches: no transformations (of course, you can do whatever you want).

ping @javiereguiluz I need your input on upper/lower case template directories here - this will affect a lot of different parts. Thanks :)

ping again @javiereguiluz!

moved these changes to #5001

This is not correct, see #4789 (including some other fixes)

What's the issue? Just that we should have the line breaks different?

missing new

This should be something like default/homepage.html.twig

i would prefer valid php here.

this is our standard