Drupal development
Where we are deepest, and why it isn't always the answer.
We've built on Drupal since 2009. It suits organisations with complex content models, many editors, fine-grained permissions and serious integrations. When it doesn't suit, we say so.
Which situation are you in?
Complex content
Many content types, structured relationships between them, and an archive that has to stay findable. Drupal's content model handles this without plugins fighting each other.
Many editors, many rules
Departments that publish their own sections, approval workflows and permissions that need to be precise. Drupal does this as standard.
An existing Drupal site
Upgrading from Drupal 7 or Drupal 10 is a migration in its own right. That has its own page.
The risks we manage
Drupal projects go wrong when they lean on too many contributed modules, or too much custom code that only one developer understands. We keep both to what the project needs.
Module sprawl
Contributed modules chosen deliberately, kept current, and only where they earn their place.
Custom code
Custom modules documented and tested, so another developer can pick them up.
Upgrades
Built to stay on supported versions, so the next major upgrade is an update rather than a rebuild.
Editor experience
Editing screens designed for the people who publish, not left as the default admin.
Performance
Caching and hosting planned for real traffic, including the spikes.
Accessibility
Built to WCAG 2.2 AA, including the editing experience.
How a Drupal build runs
Workshops, content and integration inventory, decision log.
Content model, roles, workflows, integrations.
Staged releases, reviewed with your content owners.
Content migration, redirects, performance and accessibility checks.
Training, documentation, support through WebsiteSupport.io.
Projects we've built
All case studies →
Chevening
Replaced a scholarship application system handling thousands of applications a year, with design partner Webb & Webb.
University of London Housing
Replaced the accommodation service's platform so students and landlords could find each other, and the team could run it themselves.
Questions we get asked
If yours isn't here, it's usually quicker to ask on the phone.
It is a strong fit for complex content, many editors and serious integrations. For simpler sites, WordPress or a headless CMS can be cheaper to run. Discovery answers it with evidence.
It doesn't have to be. Keeping to supported versions and a lean set of modules keeps maintenance predictable.
With the Drupal migration and upgrades page, which covers each version and what moving off it involves.
Book a migration readiness review
A free 30-minute call with a technical lead, then a short written summary of whether Drupal fits and what the build would involve.
020 3608 2525Support, maintenance and hosting for Drupal sites are handled by our sister company, WebsiteSupport.io.
Drupal support at WebsiteSupport.io →