Factory joins Pimcore Community Dev Days and the Partner Advisory Council in Frankfurt
Summary
Our backend developer Ivan Blažević attended Pimcore Community Dev Days 2026 in Frankfurt on November 10, while our CEO Ivica Horvat represented Factory at the Pimcore Partner Advisory Council (PAC). On the developer agenda were three topics close to our day-to-day work: extending the redesigned Pimcore Portal Engine, maintaining applications through framework upgrades and reviewing code written with AI assistance.
Two roles for Factory in Frankfurt
Organized by +Pluswerk and CORS, the second edition of Pimcore Community Dev Days brought the Pimcore, Symfony and PHP communities together at the Holiday Inn Frankfurt Airport. A community dinner on November 9 gave speakers and attendees a chance to catch up before the talks and demos the next morning. The speaker lineup included Pimcore core developer Marvin Bertram, Symfony core team members Alexander M. Turek and Kévin Dunglas, PHPUnit creator Sebastian Bergmann and developer relations specialist Ondřej Chrastina.
The Partner Advisory Council met at the same venue and ran alongside the developer program. With Ivica at the council and Ivan at Dev Days, Factory could take part in both. For our developers, one reason to make the trip was the chance to hear the thinking behind a platform change directly from a core contributor. Release notes can tell you what changed, but a session with the developer gives you room to ask what that change means for a project you already maintain.
Three takeaways from Pimcore Community Dev Days 2026
The redesigned Portal Engine gives developers a clearer view of where custom work begins. Marvin Bertram’s demo went inside the Portal Engine in Pimcore 2026.3. Alongside a walkthrough of the portal itself, the session covered the architectural decisions behind it, how developers can extend it and how it handles change control. Those details matter early in a portal project, when a team is deciding which requirements the platform already covers and which need an extension.
Business rules can outlast the framework they were built on. Alexander M. Turek explored how to keep an application’s core logic stable as its dependencies evolve. Take a product approval workflow: the rule about who can approve a product may stay the same for years. Keeping that rule separate from framework-specific code makes it easier to upgrade the application without having to rework the approval process along the way.
Coding agents need current guidance, and teams still need reliable tests. Ondřej Chrastina used examples from CKEditor, TYPO3 and Drupal to explore a familiar problem: an agent can suggest an integration that was correct a few releases ago. Sebastian Bergmann took up the next question in Speed is a byproduct of trust. Once an agent has proposed a change, what gives a team the confidence to ship it? His examples showed how automated tests and static analysis help developers make that call.
Thanks to +Pluswerk, CORS and the speakers for bringing the community together for a second year!