WordPress, properly engineered from the server up
I bring the same engineering discipline to WordPress that I apply to Drupal. Custom themes, plugin development, WooCommerce, third-party integrations and performance optimisation — handled by a software engineer who understands your site from the server up.
Whether you need ongoing development to extend what your site does, or reliable maintenance to keep it secure and performing well, I provide both. This is not someone clicking Update in the dashboard; it is proper engineering with infrastructure-level thinking.
Development work
- Custom theme development. A theme built for your site rather than a bought one bent into shape.
- Plugin development and customisation. New functionality where no plugin does what you need, and disciplined changes where one nearly does.
- WooCommerce. Checkout, shipping, payment and integration work on stores that have outgrown the defaults.
- Third-party integrations. CRMs, payment providers and APIs, connected properly and kept working.
- Performance optimisation. Caching, database queries and front-end weight, tuned with the server in view as well as the site.
- Hosting migration. Moving a site to hosting that suits it, without losing content, mail or search rankings on the way.
Ongoing maintenance
WordPress rewards attention and punishes neglect more quickly than most platforms, because so much of a typical site is third-party code — core, theme and plugin updates applied and checked rather than left to auto-update and hoped over.
Security hardening, backups and performance monitoring are the same discipline, sold as their own thing for a site that just needs to stay healthy: see Maintenance & Support.
Where WordPress sits in my work
Drupal is my primary specialism, and I would rather say so than imply otherwise. What that means for a WordPress client is not less attention — it is a developer whose habits were formed on a platform with stricter conventions, applying them here.
It also means the infrastructure comes with the same person. If your site needs a server change, a caching layer or a deployment pipeline, that is the same conversation rather than a different supplier.
Work is a monthly retainer with development hours included, or pay as you go for lighter needs. Either way you deal directly with the person who writes the code and manages the server.
Tell me about your WordPress site
What it does, what it needs, and what is currently going wrong with it. I will tell you honestly whether a retainer or pay as you go makes more sense, and roughly what it would involve. I usually reply within one to two working days.