The site is huge and neither visitors nor staff can find anything
We design the content model first: content types, sections, search and filters. Then we build so every document has a clear place.
A large Drupal site your editors can manage and you won't have to rebuild
We build Drupal sites for universities, public bodies and large organizations: thousands of pages, many editors, strict security needs.
Quote and schedule after your brief
Who it's for
- Universities, colleges and schools with many departments and pages
- Municipalities, agencies and public institutions
- Large organizations with several languages, teams and editors
- Owners of Drupal 7 sites who need to migrate
Problems we solve
Many editors keep breaking pages
We set up roles, permissions and a draft-and-approval workflow. Each editor sees and changes only their own section.
Drupal 7 is end of life and migration feels risky
We audit the content, migrate it with scripts and map every old URL to a new one. This protects search visibility as far as technically possible.
Security, accessibility and multiple languages are mandatory
We build in security updates, backups, WCAG accessibility (standards for users with disabilities) and multilingual structure under the agreed terms.
What's included
- Requirements and content structure analysis
- Design of key page templates
- Drupal 10 or 11 build with a custom theme
- Content types, taxonomies, search and filters
- Roles, permissions and editorial approval workflow
- Multilingual setup and interface translation
- Content migration from the old site
- Enquiry forms, CRM and email integration
- Security hardening, backups and performance tuning
- Editor training and documentation
Choose the scope
Use a package to describe what you need. We agree on the quote and schedule after reviewing your brief and requirements.
01
Start
Small institutions and departments needing a manageable site
- Up to 30 templated pages
- Design from ready-made components
- 2-3 editor roles
- Enquiry form
- Editor training
02
Portal
Universities, municipalities and organizations with many sections
- Custom design of key templates
- Search and filters across content
- Multilingual setup
- Content migration
- CRM integration
03
Ecosystem
Large bodies with several sites and complex integrations
- Multisite architecture
- API integrations with external systems
- AI agent answering enquiries
- Extended security review
- Pilot with a measurable KPI
How we work
Brief and requirements
You describe the task and current workflow. We clarify requirements, choose a first stage and prepare a quote.
Structure and prototype
We agree content types, navigation and roles, and show a prototype before development starts.
Build and migration
We build in stages, migrate content and share interim versions for review.
Testing and launch
We check security, performance, accessibility and redirects, then launch.
Handover and support
All access, files and accounts go to you. We train editors and can support the site if you want.
Scope and limits
- We don't promise search rankings: positions can shift temporarily after a migration
- We can't migrate content that doesn't exist in usable form; you need to prepare it
- We don't take projects that require certifications or formal tender procedures we can't meet
FAQ
Why Drupal and not WordPress?
Drupal is stronger where there are many content types, roles and security demands. For a small brochure site it is overkill, and we'll tell you so and suggest something simpler.
Can you migrate from Drupal 7?
Yes. There is no in-place upgrade, so we build a new site and migrate the content. We check up front what moves automatically and what needs manual work.
Who owns the site?
We agree on the handover of code, materials and account access before work starts. Third-party licences and services are listed separately when needed.
How is the price set?
We prepare a quote after reviewing your brief and requirements. A first stage can cover: up to 30 templated pages; Design from ready-made components. Scope, payment and schedule are agreed before work starts.
Can we pay in stages?
Yes. Payment is split into stages: kickoff, prototype, build, launch. You pay as each stage is completed.
Who maintains the site after launch?
We can, you can, or another team. The code is standard and documented, so there is no lock-in to us.
Start with your task
Describe your business, the outcome you need and your current workflow. We will clarify the requirements and prepare a quote after your brief.