One website. A shared content foundation for other applications.

The Schubert Group's corporate website was based on Contao. As its digital sales applications evolved, the company needed content that could be managed once and used across multiple applications, rather than exclusively on the website.

The frontend, content editing and specialist capabilities for search, media and tracking also needed to evolve independently. That called for an architecture with clearly defined responsibilities and interfaces.

Valanor was responsible for the technical migration and development of the new website architecture. Replacing Contao was only one part of the project; making structured content reusable across systems was the central requirement.

Rather than being only a website CMS, Sanity provides a shared foundation for content that is needed across different digital applications.

Alongside the corporate website, the Waypoint and Iskra sales applications use or are intended to use this common content foundation. Waypoint supports sales processes at trade shows; Iskra supports digital business cards.

Each application keeps its own interface and business processes. Shared content can be managed centrally and delivered through defined interfaces, reducing the need for duplicate editorial work and inconsistent information.

Here, Single Source of Truth applies to the editorial content managed in Sanity. It does not mean Sanity owns every customer, sales or business record across the Schubert Group.

A decoupled architecture reduces dependency on a single CMS, but requires more discipline in APIs, data models, failure handling and operating multiple services. Those responsibilities must be explicitly assigned. We assess these trade-offs through Consulting & Diagnostics.

For the Schubert Group, the separation matters because content must serve more than one website. A one-to-one Contao migration would not have addressed that cross-application requirement to the same extent.

For industrial and manufacturing companies, connecting a corporate website with product information and sales tools can be particularly relevant. This architecture shows how structured content can be shared without forcing every application to use the same frontend.