Home

Frequently Asked Questions

1. How is FluidPage different from the FLUIDTEMPLATE typoscript object?

FluidPage provides functionality that we can't figure out how to achieve using FLUIDTEMPLATE. First, the extension adds the backend layout selector fields to the rootline, which doesn't happen out of the box. Second, the extension determines which template to use (similar to how TemplaVoila works) by walking up the rootline and looking at the value of those fields on page records. This template selection process is not present in FLUIDTEMPLATE and, IMO, would be difficult or impossible to achieve with pure typoscript. Third, the extension extracts the contents of the body tag from the HTML template before passing it to FLUID. This is important because it makes it easier for there to be a clear separation of roles (one person can develop a fully valid HTML template, and another person can implement it in TYPO3). If try to use a FLUIDTEMPLATE for a page, that template will not be a full HTML document, as in most cases the contents of head need to be generated from TYPO3 and Typoscript.

Now, that said, we'd still like to rely on core functionality as much as possible in FluidTemplate, and we're looking into whether it's viable to utilize FLUIDTEMPATE for the actual rendering of the template, with some pre-processing in the extension.

2. How do I use FluidPage?

Read the documentation: How to use FluidPage