Remix – Frontend and web application
Remix handles the new website interface and application-level data loading. Presentation and interaction are no longer tied to Contao templates.
CMS Migration · Platform Engineering
A website with independently managed content and search.
We migrated Schubert System Elektronik's website from Contao to a setup using Remix, Sanity and Algolia. The new architecture separates the frontend, content management and search into distinct responsibilities.
The project illustrates how we modernize an existing website without making the content management system responsible for every part of the application.
We migrated Schubert System Elektronik's Contao website to Remix, Sanity and Algolia, separating the frontend, content management and site search.
- Client
- Schubert System Elektronik
- Type
- Migration
- Status
- Ongoing
- Services
- Platform Engineering
- Software Engineering
- CMS Migration
- System Integration
The migration went beyond replacing a CMS.
Starting point and scope
Schubert System Elektronik's existing website was built on Contao. The migration replaced the CMS-centered structure with an architecture where presentation, editorial content and search can be developed separately.
We delivered the technical migration to Remix, Sanity and Algolia. The central engineering task was to define how the components work together: which content belongs in the CMS, how the frontend consumes it and which functions the search service owns.
The Schubert Group case documents a related modernization approach. Schubert System Elektronik is a separate reference with its own scope.
Separate the concerns. Integrate the system.
Technical approach
With Remix we developed a frontend independent of the CMS. Sanity handles structured editorial content as a headless CMS, while Algolia provides a dedicated search component.
Moving from Contao to Sanity requires a deliberate content model: existing page structures and editorial needs must be represented in the new system. The frontend consumes structured content instead of relying on the original CMS templates.
Search follows the same principle. Algolia serves a separate purpose, but the content model, indexing process and application still require clearly defined interfaces and ownership.
The stack and the role of each component.
Three technologies with distinct responsibilities replaced the CMS-centered setup.
Sanity – Headless CMS
Sanity manages structured editorial content and exposes it through APIs. Content modeling and frontend development can progress independently.
Algolia – Site search
Algolia provides an independent search index and query service. Indexing, content updates and search need defined integration paths.
Search belongs in the architecture, not inside the CMS.
Content and indexing
A headless CMS is not automatically the right search engine. For Schubert System Elektronik, Algolia is part of the architecture as a separate service.
This makes it possible to evolve content management and search independently. It also requires deliberate handling of index updates, data structure, failures and operational ownership. We do not claim performance or conversion improvements without measurements.
What the migration changed technically.
The documented outcome is the separation of responsibilities, not an unverified performance claim.
Independent frontend and CMS development
The web application can evolve without rebuilding editorial workflows inside the application layer.
Structured content served through APIs
Sanity provides the content foundation and a defined interface to the frontend.
Dedicated site search
Algolia takes responsibility for search without tying its capabilities to the previous CMS.
Composable architecture shifts responsibility to integration.
Architecture decision
Remix, Sanity and Algolia are not useful because they are separate tools. They are useful when the separation matches real requirements. Content models, APIs, indexing and operations still need to function together.
For similar projects we combine Platform Engineering with Contao migration. We decide which functions should be separated and which existing systems should remain in place.
Platform Engineering · CMS Migration
Need to connect your website, content and search?
We assess your current CMS, system boundaries and whether a headless architecture with dedicated search is the right next step.
Aleksandar Basara
Managing Director
aleks@valanor.co
+49 (0) 711 16 44 6 83
Lindenspürstrasse 22, 70176 Stuttgart
