Skip to content
TYPO3 extension Fluidpages: Fluid Page Template Engine
Branch: development
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
Classes [TASK] Remove unused fields/TCA Mar 4, 2019
Configuration
Documentation/Changelog
Resources/Private
Tests
.editorconfig
.gitignore
.travis.yml
CHANGELOG.md
CONTRIBUTING.md [DOC] Update contribution guide link Jan 26, 2015
LICENSE.md
README.md
bower.json
composer.json [REMOVAL] Require PHP 7.1 or above Mar 4, 2019
ext_conf_template.txt [FEATURE] Replace deprecated configuration translation Dec 14, 2015
ext_emconf.php
ext_icon.gif
ext_localconf.php
ext_tables.sql
phpunit.xml.dist [TASK] Remove strict option from PHPUnit configuration Nov 24, 2015

README.md

Fluidpages: Fluid Page Templates

Build Status Coverage Status Documentation Build Status Coverage Status

What does it do?

EXT:fluidpages enables the use of Fluid templates as page templates, each template file acting like an individual template. The template files are processed by the extension and a simplified method of selecting templates (two selector boxes, one for current page and one for subpage templates, like TemplaVoila).

Why use it?

Although the FLUIDTEMPLATE object in TypoScript allows Fluid templates to be used as page templates, it has limited capabilities. Using EXT:fluidpages the page templates are not only selectable in page properties but also rendered from a proper Controller.

In addition to this, Fluid Pages uses all the power of Flux to allow the template to contain dynamic but very compact configuration sections - which translate to fields in the page properties, the values of which are available when rendering the template.

When combined with the VHS extension this becomes a very powerful tool: the dynamic nature of Fluid templates and the flexibility of ViewHelpers - combined with extremely easy-to-use configuration options.

How does it work?

Fluid Pages are registered through TypoScript. The template files are then processed and the configuration contained in each is recorded and used to identify the page template when being selected by content editors.

When editing the page a Flux ConfigurationProvider takes care of processing the specific template's configuration and presenting it as fields available to the content editor much like TemplaVoila.

View the online templating manual for more information.

Installation

Installation using Composer

The recommended way to install the extension is by using Composer. In your Composer based TYPO3 project root, just do composer require fluidtypo3/fluidpages.

Installation as extension from TYPO3 Extension Repository (TER)

Download and install as TYPO3 extension. Search for the term fluidpages.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.