Drupal is the open source content management system built for complexity. It powers a relatively small share of all websites — around one to two per cent by most measures — but a disproportionate number of large, demanding ones: universities, government departments, healthcare bodies, cultural institutions and international organisations. For a larger organisation in Oxford, Abingdon or elsewhere in Oxfordshire, Drupal can be the right foundation. This article explains when, and when it is overkill.
What makes Drupal different
A true content modelling framework
Where many systems treat everything as a page or a post, Drupal lets you define precise content types with exactly the fields you need, and relationships between them. If your organisation manages, say, courses linked to departments linked to staff profiles linked to research outputs, Drupal models that structure natively and keeps it consistent across thousands of items. This is its defining strength.
Granular permissions and editorial workflow
Drupal has a sophisticated roles and permissions system and built-in editorial workflow: draft, review, approve, publish, with different rights at each stage and a full revision history. For an organisation where content must be signed off before it goes live, and where you need to know who changed what and when, this is core functionality rather than an add-on.
Multilingual at the core
Every part of a Drupal site — content, menus, configuration, interface strings — can be translated and managed per language. For bodies serving multiple language communities this is more robust than bolt-on approaches.
Security suited to scrutiny
Drupal has a dedicated security team and a formal, well-documented disclosure and patching process, and it is a common choice where security is formally audited. Its permission model and configuration management support the kind of controlled, reviewable change that larger organisations and public bodies require.
Integration and scale
Drupal is API-friendly and comfortable acting as a central content hub feeding websites, mobile apps and other systems. It handles large content volumes and high traffic with appropriate hosting and caching.
The trade-offs
- Higher build cost. The flexibility takes skilled configuration and development, so projects cost more than an equivalent WordPress build, often significantly.
- Smaller specialist pool. Fewer developers work in Drupal, and rates are higher. Choosing a provider who will still be available in three years matters more than with WordPress.
- More than a small business needs. For a typical local business site, Drupal is over-engineered; WordPress will be faster and cheaper to build and run, and easier for staff to use.
- Ongoing maintenance is essential and non-trivial. Major version upgrades need planning and budget, though recent versions have made the upgrade path considerably smoother.
Is Drupal right for you?
Consider Drupal if several of these apply:
- You have complex, interrelated content types and a lot of structured data
- Multiple teams create content and formal approval is required before publishing
- You need full multilingual support across the whole site, not just the content
- Security and accessibility will be formally audited against a standard
- The site must integrate with other systems or serve content to apps
- You expect high or spiky traffic
- You have the budget for a properly built and maintained platform
If only one or two apply, WordPress or Joomla is almost certainly the better value, and we will say so.
Accessibility and the public sector
Drupal has a strong reputation for accessibility, with community commitments to WCAG conformance in both the admin and front-end. For Oxfordshire organisations with public-sector obligations, or any body that takes the Equality Act seriously, this is a meaningful point in its favour, though accessibility ultimately depends on how any site is built and maintained rather than the platform alone.
How B Bizzi approaches it
We assess the requirement honestly against your budget and the support available, and recommend the platform that fits — WordPress, Joomla or Drupal. Where Drupal is genuinely the right answer, we scope it carefully, build to its configuration-management practices so changes are reviewable, and set up managed hosting with the backups, monitoring and update planning a platform of that importance needs. Where it is not, we will point you to the simpler option.
Local to Oxfordshire
B Bizzi is based in Witney and works with organisations in Oxford, Abingdon, Woodstock, Burford, Bicester, Banbury, Kidlington and Didcot.
Talk to B Bizzi
To discuss whether Drupal suits your Oxfordshire organisation, call B Bizzi on +44 7973 693972, email hello@bbizzi.co.uk, or use the contact form at https://beebizzi.co.uk. We are based in Witney, Oxfordshire.