Drupal and headless CMS development
Decoupled and traditional CMS platforms on Drupal, Strapi and Sanity, where editors keep a workflow they recognise and the front-end stays fast.
I have worked with Drupal for most of my career, from themed sites to decoupled platforms where Drupal manages content and access control and a React or Astro front-end renders it.
My rule is to decouple where it earns its keep and stay monolithic where it does not. A headless setup gives the front-end freedom and performance, but it costs editors their preview and their layout control unless you design for that. I build the editorial experience with the same care as the public site.
What this covers
- Decoupled Drupal with GraphQL
- Custom Drupal modules and field widgets
- Flexible content modelling with Paragraphs
- Astro and Next.js front-ends on Strapi and Sanity
- Payment and CRM integrations
- Editor experience and WYSIWYG tooling
Where I did this
- Scapino Ballet Rotterdam (2023): A flexible Drupal build on reusable blocks and the Paragraphs module, integrated with Mollie for payments and ActiveCampaign for marketing.
- GeodataPro (2025): Drupal 10 as the editorial and access-control layer behind a schema-first GraphQL API and a React portal.
- TipTap WYSIWYG for Drupal (2024): A custom Drupal module that replaces CKEditor with a TipTap editor, built with Vite and loaded as a single ES module.
Related writing
By Guus van de Wal, Senior Front-end Developer & UI Engineer.