Simon Praetorius
Simon Praetorius
The extension adds a few TypoScript options to `lib.contentElement` which should be explained in the documentation. How to specify those options per column should also be mentioned: https://techblog.sitegeist.de/responsive-images-with-typo3-8-7/#comment-4
It should be possible to specify/overwrite the image quality option. Ideally, it should be possible to specify multiple qualities, e. g. to generate lower-quality for high dpi images.
Currently, the ImageViewHelper only partially supports the c and m suffixes for manually specified height and width. One possible solution could be to convert the specified values to a crop...
Currently the styleguide throws TYPO3 exceptions.
Previously, individual asset uris could only be resolved if there was a valid manifest file. Now, the resource.vite ViewHelper uses the vite dev server when it's active. Resolves #52
`` should be ``. The intention was to stay consistent with TYPO3 VH naming... well, this didn't work apparently. :)
For example: * Paths in SCSS files * Fluid Styleguide integration * Backend integration * Multiple entrypoints and code splitting
There should be an "advanced" option to define multiple dev server configurations and to mix pre-built assets with dev server. For example: ```php [ 'EXT:sitepackage/Resources/Public/Vite/.vite/manifest.json' => [ 'useDevServer' => true,...
RoundViewHelper, CeilViewHelper and FloorViewHelper provide three different ways of rounding to Fluid template. ## Examples ```xml ```