Case Study · TYPO3 Development · Multi-Frontend

// case_005 · multi-frontend configurator Eine Codebasis. Zwei Frontends. Ein Konfigurator für Web und Verkaufsraum.

TYPO3 as a headless backend for the public website and in-store consulting. 5 custom Extbase extensions, 11 domain models, and a 7-step wizard with consistent data management across both touchpoints.

2
Front ends based on a single codebase
5
Custom Extbase Extensions
11
Total domain models
7
Steps Wizard

Background

Online-Konfigurator oder In-Store-Berater?

B2B manufacturer wants a configurator. A public website for DIY shoppers, plus a tablet app for in-store consultations. Data management must be consistent.

What off-the-shelf solutions offer

Two separate apps, two backends, two data sets. Synchronization is time-consuming, and maintenance is duplicated.

Our Approach

A TYPO3 codebase serving as a headless backend, two Fluid frontends with shared domain models. Single source of truth.

Three Ways

Headless-CMS, Custom-PWA oder TYPO3 mit Multi-Frontend.

Option A

Headless CMS (Strapi/Contentful)

API-first backend, two separate front ends.

Risk external SaaS
Time 16+ Where
Costs high
Episode Vendor lock-in
Option B

Custom PWA

Custom JavaScript framework, Vue/React.

Risk lots of customization
Time 20+ weeks
Costs very high
Episode Difficult to maintain
Option C

TYPO3 + Multi-Frontend

Existing TYPO3 infrastructure, 2 templates, shared models.

Risk low
Time 12 Where
Costs medium
Episode full control

12 weeks

Vom Briefing zum Multi-Frontend.

Phase 01
Domain Modeling

11 domain models defined. Products, variants, compatibilities, pricing tiers.

Where 1–3
Phase 02
Extension Build

5 Custom Extbase Extensions. Repository pattern, clear boundaries.

Where 4–7
Phase 03
Public Front End

7-step wizard for DIY shoppers. Mobile-first.

Where 8–10
Phase 04
Consultant Tablet

Second Fluid template family for in-store consulting.

Where 11–12

Tools

TYPO3-Stack, kein Custom-Framework.

CMS

TYPO3 v13 + Extbase

  • Headless-fähig
  • 5 Custom-Extensions
Data model

Mask + Custom Tables

  • 11 Domain-Models
  • MM-Relations
Front-ends

Fluid + Tailwind

  • Public Web responsive
  • Tablet-Touch-Optimiert

Voice

From the mandate.

What won us over wasn't the finished front end, but the fact that we can maintain the code in our own back end. No vendor lock-in.

B2B-Hersteller Covered by an NDA
NDA

Three Lessons from Multi-Frontend.

01

Domain modeling before coding saves weeks.

02

One codebase with two front ends > two codebases.

03

The Repository Pattern makes multi-frontend systems maintainable.

Frequently Asked Questions

Need a multi-frontend solution? Let's outline the architecture.

The first call is free.

Request architectural services Similar cases

// further reading

Related articles from our blog

Using TYPO3 Effectively for Small and Medium-Sized Businesses

TYPO3 is considered complex—and rightly so, if you set it up like a blog system. But TYPO3 can also run efficiently for SMEs: configured leanly, with a clear editorial structure and the right extensions. We’ll show you which configurations are typical for SMEs and where typical over-complexity can be avoided.

Read more

What is TYPO3, and how does it work as a CMS?

TYPO3 is the enterprise CMS behind many German corporate websites—powerful, secure, and scalable. For SMEs, however, it’s not the array of features that matters, but the question: Does it meet our needs? We explain when TYPO3 is the right choice and which CMS alternatives work better in which scenarios.

Read more

Successfully Implementing TYPO3 Projects

TYPO3 projects rarely fail because of the CMS itself—but rather due to unclear requirements, underestimated migration efforts, and a lack of editorial coordination. Drawing on our project experience, we’ll show you the most common pitfalls and which decisions made in the first week are critical to the project’s success.

Read more