Extbase & Fluid Standalone Fluid The Fluid rendering engine of TYPO3 CMS is replaced by the standalone capable Fluid which is now included as a composer dependency The old Fluid extension is converted to a so-called Fluid adapter which allows TYPO3 CMS to use standalone Fluid New features/capabilities have been added in nearly all areas of Fluid (see docs.typo3.org for further details) Most importantly: several of the Fluid components which were completely internal and impossible to replace in the past, are now easy to replace and have been fitted with a public API Standalone Fluid also improves backend performance TYPO3v8LTS - What’s New

Extbase & Fluid Rendering Context (1) The most important new piece of public API is the RenderingContext The previously internal-only RenderingContext used by Fluid has been expanded to be responsible for a vital new Fluid feature: implementation provisioning This enables developers to change a range of classes, Fluid uses for parsing, resolving, caching etc. This can be achieved by either including a custom RenderingContext or manipulating the default RenderingContext by public methods. TYPO3v8LTS - What’s New