Book Image

Mastering Symfony

Book Image

Mastering Symfony

Overview of this book

In this book, you will learn some lesser known aspects of development with Symfony, and you will see how to use Symfony as a framework to create reliable and effective applications. You might have developed some impressive PHP libraries in other projects, but what is the point when your library is tied to one particular project? With Symfony, you can turn your code into a service and reuse it in other projects. This book starts with Symfony concepts such as bundles, routing, twig, doctrine, and more, taking you through the request/response life cycle. You will then proceed to set up development, test, and deployment environments in AWS. Then you will create reliable projects using Behat and Mink, and design business logic, cover authentication, and authorization steps in a security checking process. You will be walked through concepts such as DependencyInjection, service containers, and services, and go through steps to create customized commands for Symfony's console. Finally, the book covers performance optimization and the use of Varnish and Memcached in our project, and you are treated with the creation of database agnostic bundles and best practices.
Table of Contents (17 chapters)
Mastering Symfony
Credits
About the Author
About the Reviewers
Index

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...