Insights into our work: TYPO3 upgrades, engineering practices and how we work with agencies.
Selecting Schema.org types is only one part of a TYPO3 GEO project. Real implementations require an understanding of semantic differences, customer data and the lifecycle of changing content. Two consulting examples show why GEO concepts and TYPO3 engineering should be developed together.
Why agencies working with Symfony, Pimcore or Shopware should consider TYPO3.
A CEO's engineering perspective, updated following the European Commission's CRA guidance of 27 July 2026.
Turning an internal tool into a commercial TYPO3 extension makes you a software manufacturer — and the Cyber Resilience Act expects manufacturers to know what their product contains. A practical look at Software Bills of Materials for the PHP and frontend parts of a TYPO3 extension.
Many companies invest in better developers. We additionally invest in better processes. Both matter, but in our experience lasting quality only emerges when experience no longer accumulates merely in the minds of individual developers, but becomes part of the engineering process step by step.
The larger an upgrade becomes, the more important the question of how to organise the process. After more than 150 TYPO3 upgrades, we have come to believe that many projects become needlessly complicated because they follow TYPO3's upgrade path rather than the architecture of the target system.
