sulu VS Latte

https://sulu.io/ or https://kunstmaancms.be/ if you want to stay with symfony. Both solid options

I want to try Sulu first because it is Symfony-based.

Another usecase are Framework based CMS System. Beside Drupal, Typo3 using example Symfony components, still are not Full Stack Symfony and don't use Symfony based folder structure and are so very different then using Symfony Full Stack based CMS. In this area other CMS like Sulu, Bolt, .. are placed which do not hide Symfony Full Stack and are more for the web applications which are not typical just a Website but has application based component in it which can be build with the Symfony components and ecosystem. This CMS are also mostly more version control friendly as most configurations are inside Code and not inside Database and the CMS admin concentrate on Content Management and configure the System itself. Another CMS which is more and more migrating Full Stack Symfony is Contao CMS, which definitly should not be forgotten.

Try something on Symfony. For example https://github.com/sulu/sulu. It's a CMS, but I've noticed that it has some domain-driven design principles implemented.

While I was working on Sulu CMS and did invest a lot about prototypes around Hexagonal Architecture. I did miss something specific in the PHP-Fig interfaces, a Interface for Template engines.

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.