Entity
Types, fields, display — not the theme.
Drupal Development
We design, develop, test, and support Drupal platforms — including Drupal + AI integrations when machines should take the repetitive work and people keep the decisions. Custom themes and modules, migrations, and security that survive handover.
Start a Drupal projectWhat Drupal is
Drupal is an open-source content management system (CMS) and web application framework. It is written in PHP and distributed under the GNU General Public License. Drupal allows individuals and organizations to easily create and manage various types of websites, ranging from personal blogs and corporate websites to e-commerce platforms and community forums.
We design, develop, test, and support Drupal platforms that make your content shine and bring true value to your audience.
-
PHP
-
Symfony
-
Composer
We are a Drupal Certified Partner, contributing to the Drupal community. See GeoNovation on Drupal.org.
Drupal and WordPress
Buyers often ask whether to stay on WordPress or move to Drupal. The honest answer depends on the shape of the work, not on a slogan.
Drupal
Drupal is a CMS and a web application framework. Content types, fields, views, and workflows live in the platform. Roles can be as specific as the organisation. Multilingual sits in core. Configuration can be exported, reviewed, and handed over.
That is why we use it for high-traffic public sites that must be accessible, security-reviewed, and operable after procurement.
WordPress
WordPress is a publishing tool that grew into a CMS. Posts, pages, and plugins get a brochure or a newsroom online quickly. A small editorial team on a marketing site is often better served by WordPress.
The cost shows up later: languages, permissions, and custom data models tend to become a plugin stack that is hard to tender, harden, or migrate.
We build Drupal. If the next site is a WordPress brochure, we will say so. If you are leaving WordPress because the plugin stack no longer matches the organisation, that is Drupal work we already staff.
Drupal as a DXP
Drupal is a digital experience platform because it is modular software, not a single site template. Core is the framework: entities, fields, routes, plugins, services, and configuration. What the organisation actually runs — content types, editorial roles, integrations, the public theme — is assembled as modules and config on top of those APIs.
You do not fork Drupal to add a workflow, a content type, or a migration. You add a module. That module talks to documented APIs. Display stays separate from data. Access is a policy, not a page template. When a major version retires an API, the work is to port the module, not to rebuild the site from a theme.
GeoNovation custom modules, themes, and migrations are written against this surface: the same APIs that keep a platform updateable and hand-overable.
Drupal APIs
Drupal is powerful because it is modular. Core is not a finished site. It is a set of APIs. What the organisation actually runs is assembled as modules on that surface.
Drupal APIs Creating custom modules Backwards compatibility policy
Access
Roles as policy, not a page template.
Routing
Declared URLs. Menus hang off them.
Config
Export the structure. Keep runtime in state.
Render
Render arrays with cache, not HTML strings.
Form
Input, validate, submit — one API.
Data
In, out, and through as testable plugins.
Plugin
New behaviour without forking Drupal.
The Drupal work
Modules and themes
Tailor-made themes and modules that extend Drupal, with a codebase you can own.
- Drupal architecture, not a theme shop
- PSR-12 and a maintainable custom stack
Migrations and upgrades
From Drupal 7 or 9 toward 10 and 11, without leaving content or ranking behind.
- Content, modules, and functionality
- SEO ranking kept through the move
Security and compliance
Updates, patches, and a site that can survive a security review.
- Regular core and module updates
- Hardening that procurement can specify
SEO and UX
Visibility and a usable interface, not only a redesigned skin.
- Search-engine optimisation in the build
- UX grounded in how editors and visitors work
Mobile-first design
Interfaces designed for the small screen first, then scaled up.
- Responsive Drupal themes
- Fast on the devices your audience actually uses
Support and maintenance
After launch: updates, and a site that keeps running.
- Ongoing Drupal updates
- A squad still there after handover
Who Drupal is for
Drupal is the right default when the site is a platform, not a page.
Institutional public sites
Web leads and programme officers who need multilingual, accessible, security-reviewed public sites: EU programmes, UN-related organisations, healthcare, and their implementing partners.
Teams mid-migration
Drupal 7 or 9 platforms that must move to 10 or 11 without losing content, modules, or SEO ranking.
In-house squads that need capacity
Architecture, custom modules and themes, and hardening, with a hybrid squad that works beside your people and leaves the codebase operable.
Not a fit
A one-off brochure with two editors and no procurement constraint. WordPress, or a simpler stack, is usually faster. We would rather send you there than sell you a framework you will not use.