templating VS Latte

There are also some small template engines available like mustache or handlebars without big dependencies tree. I'm working on a templating abstraction to make this more easier to use any template engine you want so your controller dont need to care about it: https://github.com/schranz-templating/templating

It is supported via the Spiral View. The viewmanager by default will call Stempler you can test it out in the example spiral application running in examples/usages/spiral direcotory visiting /spiral-view will call the template here: https://github.com/schranz-templating/templating/blob/0.1/examples/usages/spiral/app/views/base.dark.php

Have a look at Latte. It gives you a template engine that looks and feels a lot like PHP itself, rather than being a port of Python.

FTLOG, use a template engine. Do NOT use PHP itself as a template engine (ironic given its origins). The best are probably Twig (https://twig.symfony.com/) (used by Symfony and a few others) and Latte (https://latte.nette.org/) (less widely used, but its syntax is *way* more learnable as it's more like PHP itself).

You may have already used some of Nette's tools in other projects you've worked on and not known it! There is the very extendable Tracy for debugging similar to Whoosh, and Latte for intuitive HTML templating.

The target of the project is that more libraries / modules allow to use any Template engines the project want and see the more a as data provider. Also this kind of abstraction should make libraries e.g. a async mailer easier be integrated into different frameworks. A common usecase for myself is that Sulu CMS does not only support Twig but also other Template engines like example Latte which has interesting concept context aware escaping.

Nette is a PHP framework made by David Grudl and it is a great alternative to Symfony and Laravel. It has an amazing templating system called Latte that uses similar syntax to PHP and by default has context-sensitive escaping (which no other framework has). In my opinion, it is easier to learn, because it comes with a simple structure by default, it has no dependencies and less patterns to learn.

In the template file, we passed a variable called project containing a value into the extracted string mentioned before. All of this is done using an array as a second argument of the underscore tag notation. This is how this pairing works using latte templating engine and NEON. We've also used the noescape filter, which disables automatic escaping so the HTML tags are actually rendered and not printed as a text.

I'd heard great things about Timber, how do you like to use it? I recently wanted to add some templating to a WP2Static addon and went with Latte, I believe my reasoning at the time was for better PHPStan/static analysis support - I'm definitely not a power user of it, just simple templating for now.