CMS Development – Drupal, Joomla, OpenCart and BigCommerce
Most of our work is WordPress, Shopify, Magento and React. But plenty of businesses are running something else and need it supported, fixed, or moved somewhere better maintained. We do that too — and we’ll tell you honestly which of the three it should be.
What we take on
Drupal
Module work, content type and view configuration, upgrades between major versions, and performance work on sites that slowed down as modules accumulated.
Joomla
Extension work, template customisation, version upgrades, and the cleanup that follows a site nobody has touched in a few years.
OpenCart
Store fixes, theme and extension work, payment and shipping configuration, and migrations onto a platform with a larger ecosystem.
BigCommerce
Stencil theme work, app integration, and API connections to the systems that run behind the store.
Security and version upgrades
Unsupported CMS versions are the single most common way a site gets compromised. We’ll tell you what you’re running and how exposed it is.
Migration off, when it’s time
To WordPress, Shopify or WooCommerce — content, data, and a URL map so rankings survive.
The honest version
If you’re on one of these platforms, there are usually three options, and the right one depends on how much the site still earns you:
- Keep it and maintain it. Sensible when it works, the version is still supported, and rebuilding would cost more than it returns.
- Keep it but secure it. If it’s on an unsupported version, that is the urgent problem — before any feature work.
- Move it. When every change needs a specialist, finding anyone who knows the platform is hard, and the ecosystem has thinned out.
We’d rather maintain a site that’s working than sell you a rebuild you don’t need. We’d also rather say “move this” than keep patching something at end of life.
Finding support is the real issue
The practical problem with these platforms usually isn’t the software. It’s that the pool of developers has shrunk, so:
- Quotes come back high, because few people will take the work
- Extensions get abandoned and stop receiving security fixes
- Hosting support knows less about your stack each year
- Your own staff turnover leaves nobody who understands it
None of that means move immediately. It does mean the cost of staying rises every year, and that should be in the decision.
Common questions
Our site is on an old version — how urgent is that?
If the version is unsupported, urgent. Unpatched CMS installs are found by automated scanning, not by someone targeting you specifically. We can tell you what you’re exposed to within a day of seeing the site.
Can you take over from a developer who’s gone?
Yes. It starts with an audit, because we need to know what’s custom and what’s stock before changing anything.
Should we migrate or rebuild?
Migrate when the content and structure are sound and only the platform is the problem. Rebuild when the structure stopped matching the business some years ago. The audit answers it; guessing is expensive either way.
Will we lose our Google rankings if we move platform?
Not if the URL map is built first. Rewriting content doesn’t lose rankings; changing or deleting URLs does. More under search engine optimization.
Tell us what you’re running
Platform, version, and what’s currently going wrong. We’ll tell you whether to maintain it, secure it, or move it.