Drupal 7 to Drupal 9 migration of the University of Applied Sciences website

Frontend component development

We used Storybook to build and test UI components in isolation from Drupal before combining them into full-page layouts. This made it easier to design and validate components independently of backend logic. A Theme Processor layer connected Drupal data structures to frontend components, simplifying integration and helping keep a consistent design system across the website.

Integration architecture

The platform integrates with external systems like DIAS (for displaying job vacancies), BITE (for displaying official announcements and university rules), Opus 4 (for lists of publications), and a personalized podcast player via an iframe.

Component-driven page model

The platform was built on a Paragraph-based setup, where pages are built from reusable components rather than fixed templates. This gave editors more freedom to build and update content, while keeping everything consistent across thousands of pages and two languages. Separating structure from design also made the system easier to scale and maintain without breaking layouts.

Shared content update

To reduce repetitive work, shared data, such as application periods, was moved out of individual program pages into dedicated content entities. Editors can now update information in one place instead of repeating the same changes across multiple pages. This keeps content consistent, reduces the risk of outdated information, and makes ongoing maintenance much easier.

Department-based access

We moved access management to a department-based group model instead of a central permission system. Each department now works within its own space, with roles like Assistant, Editor, and Administrator handling content creation, review, and publishing. Now departments can manage pages, users, roles, and permissions directly in the admin interface, making changes much faster and easier without technical support.

Structured editorial workflows

Publishing was implemented as a workflow-driven process with clearly defined content states and approval stages. Content creation and publication rights were separated, ensuring that editorial review remained part of the publishing lifecycle. This structure allowed hundreds of contributors to participate in content creation while maintaining governance and accountability across departments and faculties.

Performance optimization

In the old system, image quality was inconsistent because hundreds of contributors uploaded files in different sizes and formats. We solved this with an automated pipeline using Drupal Image Styles and custom logic. Editors upload images once, and the system generates optimized versions for different layouts, screens, and devices, removing manual work, improving consistency, and boosting performance.

Security and maintainability

We built the platform primarily on Drupal core and trusted community modules, adding custom code only when necessary. Where possible, we extended existing modules rather than them. This reduced long-term maintenance, made upgrades easier, and ensured the system followed Drupal security best practices while staying aligned with community updates.