Sector(s)

Team Members

aninaangehrn, ancaverniceanu, czigor, dulnan, milanbombschliip, mariuskueng, siegrist, tonsibonsi, vrancje, andreylugovtsov, remoregli

Project Team

Oris SA

  • Dominic Guye (Project Lead)
  • Vanessa Vögtli (Project Lead deputy)

Jung von Matt (Design)

Wortspiel (SEO)

Visit the site

Visit the site

Organizations Involved

Community contributions

The development of the Commerce Giveaway module, primarily for Oris, contributed valuable functionality to Drupal’s commerce ecosystem. This module supports promotional giveaways, providing a useful tool for managing such campaigns within Drupal Commerce.

As part of the project, contributions were also made to related modules, including GraphQL Commerce (graphql_commerce) and GraphQL Core Schema (graphql_core_schema). Several commits improved these modules, enhancing their functionality and integration, and benefitting the broader Drupal community.

The recent project between Swiss watchmaker Oris and digital agency Liip centred on creating a modern, user-friendly website to enhance the brand’s online presence. Oris, known for its precision timepieces, sought a digital upgrade that matched its craftsmanship standards. 

Liip, leveraging its expertise in Drupal CMS and Nuxt for front-end development, streamlined Oris’s digital infrastructure. This collaboration tackled challenges like adapting product information across markets, ensuring a smooth launch. The result is a sleek, high-performance site that reflects Oris’s identity and supports future digital growth.

Describe the project (goals, requirements and outcome)

The Oris website project aimed to modernise the brand’s online presence, enhance user experience, and streamline content management by consolidating key features into a single Drupal-based system. Key requirements included integrating e-commerce functionality, managing regional product variations, and creating a design that reflected the brand's identity. The project followed a clear timeline, with major milestones such as a soft launch for testing, editor onboarding session, and the final go-live.

A collaborative and iterative project management approach was used, emphasizing open communication and decision documentation. Early challenges, like adapting designs to Drupal’s structure and the team’s unfamiliarity with a decoupled setup, were mitigated by onboarding experienced staff and fostering direct collaboration with Oris’s editors. This process strengthened client relationships and ensured a smooth content migration.

The project significantly improved, including faster website performance and easier content updates through the Blökkli editor. The modernised platform enhanced the user experience and laid the foundation for ongoing development, positioning Oris for future digital growth

Why Drupal was chosen

Drupal was chosen as the CMS for the Oris project because key components, such as the checkout and member login, were already built on it. Consolidating all functionalities within Drupal streamlined the system architecture, simplifying maintenance and reducing complexity. Drupal’s flexibility and scalability ensured it could handle the project’s requirements, including integrating product data and managing regional variations. This unified approach improved efficiency, allowing for a cohesive user experience and easier content management.

Technical Specifications

Drupal version:

Key modules/theme/distribution used:

Why these modules/theme/distribution were chosen

We use drupal/commerce, as it is a good solution and structure for an e-commerce shop, which oris.ch is. We used GraphLQ instead of Rest or JSONAPI to be more flexible in the frontend programming. Since we have a decoupled site with a Nuxt frontend, frontend devs are happy to not rely on backend devs to provide data through an extra API, but just query the data they need through GraphQL.

For responsive images we use Rokka and therefore also used the Drupal Rokka module. Editors can upload images and video with this and we only serve the IDs to the frontend so it can then query the appropriate image (dimension and resolution) from Rokka.

The search_api is together with SOLR used in multiple places. On the one hand, for the search for watches or service locations on the website for end users. On the other hand, in the backend, to search through all customers and their watches to enable a good CRM experience for the Oris employees.