rfc VS Twig

That said, I do agree with the general opinion that you should stay clear. Now even more so than in the past. I'm saying this as someone who has been using Joomla for well over 10 years and contributing for some years as well. Although Joomla has some big plans ahead (https://github.com/joomla/rfc), I don't expect it to get far. Joomla has a long history of bad practices and incompetent maintainers and this has gotten worse in the last few years. While there are a few high level developers somewhere behind closed doors, the majority of maintainers don't even know PHP basics, do not follow PHP development, do not care to review the submitted code properly, do not care to look into reported issues. Yes, unit tests are very limited and human tests are borderline useless in most cases. Not to mention that every other patch release intentionally introduces B/C breaks despite the project promising Semantic Versioning.

Miscommunication in our projects is costly. A single misunderstood User Story can result in 3 days of wasted development time. Additionally, when developers do not use the same programming language, it may be necessary to construct APIs to facilitate communication, which can also be expensive. It is important to consider why front-end developers may be hesitant to work with Twig and how this can lead to a disconnect between front-end and back-end development.

The first step before generating the PDF is writing the HTML. To generate the HTML string, we will use the Twig template engine, which is the default one in Symfony. It comes with tons of features such as inheritance, blocks, filters, functions, and more.

In the phase of outputting data, you can use template engines like Twig or Blade or htmlspecialchars function.

Joomla dips into and out of php to get vars/logic into the frontend, which is fine, but it's nowhere near as tidy as a full-fledged templating engine like blade or twig which many other php CMSs offer out of the box.

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

It took me a while to find a PHP project that was simple enough for me to set up on a single Docker image, but after some trial and error I found the Twig project.

Symfony uses Twig, a fast, secure, and flexible templating engine. Twig allows the developer to define custom tags and filters and create Domain-Specific Languages (DSL).