Grow · service 07 of 09

Corporate websites

Multi-site and multilingual corporate and B2B websites that marketing teams can run themselves, with editorial workflows that keep content consistent across brands and regions. Built on Drupal, so content, translations and permissions live in one place and your team can publish without a developer.

corporate-websites.yml
engagement: Project, then ongoing support
platform: Drupal 10/11
suits: Multi-brand, multi-region, B2B
design: From your designers or agency
Is this for you?

Sounds familiar?

  • Separate sites for each brand or country have drifted apart
  • Every page change needs a developer
  • Translations are managed in spreadsheets and email
  • Regulated content goes live without a proper approval step
  • Sections of the site look and behave inconsistently
What's included

The work, in detail.

01

Multi-site and multilingual setups

One codebase for several sites or regions, with content and interface translation built in.

02

Editorial roles and approval workflows

Draft, review and publish steps with the right people at each stage, and a record of who approved what.

03

Reusable page-building components

A library of components editors combine into pages, so new pages don't need new code.

04

Design system integration

Components built from your design system, working with your designers or agency.

05

Search, forms and lead capture

Site search, forms and enquiry journeys connected to your CRM.

06

Editor training and documentation

Hands-on training and a guide written for your editors, not for developers.

How it works

From first call to finished work.

Every engagement starts with a free 30-minute discovery call and a written proposal. Nothing starts until the scope, price and terms are agreed in writing.

  1. Discovery and content model

    Brands, regions, editors and workflows mapped into a content model and permissions plan.

  2. Build the components

    Components and templates built and shown on staging as they're ready.

  3. Content and training

    Content migrated or entered, and editors trained on the real site.

  4. Launch and support

    A planned launch, then ongoing support and improvements if you want them.

Questions

Frequently asked.

Do you do the design?

No. I work with your designers or agency, or bring in trusted freelancers when a project needs them, so you only pay for design when you need it.

Why Drupal rather than WordPress?

WordPress is a good fit for many sites. Drupal tends to suit sites with complex content, many editors with different permissions, several languages and formal approval workflows.

Can our team manage it after launch?

That's the aim. Editors are trained on the real site and get a written guide, and developer documentation is kept in your repository.

Will you have access to personal data?

If the work means handling personal data, such as user accounts, form submissions or a copy of a live database, we sign a UK GDPR data processing agreement alongside the contract before I get access. Where I can, I work on copies with personal data removed.