Tom Verhaeghe
I’m a developer at the European Commission since 2019 (DG Education and Culture) with nearly 18 years of experience in both frontend and backend development. Over the years, I’ve worked on a wide range of Drupal projects, with a strong focus on building maintainable and long-term solutions.
I live in Marke (Kortrijk) and I'm a father of three. Outside of work, I enjoy music and playing drums, snowboarding and tinkering with hobby electronics.
Session
Link to the demo environment
In many Drupal projects, frontend and backend are tightly coupled. Teams often start with the best intentions, but every greenfield project evolves over time and that always comes with some form of entropy.
Six years ago, I started working as a Drupal developer/architect at the European Commission. Around that time, we began building a platform to power multiple websites. Knowing that we would maintain this platform over the long-term, we revisited the pain points that we had encountered over the years. We explored a different approach to frontend development, with a focus on better reuse across websites of DG Education and Culture.
We eventually moved to an architecture where Vue.js components are developed and documented in Storybook, and then integrated into Drupal Twig templates for rendering, and that's what we'll dive into in this session.