Using Fluid in TYPO3

Here are some examples of how Fluid can be used in TYPO3:

Create a template (theme) using a combination of TypoScript FLUIDTEMPLATE and Fluid. Check out the TYPO3 site package tutorial which walks you through the creation of a sitepackage extension.
Create a custom content element type in addition to the already existing content elements TYPO3 supplies.
Extbase-based controllers have a default Fluid view in $this->view.
Use Fluid to create emails using the TYPO3 Mail API.
Use Fluid in backend modules, either with or without Extbase.
Use the generic view factory to create a Fluid view.

Changed in version 14.0

These classes were marked as deprecated in TYPO3 v13.3 and have been removed in v14:

\TYPO3\CMS\Fluid\View\StandaloneView
\TYPO3\CMS\Fluid\View\TemplateView
\TYPO3\CMS\Fluid\View\AbstractTemplateView
\TYPO3\CMS\Extbase\Mvc\View\ViewResolverInterface
\TYPO3\CMS\Extbase\Mvc\View\GenericViewResolver

Using the generic view factory (ViewFactoryInterface)

New in version 13.3

Class \TYPO3\CMS\Core\View\ViewFactoryInterface has been added as a generic view factory interface to create views that return an instance of \TYPO3\CMS\Core\View\ViewInterface . This implements the "V" of "MVC" in a generic way and is used throughout the TYPO3 core.

You can inject an instance of the \TYPO3\CMS\Core\View\ViewFactoryInterface to create an instance of a \TYPO3\CMS\Core\View\ViewInterface where you need one.

Note

Extbase-based controllers create a view instance based on this factory by default and which is accessible as $this->view.

EXT:my_extension/Classes/Controller/MyController.php (Not Extbase)

<?php

namespace MyVendor\MyExtension\Controller;

use Psr\Http\Message\ServerRequestInterface;
use TYPO3\CMS\Core\View\ViewFactoryData;
use TYPO3\CMS\Core\View\ViewFactoryInterface;

final readonly class MyController
{
    public function __construct(
        private ViewFactoryInterface $viewFactory,
    ) {}

    public function myAction(ServerRequestInterface $request): string
    {
        $viewFactoryData = new ViewFactoryData(
            templateRootPaths: ['EXT:my_extension/Resources/Private/Templates'],
            partialRootPaths: ['EXT:my_extension/Resources/Private/Partials'],
            layoutRootPaths: ['EXT:my_extension/Resources/Private/Layouts'],
            request: $request,
        );
        $view = $this->viewFactory->create($viewFactoryData);
        $view->assign('mykey', 'myValue');
        return $view->render('path/to/template');
    }
}

The ViewFactoryInterface needs an instance of \TYPO3\CMS\Core\View\ViewFactoryData , which is a data object and should therefore be created via new.

Best practices in creating a ViewFactoryData instance:

Hand over request of type \Psr\Http\Message\ServerRequestInterface if possible. See Getting the PSR-7 request object.
Use the tuple $templateRootPaths, $partialRootPaths and $layoutRootPaths if possible by providing an array of "base" paths like 'EXT:my_extension/Resources/Private/(Templates|Partials|Layouts)'
Avoid using parameter $templatePathAndFilename
Call render('path/within/templateRootPath') without file-ending on the returned ViewInterface instance.