BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//drupalcamp-kortrijk-2026//speaker//YNCPAT
BEGIN:VTIMEZONE
TZID:Europe/Brussels
BEGIN:DAYLIGHT
DTSTART:20250630T000000
TZNAME:CEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20251026T030000
RDATE:20261025T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260329T030000
RDATE:20270328T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Decoupled frontend with Drupal still behind the wheel - Tom Verhae
 ghe
DTSTART;TZID=Europe/Brussels:20260630T153500
DTEND;TZID=Europe/Brussels:20260630T160000
DTSTAMP:20260811T012300Z
UID:pretalx-drupalcamp-kortrijk-2026-EQP9TA@pretalx.com
DESCRIPTION:[Link to the demo environment](https://dckortrijk.heartdriven.
 com)\n\nIn many Drupal projects\, frontend and backend are tightly coupled
 . Teams often start with the best intentions\, but every greenfield projec
 t evolves over time and that always comes with some form of entropy.\n\nSi
 x years ago\, I started working as a Drupal developer/architect at the Eur
 opean 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.\n\nWe e
 ventually moved to an architecture where Vue.js components are developed a
 nd documented in Storybook\, and then integrated into Drupal Twig template
 s for rendering\, and that's what we'll dive into in this session.
LOCATION:Drupal.be room
URL:https://pretalx.com/drupalcamp-kortrijk-2026/talk/EQP9TA/
END:VEVENT
END:VCALENDAR