Team Members

prudloff, alexl, dmoret, Samuel Coudron, ymartinez, aliabeva anastasiia

Project Team

Our team included:

  • 1 project manager: monitor and coordinate the project at a overall level, in close collaboration with the Gallimard team
  • 2 engineers – web experts: strategic and functional project management - one for the front-end, one for the back-end
  • 1 web-designer: design UX/UI of the new website (wire-frames and mock-ups)
  • a team of 2 to 4 back-end and front-end developers: realize the operational delivery of the website

Visit the site

Visit the site

Organizations Involved

Community contributions

As usual, we made several contributions to community modules while working on this project: from bug fixes and new features (Custom SQL Migrate Source Plugin, Facets autocomplete, Relative Date Facets) to new contrib modules (Root term condition, MaxLength Auto) and various Drupal 10 compatibility fixes.

In 2024, Gallimard and Insite partnered to migrate and redesign the Gallimard website from ez Publish to Drupal 10.
The aim of this redesign was to provide users with a mobile first and responsive website, to ease the deployment of future functionalities and to provide a better back-office experience for webmasters.

Describe the project (goals, requirements and outcome)

Goals

  • Allow users to browse Gallimard products easily on desktop and on mobile devices
  • Migrate existing books and authors into the new website and keep them in sync with the Gallimard catalog
  • Provide back-office tools that would empower webmasters in their daily work
  • Adopt a stable and up-to-date web platform
  • Make bug fixes and adding new features easier

Requirements

  • Implement catalog imports in a way that minimizes performance impact on browsing the website
  • Implement feature parity with the previous website
  • Connect Drupal with various Gallimard APIs to provide additional functionalities shared with other Gallimard websites

Outcome

  • Improved user experience on mobile
  • More focused back-office experience
  • Continuous integration allows deployment of new features or bug fixes with minimal downtime
  • Drupal release cycle provides a predictable road-map for upgrades
Back to top
Why Drupal was chosen

Gallimard hosts a catalog of more than 60,000 books and Drupal was particularly suited to manage a website with that much content.

Other related advantages were:

  • A strong integration with the Solr search engine
  • The migrate API made scheduled synchronization of books from the catalog easier to implement
  • Drupal’s powerful cache system and integration with Varnish helps maintain scalability on a website with a lot of visits
  • Drupal’s content structure enables an easier management of the many content types on the website

Technical Specifications

Drupal version:

Why these modules/theme/distribution were chosen

We used migrate and related contrib modules to implement a daily synchronization of content from the Gallimard catalog.

Facets and related modules were used to build a powerful search engine allowing users to find the book they are looking for.

Redis, Purge and Cache Control Override were used to implement a multi-layer cache system that ensures the most requested web pages always respond quickly.