Tailor joined the renewal of a major European tourism portal to build fifteen frontend views. We ended up creating the technical visibility and operating model that turned a blocked multi-partner project into a platform the marketing team could evolve with greater confidence.
The client is the public organisation responsible for promoting one of Europe's leading tourist destinations internationally.
Its digital ecosystem receives around 14 million visits a year, with 80% of traffic coming from mobile devices. Thousands of pages, multiple destinations and dozens of localised versions make it a substantial content and technology operation.
Tailor joined a project already underway, with four organisations responsible for its design, CMS, backend and frontend.
Our initial assignment was to build fifteen views in Next.js on an existing Drupal platform. Once real content entered the interface, a deeper problem surfaced. Fifteen years of legacy structures did not map consistently to the new components, and the teams lacked a shared data contract defining what each layer should deliver.
When a page failed, the cause could sit anywhere between the CMS, migrated content, backend response, mapper and renderer. Diagnosing it meant searching through thousands of lines of nested data. The marketing team remained dependent on several providers to move campaigns and content changes forward.
We developed the Next.js frontend and the integration layer required to transform Drupal's data into consistent component structures.
To manage the wider complexity, frontend lead Juanan Gómez built an agentic engineering system around Codex comprising 13 skills, six specialised agents and 36 reusable commands.
Its central capability, Dynamic Features, traces content through the frontend pipeline and produces evidence of what each page receives, how it is mapped and what appears on screen. Problems that once required lengthy manual investigation can now be located and assigned to the right team in minutes.
The frontend repository became the operational source of truth, connecting code, decisions, reports and workflows in one place.
That visibility allowed Tailor to take responsibility beyond its original frontend scope. Our team began coordinating tasks across providers, clarifying ownership and giving the client a reliable view of progress.
Promotur eventually asked Tailor to take the operational lead, turning an initially scoped implementation role into responsibility for moving the wider project forward.
Tailor turned a scenario shaped by dependencies and recurring blockers into a more agile operating model.
The marketing team can move campaigns and content initiatives forward with greater speed and confidence. Technical issues are traced to their source, responsibilities are clearer and frontend development can continue when another part of the system is unavailable.
Promotur has recovered the visibility and operating capacity needed to use the portal as an active marketing channel while the platform continues to evolve.