Client work

Some of this work was delivered under confidentiality agreements. Those projects appear anonymised: the engagement is described faithfully, but the client is not named, links are withheld, and the imagery is illustrative.

Showing 19 - 20 of 20
Hands writing a reference onto a card beside a research report
A policy report that people can still cite in ten years needs a permanent identifier. We built the Drupal module that mints one for the records the Analysis & Policy Observatory publishes, in partnership with Media Insights.
  • Drupal
  • Custom development
  • Continuous integration
The Victoria University homepage
Victoria University's websites are where prospective students choose a course, researchers get found, and the public meets the institution. We have worked alongside the university's own web team on the platform behind them since 2017.
  • Drupal
  • Migration
  • Updates
  • Performance optimization
  • Custom development

Open Source work

Showing 1 - 8 of 8
The CivicTheme homepage at civictheme.io
Public-sector teams keep rebuilding the same accessible components, site after site. CivicTheme, published by Salsa Digital, turns that repeated cost into one maintained open-source design system, and we have engineered it since its first commit in 2021.
  • Open source
  • CivicTheme
  • Design system
  • UI Kit
  • GovCMS
The Behat Steps logo and name with the tagline 'A collection of Behat steps for PHP and Drupal projects', on a dark background of faded step text
Almost every Drupal project writes the same forty or fifty automated test steps from scratch, then owns them forever. behat-steps is our open-source library of those steps, written once and maintained since 2018.
  • Open source
  • Testing
  • Behat
  • Drupal
  • Automation
The Vortex project template homepage at vortextemplate.com
Every new Drupal project starts with weeks of setup, and every running one drifts into a configuration only its own team understands. Vortex is our answer: an open-source Drupal project template, maintained since 2017, installed once and kept current through the same tool that set it up.
  • Open source
  • Vortex
  • Drupal
  • DevOps
  • Continuous integration
The Eddy home page at eddy.drevops.com, open on a laptop
Your Drupal website runs on contributed modules, and each one has to keep working through every Drupal and PHP update. Eddy is our free, open-source template that gives a module or theme a local site, tests across versions and publishing to Drupal.org from its first commit.
  • Open source
  • Drupal
  • Testing
  • Continuous integration
  • Updates
Nexus open at nexus.drevops.com in a browser on a laptop, showing the Umami content model, in front of a whiteboard of sticky notes
Nearly every decision about a Drupal website depends on its content model, and the model is surprisingly hard to see. Nexus is our free, open-source tool that draws it from the site's own configuration, checks it, compares versions of it and documents it, all in your browser.
  • Open source
  • Drupal
  • Migration
  • Custom development
BATS helpers logo with the line: Write BATS shell tests faster with ready-made helpers, above a passing bats test run
The scripts that provision, deploy and back up a platform run with real credentials against real data, and they are usually the last piece of code anyone thinks to test. bats-helpers is our open-source library that makes testing them practical.
  • Open source
  • Testing
  • Automation
  • DevOps
  • Continuous integration
Git Artifact logo with the line: Deploy a lean copy of your code to Git-based hosting, above a git-artifact command that packaged successfully
Plenty of hosting platforms deploy whatever sits on a git branch, which means the thing you push has to be exactly what production needs and nothing else. git-artifact is our open-source tool that builds that package in CI and pushes it safely, and it has been in service since 2017.
  • Open source
  • Continuous integration
  • DevOps
  • Automation
  • Testing
Behat Screenshot logo with the line: Screenshot your Behat tests on failure or on demand, above a Behat scenario and the screenshots it saved
When an automated browser test fails in a build, the log tells you which check did not pass, not what the page actually looked like. We build and maintain an open-source Behat extension that captures the page itself, automatically on failure or on demand mid-test.
  • Open source
  • Testing
  • Behat
  • Automation
  • Continuous integration