NCREP Heritage Consultancy: turning an agency-led brief into a multi-site Craft CMS platform

When Major brought GOMO into the NCREP project, the first important decision happened before the design work began.

NCREP did not need a simple bilingual website. They needed an international presence, a UK-specific version, and a content structure where services, sectors, portfolio projects and other pages and content could be managed cleanly over time.

During the initial technical discovery, Fred recommended Craft CMS. Webflow would have been the wrong fit for this particular project: two distinct site experiences, one of them bilingual, with market-specific editorial rules, would quickly become harder to maintain as separate visual-builder sites. Craft made the structure straightforward from the start.

Major’s design, GOMO’s technical platform

This was an agency partnership. Major led the client relationship and design direction, and GOMO joined as the technical partner responsible for turning the project requirements into a production-ready CMS platform.

That collaboration model mattered. NCREP could discuss technical constraints directly, Major could focus on the creative and client-facing side of the work, and Fred could take responsibility for the architecture, implementation and launch without adding friction to the process.

The result was a clear division of responsibility: Major shaped the visual direction; Fred handled the technical discovery, Craft CMS architecture, template development, custom plugin and module work, deployment, domain behaviour, technical SEO and launch support.

Choosing Craft before the interface existed

The most important technical requirement was not visual. It was structural.

NCREP needed a bilingual international website and a separate UK presence, with services that could exist in one market and not the other. That meant the CMS had to support more than translated pages. It needed to understand sites, languages, domains, content availability, URL behaviour, sitemap rules and editorial relationships.

Craft CMS was the natural choice for that. It allowed the project to be built as one coherent platform instead of a set of duplicated websites.

Services, sectors, portfolio projects, team profiles, insights and testimonials could all be modelled as structured content. Editors could manage content in Craft without manually rebuilding pages or duplicating layouts across markets.

Custom Craft engineering where it mattered

The build included custom Craft CMS work where buying a plugin would have added unnecessary complexity.

For contact submissions, GOMO built a focused Craft CMS plugin instead of using a heavy form-builder plugin. The form interface had already been designed, including success and error states, so the project only needed the right engine behind it: save submissions in Craft, notify the right people by email, give managers a table of enquiries, and let them reply directly from the Craft dashboard.

After launch, Cloudflare Turnstile was added to reduce spam. That fitted naturally into a technical stack that already used Cloudflare R2 for media storage.

GOMO also built custom module logic for slug management and UK site mirroring. The slug handling keeps URLs aligned with title changes while preserving manual overrides and redirects. The site-mirroring layer allows the English site to behave correctly on the UK domain, including market-specific service visibility and URL behaviour.

Technical ownership through launch

The work was not limited to building templates.

GOMO handled the full technical path from discovery to launch: Craft CMS setup, content modelling, Twig templates, custom plugin development, custom modules, Cloudflare R2 media storage, form handling, Turnstile spam protection, deployment, domain behaviour, sitemap generation, hreflang handling, structured data and post-launch support.

The technical SEO layer was treated as part of the build rather than an afterthought. The site includes structured data, breadcrumbs, multilingual sitemap handling, hreflang alternates and UK-specific sitemap behaviour. That clean setup helped Google pick up the new site quickly after launch.

A partnership built on trust

The project was delivered in around four months, from technical discovery to launch.

For NCREP, the result was a refined, manageable Craft CMS platform that supports both international and UK-facing needs without splitting the system into disconnected websites.

For Major, it was the kind of agency partnership that works best: a senior technical partner who can join client conversations, recommend the right platform early, take ownership of the implementation, and protect the quality of the final delivery.

This is the kind of agency partnership GOMO is built for: helping agencies deliver technically demanding websites with calm execution, clear judgement and direct responsibility from the person doing the work.

It is also a clear example of Craft CMS development being the right choice when a website needs multi-site structure, multilingual content, custom editorial rules and long-term maintainability.