How to Embed Controllers in a Template

Rendering embedded controllers is "heavier" than including a template or calling
a custom Twig function. Unless you're planning on caching the fragment,
avoid embedding many controllers.

Including template fragments is useful to
reuse the same content on several pages. However, this technique is not the best
solution in some cases.

Consider a website that displays on its sidebar the most recently published
articles. This list of articles is dynamic and it's probably the result of a
database query. In other words, the controller of any page that displays that
sidebar must make the same database query and pass the list of articles to the
included template fragment.

The alternative solution proposed by Symfony is to create a controller that only
displays the list of recent articles and then call to that controller from any
template that needs to display that content.

First, create a controller that renders a certain number of recent articles:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19

// src/Controller/ArticleController.phpnamespaceApp\Controller;// ...classArticleControllerextendsAbstractController{publicfunctionrecentArticles($max=3){// make a database call or other logic// to get the "$max" most recent articles$articles=...;return$this->render('article/recent_list.html.twig',['articles'=>$articles]);}}

Then, create a recent_list template fragment to list the articles given by
the controller: