BUILD
Drupal, built and looked after by people who know it.
Drupal runs serious websites for organizations that need structured content, real editorial workflow and detailed permissions. We build on it, maintain it, upgrade it and support it.
Structured content with real relationships, editorial workflow with approval stages, detailed permissions across many editors, and multilingual content that's actually maintained.
What we do on Drupal sites.
Development
Custom modules and functionality, written to Drupal conventions.
Troubleshooting and repair
Sites that are down, throwing errors, or behaving differently for logged-in users.
Version upgrades
Drupal 7 sites past end of life, and Drupal 9 to 10 and 11. In practice, a migration.
Security updates, applied promptly
Drupal advisories are public and specific, so an unpatched site is a documented target.
Module work
Updates, patches, and replacing modules that have been abandoned.
Hosting and infrastructure
The server, PHP version, database and caching layer underneath.
- Drupal 9 / 10 / 11
- Drupal 7 legacy
- Twig
- Composer
- Drush
- Custom modules
- Views
- Migrate API
- Patch management
- PHP 8
- MySQL
Working in Drupal.
It isn't as hard as its reputation
Drupal is known for being difficult, which is mostly a reputation for being unforgiving of sloppy work. Built well and kept current, it's an excellent platform for structured content, complex permissions, multilingual sites and organizations with real editorial processes.
End of life is a real deadline
When a Drupal major version reaches end of life, the security team stops issuing advisories for it. The site keeps working, which is exactly why organizations leave it. What changes is that new vulnerabilities stay open permanently.
What to expect
- We check the version and what's patched
- We read the build
- We work out whether it can be updated in place
Ongoing maintenance is quoted on what your site actually needs. Upgrades and migrations are scoped after a review.
Drupal questions.
We're still on Drupal 7. How bad is that?
It's out of official support, so new vulnerabilities in core and contributed modules won't be fixed. Commercial long-term support exists and is a reasonable stopgap, but it isn't a plan.
Can you just maintain it? We don't want to change anything.
Yes, and that's a sensible position for a site that does its job. Updates, security patches, backups, monitoring and someone to call. Drupal maintenance is quoted rather than sold as a plan, because what a Drupal site needs each month depends on how it was built.
Should we move off Drupal?
Only if the reasons Drupal was chosen no longer apply. If you need structured content, workflow and fine-grained permissions, moving costs you capability you're relying on.
Drupal work is quoted on what your site actually needs, one-off or monthly. There is no plan that pretends otherwise.
Not what you need? See all three ways we work
Drupal site that needs attention?
Tell us the version, roughly when it was last updated, and what's worrying you. We'll give you a straight read on it.
Rather talk it through? Call 833-336-6453.