Hi,
We (I’m talking on behalf of my team) would like to address our experiences with file processing, specifically encountered during the PWA initiative and ext:headless development. We recognize that currently, image processing is predominantly handled in fluid viewhelpers, a setup that may not be ideal for this kind of logic implementation. To enhance our understanding and approach, we are considering a step back to thoroughly analyze and research this area. Our aim is to develop a detailed, technical blueprint that can outline proposed implementation.
Here’s our roadmap:
- Investigate the current state and identify existing problems.
- Conduct research and analysis of market solutions and find one that fits TYPO3 best.
- Draft a document outlining our next steps and proposals, engage with the core team, and develop a technical concept.
- Feedback loop with core team and community
The expected outcome is a blueprint for technical changes that will guide our further budget considerations.
Regarding your specific questions:
2. Asynchronous frontend image processing and the feasibility of integrating different image processing providers, like imgproxy.
3. Our strategy includes offering a smooth migration path through an abstraction layer, with plans to deprecate the old API eventually.
4. We aim to prepare a technical blueprint for our proposed solution and seek feedback from the core team and the TYPO3 community, improving our solution iteratively.
5. If feasible, we plan to extend coverage to ViewHelpers and TypoScript, adapting them to interact with the image processing service via the new abstraction layer.