Platforms
Some work arrives named after a platform rather than an outcome. These pages give that request somewhere to land, and show how the work is done before you have to ask.
These are not separate practices. They are the platforms the engineering discipline is practised on, delivered through the same engagements as everything else.
Established platforms, extended without fighting them.
WordPress theme & plugin development
Custom WordPress development for sites that have outgrown what a purchased theme or an off-the-shelf plugin can do—built as themes, plugins and integrations rather than as workarounds layered on top of someone else’s code.
Drupal module & theme development
Drupal development for organisations whose content, permissions or integrations are too structured for a simpler platform—custom modules, custom themes and the migrations between versions that tend to get postponed.
Shopify theme & app development
Custom Shopify development for merchants whose product, checkout or operations need behaviour the theme editor cannot express—custom themes, private apps and the integrations that connect a shop to the systems behind it.
Progress Sitefinity development
Development on Progress Sitefinity for organisations running it as an enterprise platform—custom widgets, page templates and the integrations that connect it to internal systems, with the governance such an environment usually carries.
Applications where the business logic is the point.
Laravel API & application development
Laravel development for applications that carry real business rules—REST APIs, MVC applications and the integrations between them—structured so the logic stays testable and legible as the application grows.
Node.js API & backend development
Node.js development for the server side of a product—HTTP APIs, background workers and the integrations between systems—written so that behaviour under failure is as defined as behaviour when everything works.
React & Next.js development
React and Next.js development for product interfaces that have to keep working as they grow—clear component boundaries, a deliberate line between server and client, and performance treated as a requirement rather than a later optimisation.
Angular application development
Angular development for applications with a long life ahead of them—typed, structured and conventional enough that the next team can read the code without an introduction from the last one.
Vue.js application development
Vue development for teams who want a clear component model without committing to a full rebuild—whether that is a complete application or a considered introduction of Vue into something that already exists.
Python automation, APIs & data tooling
Python for three related jobs: automating work that people are doing by hand, building APIs and services with Django or FastAPI, and the data and AI tooling that sits alongside them—each written to be run again by someone other than its author.
A clear next step
Get preliminary direction first, or book a focused session when the question is ready.
