Ciment Prompt addresses a varied customer base, from professionals working in heritage restoration to industrial purchasing teams. The website therefore needs to present structured product information and provide services tailored to different user needs.
About the project
Goals
- Promote a natural cement with a very wide range of applications - heritage restoration, decorative works, technical and industrial uses - to four European markets
- Deliver a fast, SEO-efficient public site while keeping a rich, fully administrable content model
- Help professionals and individuals size their projects themselves, and find the nearest point of sale
- Isolate the content back office from the public front end, for both security and performance reasons
Requirements
- A decoupled architecture: Drupal as the content and business back end, a Next.js front end for public rendering
- Four languages - French, English, Spanish, Italian - covering content, menus, metadata and forms
- A product dosage calculator, fully administrable, translatable and revisionable
- A point-of-sale locator fed by imports from the group's information systems, with map display
- Full-text and faceted search across the whole catalogue
- Contact forms segmented by audience and topic, each routed to the right internal team
- SEO parity with a classic Drupal site: metadata, structured data, sitemap, redirections, robots.txt
Outcome
- A Drupal 11 back end exposing its content through GraphQL, consumed by a Next.js front end deployed alongside it
- Four fully translated language versions, with a language negotiation layer adapted to the decoupled context
- A calculator built as a dedicated custom content entity, so marketing can adjust its parameters, labels and translations without any release
- A point-of-sale network imported automatically and rendered on an interactive map in the front end
- Elasticsearch search and suggestions exposed through the GraphQL schema, so the front end queries a single endpoint
- Webforms exposed through GraphQL, keeping form definition, validation and notification logic in Drupal while the front end only renders them
- SEO artefacts - metadata, structured data, sitemap, redirections, robots.txt - served to the front end through dedicated API endpoints, so that decoupling costs nothing in search visibility
- A containerised deployment on Kubernetes, with all traffic between the front end and the search engine routed through an authenticated serverless API gateway
Why Drupal was chosen
Ciment Prompt is a natural cement sold in France and across southern Europe, to an audience ranging from heritage restoration specialists to industrial buyers. Drupal was chosen as the content back end of a decoupled architecture:
- A mature GraphQL layer, letting a JavaScript front end consume precisely the content it needs
- Structured, translatable content modelling, with four languages managed from a single back office
- Custom entity types can be added natively, which was required for the product calculator and the point-of-sale network
- Editorial autonomy preserved despite the decoupled architecture, through a component-based authoring experience
- A robust integration layer for the search engine and the external services the site depends on
- Enterprise-grade security, applied to the content back end that is never exposed directly to the public
Drupal provides the content and business logic, while the front end is free to optimise rendering, SEO and performance independently.
Technical Specifications
Drupal version:
Key modules/theme/distribution used:
GraphQL, Consumers and the Next.js front end are what make the decoupled architecture work. Rather than exposing a generic REST surface, dedicated schema extensions were built on top of the GraphQL module to publish exactly the operations the front end needs - content, Elasticsearch queries and suggestions, webform definitions and submissions, SEO artefacts. The front end therefore talks to a single, typed, versionable endpoint, the Drupal back end is never exposed directly to public traffic, and Next.js is free to optimise rendering, caching and search-engine visibility independently.
Content modelling and editorial autonomy rely on Paragraphs, Webform, Conditional Fields, Only One and Unique Field Ajax. More than forty Paragraph types describe every block the front end can render, so adding a section to a page remains an editorial action even in a decoupled setup, across the four language versions. Webform keeps form definition, validation and notification logic inside Drupal while the front end only renders them. Conditional Fields keeps complex editing forms manageable by revealing fields only when they apply, Only One prevents duplicate singleton pages such as the homepage, and Unique Field Ajax guarantees the uniqueness of the identifiers used by the front end as it builds its routes.
Config Pages and Geolocation cover the global settings and the point-of-sale network. Config Pages holds the parameters the front end reads at build time - contact details, global call-to-actions, front-end feature switches - so marketing can change them without a release. Geolocation positions the network of points of sale, imported automatically from the group's information systems, and exposes the coordinates the front end renders on its interactive map, one of the site's main conversion paths alongside the product dosage calculator.