Skip to content
Sign In Create account
WordPress engineering

WordPress, from a blank page or from a broken one.

We build WordPress properly — themes written from scratch, plugins built for the job, WooCommerce that fits the business — and we take over the projects that have grown difficult. Custom code, not a page builder and a pile of extensions.

One reply, from the engineer who would do the work. No sales sequence.

Why Digipacket

A specialist, not a generalist who also does WordPress.

WordPress is a platform with twenty years of decisions behind it. Knowing which of them apply to your project is most of the job.

WordPress is the specialism

Not one framework among several. The hooks, the query layer, the block editor, the update path and the ways each of them goes wrong are the ground we work on every day.

Written, not assembled

A theme built for your content instead of a bought one bent into shape, and a plugin written for the requirement instead of four plugins that nearly cover it. Less code to run, and less to break.

We read code we did not write

Most serious WordPress work starts in somebody else's codebase. Taking one over — reading it, stabilising it, then changing it safely — is a skill in itself, and it is one we practise.

Reviewed in the open

Our plugins are published in the official WordPress.org directory, which means the plugin review team read the code before anyone could install it. You can read it too.

What we do

Eight kinds of WordPress work.

From a first site to a platform several teams depend on — and everything that goes wrong in between.

Custom WordPress sites

Showcase, corporate, e-commerce and business platforms, built around what the site has to do rather than around a template that already existed.

Themes from scratch

A clean architecture, a design that is yours, and markup that stays fast and editable as the site grows.

Custom plugins

Business logic, API integrations, automations and the complex extensions that no directory plugin will ever cover.

WooCommerce

Checkouts, product models, payment and shipping integrations built to fit how you actually sell.

Difficult problems

Critical bugs, plugin and theme conflicts, performance collapses, server errors, migrations and security incidents.

Large projects

Architecture, refactoring, scaling and evolving a platform that people already depend on, without stopping it.

Audit and optimisation

A read of an existing project that names what is blocking it and what it would take to fix — in that order.

Maintenance and evolution

Ongoing work on projects where an outage costs something, with the same people who already know the codebase.

Not sure which of these your project needs? Describe it and we will tell you — including when the answer is that you do not need us.

Describe your project

Built for you

Where the difference is made.

Two decisions separate a WordPress site that ages well from one that has to be rebuilt in three years. Both of them are ours to get right.

Themes from scratch

A theme that was written for your content.

A bought theme carries every feature its author could imagine, and your site pays for all of them on every page load. Writing one means the templates match your content model, the CSS is the CSS your design needs, and the editor offers your team the blocks they actually use — nothing more to configure, nothing more to break.

  • A clean architecture — templates, parts and blocks that map to your content
  • Design implemented as designed, not approximated by a builder
  • Fast by construction: no unused framework, no imported kitchen sink
  • Responsive across the range, and tested there rather than assumed
  • Built to be extended, so year three is a change and not a rebuild
Custom plugins

The functionality that does not exist yet.

Every business has a rule that no directory plugin implements. Bolting four half-fitting extensions together to approximate it is how a site becomes fragile. A plugin written for the requirement does one thing, is the only thing to update, and can be read by whoever inherits it.

  • Business logic modelled properly, not forced into a form builder
  • API integrations — CRM, ERP, payment, logistics, internal services
  • Automations that remove a manual step rather than moving it
  • Complex extensions: custom post types, roles, workflows, admin screens
  • Written to WordPress coding standards, so any developer can pick it up

Complex projects

Your WordPress has become complicated.

We take it over, stabilise it, make it fast, and make it possible to change again. Inherited codebases are not a special case here — they are most of the work.

What people usually arrive with

  • A critical bug nobody can reproduce
  • Plugin and theme conflicts after an update
  • Pages — or the admin — that have become slow
  • White screens, 500s and memory limits
  • A migration that went wrong, or one nobody dares start
  • A security incident, or a site flagged as compromised
  • PHP or WordPress versions that can no longer be upgraded
  • Years of technical debt and no safe way to change anything

How a takeover goes

  1. Stabilise first

    Stop the bleeding before touching anything else: the breakage in front of you, reproduced, understood and fixed.

  2. Then understand

    A read of the codebase, the data model and the hosting, so the next change is made with the whole picture rather than around it.

  3. Then make it fast

    Queries, assets, caching and the plugin load — measured before and after, because an optimisation nobody measured is a belief.

  4. Then make it changeable

    Refactoring where it pays for itself, so the platform can take the features the business wants next.

Tell us what is happening. If it is something you can fix yourself in an afternoon, we will say so.

Describe the problem

How we work

Seven stages, and none of them is a surprise.

The same path whether the project starts empty or arrives with ten years of history behind it.

  1. 01 Audit What exists, what it does, and what is actually in the way.
  2. 02 Architecture The shape of the solution, agreed before any of it is written.
  3. 03 Development Custom code, to WordPress standards, in versioned increments.
  4. 04 Testing Function, performance, browsers and the upgrade path.
  5. 05 Deployment A planned release with a way back, not a Friday upload.
  6. 06 Optimisation Measured, tuned, measured again — on the real site.
  7. 07 Evolution The next thing the business needs, on foundations that take it.

Start here

Tell us about your project — or your problem.

A few lines is enough. You will get an answer from somebody who has read it, not an acknowledgement from a queue.

Most enquiries are answered within one business day.