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.
Backend User Invite 0.0.2 is now available as its first public beta, providing a cleaner invitation-based onboarding workflow for TYPO3 backend users.
What I learned using Kirby for everything from marketing sites to flexible, content-driven platforms.
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.
The talk I gave in Karlsruhe at TYPO3 Developer Days 2026 — why the TYPO3 backend is a serious framework for business applications. Scroll through the full deck.
Should we modernise the existing platform, or would it be more economical to start over from scratch?
When open source is discussed, many conversations focus on new features, security updates or release cycles. It is far rarer to talk about why companies invest time, money and experienced developers at all, even though such investments can seldom be attributed directly to a single client project. This is exactly the question that has occupied us again and again for some years.
