This feature has been moved to the extension "Fluid Pages" (key: fluidpages) which you will find on TER as well as Github: https://github.com/NamelessCoder/fluidpages
This feature has been moved to the extension "Fluid Pages" (key: fluidpages) which you will find on TER as well as Github: https://github.com/NamelessCoder/fluidpages
The Fluid Page feature allows the use of Fluid templates as page layout templates. The feature is activated through extension configuration and adds a new tab - called Page Template - to regular pages and shortcuts.
Templates are inherited to subpages, just like selecting a backend layout.
The Fluid Page feature can be used to replace all ordinary template rendering with the advanced Fluid engine's excellent templating features. It follows the logic of a FLOW3 site package: page templates are individual files which can use Layouts and Partials. Template files contain sections which will be rendered by a Layout - just like an Extbase extension but containing the entire page design template instead of just a plugin design template.
One of the main benefits of using this feature is the option to combine an entire web site's design templates in an extension. This makes it easily transportable and eases version control integration. Resource files - stylesheets, javascripts, images and icons - can also be contained as a Resource for the site design extension.
You can also choose to place your template design files in fileadmin or another location, if you find this approach more suitable.
The feature only requires three lines of TypoScript indicating where to fetch a set of template files. The rest - page labels, configuration options, additional Fluid template variables etc. - is all configured in template files. Page rendering configuration options can be defined in much the same way as a FlexForm, making it possible to select target pages, user access groups, rendering parameters and the likes through editing page properties in the backend.
You can even use these options to control how properties are presented to the backend editor: enable/disable fields and tabs, limit possible selections, affect page record fields and so on - when set, the defined rendering parameters can be used for condition statements and can affect other rendering parameters.
You no longer need to define your menus in TypoScript - there are ViewHelpers to render not only menus but also language selection, content output, page header content and much more.
Content sliding - a new feature in TYPO3 4.4 - is supported, letting you specify content inheritance on subpages without complicated TypoScript.
Because of the dynamic nature of the rendering parameters you can even control all of these things through your template - entry levels, starting page, content inheritance, language labels, content elements etc.