How templates are organized

The strategy that you choose for template hierarchy depends on your project. In this project, we will place the base template on the base of the pyramid. This is where you define the main HTML structure of your project. It contains the building blocks of your main template. This means placeholders for blocks such as headers, navigation, body, and footer are defined here.

So, we cannot define an important template like this in our bundles. It should be somewhere safe where it can be easily accessible from every corner of the project.

The app/Resources/views folder seems to be the perfect place for it. Define your desired skeleton for projects here, then extend it in your bundles and add content the way you like. This way, if you need to modify the page structure in the future, you don't need to go through every single bundle individually. As they are extended from the base template, changing the base will affect the rest of the templates.

How about vendors? You can...