Room for an improved UiTinVlaanderen with Drupal
In 2019, the technical basis of UiTinVlaanderen was a Drupal website, with the focus mainly on the possibilities for the editors who provided the websites with essential content. They used Drupal purely for the editorial work: activities, trips, tips and more. Activities that come straight from the UiTdatabase.
There was no question regarding the choice of Drupal as an editorial system, something that we as Drupal experts could only applaud. However, there was room for an improved digital UiTinVlaanderen, with new links to improve functionality and external APIs. Think new integrations that make optimal use of the comprehensive UiTdatabase.
A centralised leisure agenda for Flanders and Brussels
A headless website and central GraphQL back-end layer for API integration.
About UiTinVlaanderen
UiTinVlaanderen inspires everyone with activities in the largest leisure calendar of Flanders and Brussels. Hiking and cycling, cultural performances and spots, events and all other possible activities, entered by organisers themselves. Choose from thousands of activities in every region and get out the door ... or experience it online.
Headless as the driver of omnichannel ambitions
UiTinVlaanderen had been working for some time with an internal development team, full of technical specialists with their own vision of the future. Even before the collaboration was officially a fact, both development teams put their heads together and came to a common conclusion: a headless CMS to provide the website with editorial content.
Today, the presentation layer is disconnected from the CMS and the content is managed in a separate environment. A central GraphQL layer makes the link with the various customer systems (UiTiD, UiTPAS, UITdatabase, Drupal) and thus provides a single point of contact for the front-end, so that it only has to focus on the presentation. As a result, additional integrations can be added quickly, and each part can be managed by a separate team - with specific their specialist knowledge.
GraphQL - for a reliable back-end foundation
For the GraphQL layer, the teams chose Apollo, partly at the suggestion of the iO specialists. With Apollo you have a well-known platform to build the GraphQL layer of the base in NodeJS. Apollo is supported by extensive logging functionality. The paid version is also an interesting option that provides continuous insight into the ups and downs of each API, in case of error messages, an above-average number of requests or executed API calls. Everything can be followed up completely online.
GraphQL makes APIs faster, more flexible, and developer-friendly. With GraphQL as an intermediate layer, developers can build requests that retrieve data from different data sources, all in a single call.
"A central GraphQL layer makes the link with the various customer systems (UiTiD, UiTPAS, UiTdatabase, Drupal) and thus provides a single point of contact for the front-end, so that it only has to focus on the presentation."
A close collaboration, ongoing and sprint-based
iO teams and the vzw public have been in close cooperation for three years now. To date, the website has been created through the joint efforts of developers from both organisations. They distributed code reviews among themselves, helped by the short lines of communication and the smooth de-escalation of technical problems. The in-house developers knew their own APIs inside out, as well as their own internal culture and that of the various stakeholders. A big advantage.
Because the customer was closely involved in this project, they were also able to monitor the process efficiently and pick up when certain functionality was not in line with the customer vision, for example, or catch new integrations that had no place on the internal roadmap. We had these conversations during the development phase, and at the end of each sprint. Our close cooperation meant we wasted less time and resources.
We helped UiTinVlaanderen with
A future full of (new) components
The iO and UiTinVlaanderen story is far from over, as a permanent partner we remain involved in the project providing aftercare and optimisation. Both teams regularly review the internal roadmap to determine the next steps. Today, these are redesigns of the Tips pages, as well as new components to improve the user experience.
UiTinVlaanderen also regularly enters dialogue with their users to gauge desired improvements, from minor change requests to complete redesigns. Our experts then link back their own insights, proactively and data-driven.
Would you like to improve digital experiences for your users?
Get in touch with us at iO. We would love to hear about what you want so that we can see how we can help. Transformation of your digital ecosystem, for example? In line with your story and your brand DNA.
