02 / 05Drupal + Next.js commerce platform
Lexibook
Built by the Rush Hour Digital team. I worked across the Drupal and Next.js layers as one of its full-stack developers.
- Client
- Lexibook
- Delivered by
- Rush Hour Digital
- My role
- Full-stack developer, RHD team
- Stack
- Drupal · Next.js · React · PHP · Lando
- Scope
- Drupal structures, Next.js storefront sections, multilingual delivery
- Live
- lexibook.com ↗

01Overview
Lexibook is a live Drupal and Next.js commerce experience with a multilingual storefront, product browsing and CMS-backed promotional content.
02Challenge
Multilingual catalog, campaign and CMS content had to move through one delivery pipeline without turning the Next.js storefront into a brittle set of one-off templates.
03My role
As part of the Rush Hour Digital team, I worked across Drupal structures and Next.js rendering — turning CMS and catalog data into reusable commerce sections instead of one-off page builds.
04Architecture
L1
Drupal CMS + APIs
L2
Catalog & commerce data
L3
Next.js storefront + routing
L4
Lando shared local env
05Key challenges
- 01Keeping localised content, product data and promotional layouts in sync as Drupal structures evolved.
- 02Building frontend sections that absorb CMS variation without hard-coded templates.
- 03Shipping changes in a live commerce environment where content, catalog and presentation move together.
06Decisions
- 01Drupal as the content and integration backbone; the customer-facing experience in Next.js.
- 02CMS structures mapped to reusable frontend sections rather than one page shape.
- 03Shared local tooling (Lando) so every developer works against the same environment.
07Result
The storefront stayed modular as product and merchandising requirements changed across locales — editors manage merchandising in Drupal while the frontend stays fast.
08Screens

Next project
NSW Law Reports
Drupal + Next.js legal publishing platform · Rush Hour Digital