Development Technologies
From custom web applications built with Nuxt, Laravel and Strapi to CMS websites and online stores on WordPress, Drupal, Kentico and Magento, each technology has its own strengths. Explore what each one does best and when we recommend it.
Open-Source CMS
Drupal is a free, open-source content management system built around structured content and flexibility. Thousands of modules extend what it can do, while built-in multilingual, accessibility and security features make it a long-standing choice for governments, universities and large organisations.
Most websites run on more than one technology. Here’s how common project needs map to the right web development stack, and how each piece works with the others.
| Project Need | Recommended Stack | Why It Fits |
|---|---|---|
| Corporate website that needs to rank on search engines | Nuxt + Strapi | Editors manage content in Strapi, while Nuxt renders each page on the server, so visitors and search engines get fast, readable pages. |
| Customer portal or booking system with logins and payments | Nuxt + Laravel | Laravel handles accounts, data and business logic behind the scenes, then connects to Nuxt through an API for a fast, responsive frontend. |
| Website and mobile app sharing the same content | Strapi | Content is entered once in Strapi and delivered through its API to both the website and the app, keeping them in sync. |
| Government or university website with many editors and languages | Drupal | Role-based access, built-in multilingual tools and accessibility features help large teams publish in several languages. |
| Website the marketing team updates often | WordPress | A familiar editor and a large library of themes and plugins let teams update pages and add features with little technical help. |
| Organisation that wants content and marketing tools together | Kentico | Kentico combines content management with digital marketing tools, so content and campaigns run from a single platform. |
| Online store with a large product catalogue | Magento | Magento is an e-commerce platform that manages product catalogues, shopping carts and checkout in one place. |
Drupal’s latest advisories affect specific modules, logins and private files. Learn what your website team should check and report.
30 Oct 2026 · 3 min read
Learn what Drupal does, where its flexibility is useful and what to ask before choosing it for your business website. No technical background needed.
22 Aug 2026 · 3 min read
Assess Drupal against your organisation’s publishing needs: approvals, languages, shared content and ongoing care. Practical questions for a useful demo.
18 Aug 2026 · 3 min read
Drupal is a content management system suited to websites with many pages, several content types or multiple publishing teams. It can organise information such as services, news, events, documents and directories. We recommend it when clear content structures, permissions and publishing processes matter, including government, education and corporate websites.
Yes. We can configure roles so contributors prepare content, reviewers check it and authorised editors publish it. Drupal can keep the current page live while a revised draft goes through review. We agree the responsibilities and approval steps with your team, then test the workflow before handover.
Yes. Drupal includes tools for managing content in multiple languages. We can set up language-specific pages and navigation so visitors can switch between the supported languages. Your team still needs to supply or approve the translations; enabling multilingual features does not automatically produce accurate translated copy.
Yes. We configure editing forms for the content your team needs to maintain, such as news, events, service information and downloadable documents. Editors update the relevant fields instead of changing website code. Templates keep the presentation consistent, while changes to the design or new functionality remain development work.
Yes. Drupal can supply content through APIs to a separate website built with Nuxt, or display the website through its own templates. It can also connect to systems with suitable integration interfaces. We define which data is shared and who can access it. A separate frontend is an option, not a requirement for using Drupal.
Yes. We can plan the transfer of pages, documents, images and other agreed content. We first map the old content to the new structure and test a sample import. Existing URLs should be retained where practical, with relevant redirects for changed addresses. Your team reviews the migrated content before launch; a migration does not guarantee unchanged search rankings.
Plan for Drupal core and module updates, hosting, backups and checks after changes. Updates should be tested before they reach the live website, especially where custom features or integrations are involved. Your team also needs to keep content, documents and user access current. We agree the maintenance responsibilities and scope before handover.
