||2 years ago|
|.ddev||2 years ago|
|Classes||2 years ago|
|Resources/Private/Examples||2 years ago|
|.gitignore||2 years ago|
|LICENSE||2 years ago|
|README.md||2 years ago|
|composer.json||2 years ago|
|ext_emconf.php||2 years ago|
|ext_localconf.php||2 years ago|
|functions.php||2 years ago|
PHPTEMPLATES is a TYPO3 extension which implements a simple template rendering engine based on plain PHP files.
It can be used alongside the well-known Fluid template engine or as a replacement for it.
At the moment the only way to install this extension is through Composer:
composer require jdoubleu/typo3-phptemplates
State of Development
WARNING: This extension/template engine is still under development. The API may be subject to breaking changes in the future. As this is an experimental template engine the internals may also change. If you have any suggestions, critic or use cases please feel free to share them.
Following some criticism about the complexity of Fluid templates
and limitations by the template engine itself, I wanted to implement a simple-as-possible template engine while
still providing enough features for general page rendering. In fact,
PHPTEMPLATES only implement a template resolving and
overriding mechanism as well as a minimal and easy to learn API to interact with certain TYPO3 internals (e.g. TypoScript, ContentElements, etc.).
This template engine is meant to be opinionated and thought to work only a specific way, although it is possible to extend the internals and behaviour.
- Easy to learn: You only need to know PHP itself, a minimal (~5 LOC) initial configuration and a small and simple API
- Fast: Since we are using PHP files already we don't need to render any template files back to PHP. However this might only affect development time, because templates are cached in production.
- Flexibility: You can write any PHP code and logic inside the templates and don't need to know how to write
- Easy debuggable: You can either use PHP's built-in
var_dump, etc. functions or use XDebug and set breakpoints directly in your template files.
Given the features, the developer is still responsible for writing clean code, meaning to not blow up templates and separate business logic from presentation.
As long as there is no official documentation, follow the examples in