Chevening
Replaced a scholarship application system handling thousands of applications a year, with design partner Webb & Webb.
Read the case study: Chevening →
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.
Where you're starting from
- Drupal 7
- Drupal 10
- WordPress
- Other CMS
Where you go next is decided in the Blueprint. Sometimes the answer is to upgrade.
Which situation are you in?
Good fit
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.
A content model built around how you publish.
Good fit
Many editors, many rules
Departments that publish their own sections, approval workflows and permissions that need to be precise. Drupal does this as standard.
Roles and workflows your teams can run.
Already on it
An existing Drupal site
Upgrading from Drupal 7 or Drupal 10 is a migration in its own right. That has its own page.
See Drupal migration and upgrades.
What usually goes wrong, and how we stop it
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.
1
Module sprawl
Contributed modules chosen deliberately, kept current, and only where they earn their place.
2
Custom code
Custom modules documented and tested, so another developer can pick them up.
3
Upgrades
Built to stay on supported versions, so the next major upgrade is an update rather than a rebuild.
4
Editor experience
Editing screens designed for the people who publish, not left as the default admin.
5
Performance
Caching and hosting planned for real traffic, including the spikes.
6
Accessibility
Built to WCAG 2.2 AA, including the editing experience.
How a Drupal build runs
- DiscoveryWorkshops, content and integration inventory, decision log.
- ArchitectureContent model, roles, workflows, integrations.
- BuildStaged releases, reviewed with your content owners.
- LaunchContent migration, redirects, performance and accessibility checks.
- HandoverTraining, documentation, support through WebsiteSupport.io.
Projects we've built
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.
Read the case study: University of London Housing →Questions
If yours isn't here, it's usually quicker to ask on the phone.
Is Drupal right for us?
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.
Is Drupal expensive to maintain?
It doesn't have to be. Keeping to supported versions and a lean set of modules keeps maintenance predictable.
We're on Drupal 7 or 10. Where do we start?
With the Drupal migration and upgrades page, which covers each version and what moving off it involves.
After launch
Drupal support and maintenance →Already live? WebsiteSupport.io looks after it
Once a Drupal site is live, our sister company WebsiteSupport.io keeps it patched, monitored, hosted and improving.
Start with a Blueprint!
Three weeks, from £5,500 + VAT. Credited against the build, and yours to take to any supplier.