---
title: "Page Builder for TYPO3: Build Pages Visually | Laioutr"
canonical_url: "https://www.laioutr.com/en/page-builder-typo3"
locale: en
meta:
  description: "Page builder for TYPO3: Laioutr adds a visual editor and fast frontend to TYPO3 content. No Fluid templating, accessible and GDPR-compliant."
  "og:description": "Page builder for TYPO3: Laioutr adds a visual editor and fast frontend to TYPO3 content. No Fluid templating, accessible and GDPR-compliant."
  "og:title": "Page Builder for TYPO3: Build Pages Visually | Laioutr"
---

TYPO3 x Laioutr

# Page builder for TYPO3: visual editor and fast frontend

Visual page building without Fluid templating for every page

More speed and creative freedom for TYPO3 websites: TYPO3 stays the CMS, Laioutr delivers the page builder and frontend.

[Request a demo](https://www.laioutr.com/en/contact)

![Laioutr: visual editor and frontend for TYPO3](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmr24iubs8qii07mnhoipk9m4)

Partners support the implementation of TYPO3 frontends with Laioutr.

[![Best it](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:360/auto_image/cmix5spa5b1w807mil223s722)](https://www.bestit.de/ "Best it") [![Datrycs](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:360/auto_image/cmmadi4tvbwvo07jruwbnp77v)](https://www.datrycs.com/ "datrycs") [![Valantic](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:360/auto_image/cmn66fjx185su07mgyojaxmlc)](https://www.valantic.com/ "valantic")

5/5

OMR Reviews

70+

Frontend components

Lighthouse 100

Performance from day one

Made in EU

GDPR-compliant by default, EU hosting available

PAGE BUILDER FOR TYPO3

## What a page builder for TYPO3 does

TYPO3 is a powerful enterprise CMS: content, editorial workflows, permissions, multi-site and multilingual capabilities are its strengths. What is often missing is a modern, visual frontend that marketing and editorial teams can operate without Fluid templating. This is where Laioutr comes in: as a visual page builder and frontend layer that reads TYPO3 content via the content API (TYPO3 Headless) and delivers it as a fast website. TYPO3 remains the leading system, Laioutr delivers the frontend. Laioutr is also an integrated headless CMS in its own right: content collections, Studio and frontend in one platform, for example for campaign content that should not live in TYPO3.

[Book a strategy call](https://www.laioutr.com/en/contact)

### 1. The backend stays TYPO3

TYPO3 continues to manage content, the page tree, permissions, editorial workflows, multi-site and translations. The TYPO3 backend and established processes stay unchanged, with all extensions and workflows.

### 2. Choose the frontend option

There are several options for the frontend: classic Fluid/TypoScript, a headless setup (EXT:headless) with a separate frontend, a custom build or a page builder like Laioutr. Each option has its pros and cons.

### 3. Content flows through the content API in real time

No data duplication, no sync conflicts. Laioutr reads TYPO3 content via the headless/content API (JSON) and renders it, including multilingual content and multi-site.

FRONTEND OPTIONS

## Which frontend options are there for TYPO3?

With Fluid, TypoScript and the headless extension, TYPO3 provides the building blocks, but no ready-made frontend product that non-developers can operate visually. That raises the frontend question in every TYPO3 project. Four options are well established.

[Book a strategy call](https://www.laioutr.com/en/contact)

### 1. Fluid & TypoScript (classic)

The classic TYPO3 route: templates in Fluid, configuration via TypoScript. Full integration, but every layout change goes through development. A good fit for stable pages with rare changes or teams with deep TYPO3 expertise.

### 2. TYPO3 Headless (EXT:headless) with a separate frontend

The headless extension exposes TYPO3 content as a JSON API. The decoupled frontend is built in-house: maximum freedom, but the design system, components and maintenance stay with the internal team. A good fit with a suitable frontend team.

### 3. Custom build (Next.js or Nuxt)

Maximum control, highest effort: a six- to twelve-month build phase and ongoing maintenance by an in-house frontend team that connects the TYPO3 content API itself. A good fit when frontend engineering is a strategic core competency.

### 4. Laioutr Page Builder

Visual page builder and frontend platform with 70+ components and a TYPO3 connection, with EU cloud hosting available as an add-on. Fast time-to-launch, gentle learning curve, marketing and editorial teams build pages themselves. A good fit for a fast go-live without investing in a custom build.

USE CASES

## Use cases: Laioutr on TYPO3

Laioutr is designed for TYPO3 setups that need to change and scale fast: from corporate websites to multi-site portfolios and campaign landing pages with high editorial volume.

[Book a strategy call](https://www.laioutr.com/en/contact)

### Multi-site and multi-domain on one TYPO3

TYPO3 is strong at multi-site: several websites, brands and domains from one instance. Laioutr turns them into standalone frontends: one component pool, many brand presences, each with its own design.

### Campaign and landing pages without a ticket

Marketing builds landing pages visually from ready-made building blocks, without a Fluid template and without a developer ticket. Content comes from TYPO3, the layout is created in the page builder.

### Multilingual websites

TYPO3 manages translations and language trees, Laioutr delivers them consistently. Languages, layouts and content can be controlled per site and are compatible with the TYPO3 language concept.

### Public sector and accessibility

Public authorities and institutions rely on TYPO3. Laioutr delivers the accessible frontend to match: WCAG- and BFSG-compliant, GDPR-compliant by default, EU hosting available.

### Relaunch without touching the backend configuration

Renewing an existing TYPO3 frontend without touching the page tree, permissions or editorial processes. Phased migration with a clear rollback plan.

### New TYPO3 projects live fast

New TYPO3 project, fresh start. With Blueprints, Themes and the UI library, the project goes live in weeks instead of months of custom development.

LAIOUTR OR CUSTOM BUILD

## Page builder for TYPO3 or custom build: the comparison

Both routes lead to a decoupled frontend on TYPO3. A custom build (Next.js or Nuxt on the TYPO3 API) offers maximum control but requires a six- to twelve-month build phase and ongoing maintenance. Laioutr delivers Studio and 70+ components, with full code extensibility for special cases; Cloud/Edge Hosting is available as an add-on. The difference lies in time-to-launch, maintenance load and who can build pages.

Pricing Plans Comparison

| Compare differences | Laioutr Page Builder | Eigenentwicklung (Next.js / Nuxt) |
| --- | --- | --- |
| Laioutr Page Builder Eigenentwicklung (Next.js / Nuxt) |
| Builder und Komponenten Was ab Werk enthalten ist und was selbst aufgebaut werden muss. |
| Visueller Page Builder Drag-and-drop-Editor für Marketing- und Redaktions-Teams. | Enthalten (Studio) Live-Vorschau, komponentenbasiert | Nicht enthalten Eigenbau oder externes Tool |
| Frontend-Komponenten Vorgefertigte UI-Bausteine für Seiten, Landing- und Content-Pages. | 70+ Komponenten Design-Token-basiert, anpassbar | Selbst aufbauen Komplette UI-Bibliothek selbst entwickeln |
| Blueprints und Themes Startpunkt für neue Websites ohne Greenfield-Aufwand. | Blueprints und Themes Start-Sites je Branche plus Design-Themes, voll erweiterbar | Greenfield Designsystem komplett selbst aufbauen |
| Hosting Wo das Frontend ausgeliefert wird und wer es betreibt. | Add-on: Cloud/Edge Hosting EU-Hosting verfügbar, kein separater Deploy | Selbst hosten Vercel, AWS, eigene Infrastruktur |
| Architektur und Compliance Wie flexibel die Plattform ist und was regulatorisch abgedeckt ist. |
| Backend-Flexibilität Welche CMS- und Commerce-Backends sich anbinden lassen. | Multi-Backend TYPO3, weitere CMS und Commerce-Systeme | Backend-spezifisch Code an die TYPO3-Content-API gebunden, Wechsel teuer |
| Performance und Core Web Vitals Wie viel Aufwand für Lighthouse-100-Niveau nötig ist. | Ab Werk Lighthouse 100 als Zielwert | Manuelles Tuning Performance-Engineering durch das Team |
| BFSG und WCAG 3.0 Konformität mit Barrierefreiheitsstärkungsgesetz und WCAG 3.0. | Im Standard WCAG 3.0, BFSG, EN 301 549 | Eigenverantwortung Audit separat erforderlich |
| Datenschutz und Hosting-Region Wo Daten verarbeitet werden und welche EU-Verträge gelten. | DSGVO-konform ab Werk EU-Hosting verfügbar, EU-Standardvertrag, deutschsprachiger Support | Hosting-abhängig Abhängig vom gewählten Hosting |
| Team und Wirtschaftlichkeit Wer mit der Plattform produktiv ist und was sie über die Zeit kostet. |
| Lernkurve Wie schnell ein neues Teammitglied produktiv wird. | Niedrig Redaktion ist in Tagen eingearbeitet | Hoch Fluid/TypoScript bzw. React/Vue plus TYPO3-Content-API |
| Time-to-Launch Realistische Zeitspanne bis zum Live-Gang einer neuen Website. | Pilot in 14 Tagen Pilot meist innerhalb von 14 Tagen live, Migration im Median unter 14 Tagen, Founder-begleitet ohne Aufpreis | Monate Sechs- bis zwölfmonatige Build-Phase |
| Ideales Team-Setup Wer mit der Plattform arbeiten kann und wer arbeiten muss. | Cross-funktional Marketing, Redaktion, Design und Entwicklung gemeinsam | Engineering-only Drei oder mehr Frontend-Engineers |
| Preismodell Wie sich Kosten zusammensetzen: Software, Betrieb und Entwicklung. | [SaaS (planbar) Transparente Pläne, Hosting als Add-on](https://www.laioutr.com/de/pricing) [Preise ansehen](https://www.laioutr.com/de/pricing) | Engineering-Kosten Build plus dauerhafte Wartung |

*Comparison based on a typical mid-market setup, publicly available information and our own platform tests. As of July 2026. The exact scope depends on the specific TYPO3 project and its requirements; TYPO3 features may have evolved since.*

CUSTOM BUILD

### When a custom build is the right choice

A dedicated frontend team with TYPO3 and content API experience is in place, at least three engineers. Exactly one TYPO3 frontend with highly specialized requirements is being built. Frontend engineering is a strategic core competency. The classic case: a brand with its own engineering team and a demand for pixel-level control.

LAIOUTR

### When Laioutr is the right choice

Go-live in weeks instead of months, editorial and marketing teams build pages on their own, several sites or brands run on TYPO3, TYPO3 should stay and only the frontend is modernized, and BFSG and WCAG must be covered without a separate audit. The classic case: an organization that wants to modernize and scale its TYPO3 frontend without a large engineering investment.

![Get started faster with a Blueprint](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:800/auto_image/cmj6yw1p4p99j07l4gu1za1ly)

BLUEPRINTS

## Start with a Blueprint instead of from scratch

Blueprints are pre-composed starter sites for each industry, instantly customizable and matched to the TYPO3 setup: a starting point for a faster go-live.

[View Blueprints](https://www.laioutr.com/en/blueprints)

UI PREVIEW

## What can be built with Laioutr on TYPO3

Home pages, landing pages, campaign pages, content pages, blogs, career and product pages and more.

[Explore the UI preview](https://preview.laioutr.com/)

![Laioutr Studio: visual editor for TYPO3 content](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:2048/auto_image/cml81bh8z7qjk07lczs1xft6f)

Support for implementation: certified composable partners deliver frontend projects with Laioutr, from greenfield setups to relaunches of existing TYPO3 websites.

[![Best it](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:360/auto_image/cmix5spa5b1w807mil223s722)](https://www.bestit.de/ "Best it") [![Datrycs](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:360/auto_image/cmmadi4tvbwvo07jruwbnp77v)](https://www.datrycs.com/ "datrycs") [![Valantic](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:360/auto_image/cmn66fjx185su07mgyojaxmlc)](https://www.valantic.com/ "valantic")

FAQ

## Frequently asked questions about the page builder for TYPO3

Does Laioutr work with TYPO3 (multi-site and multilingual)?

Yes. Laioutr reads TYPO3 content via the headless/content API and supports multi-site, multiple domains and multilingual setups, provided the corresponding API endpoints are available.

How does Laioutr differ from a custom build with Next.js or Nuxt?

A custom build typically takes six to twelve months of engineering plus ongoing maintenance by an in-house frontend team. Laioutr delivers Studio and 70+ components ready to use, with Cloud/Edge Hosting available as an add-on. Time-to-launch drops from months to weeks, and the total cost of ownership is typically well below.

How does Laioutr differ from Fluid and TypoScript?

Fluid and TypoScript are the classic developer route: every layout change goes through development. Laioutr delivers a visual builder, ready-made components, Themes and Blueprints, so marketing and editorial teams can build pages themselves, without a ticket for every change.

How does Laioutr connect to TYPO3?

Laioutr connects via the TYPO3 headless/content API (JSON). Standard content (pages, content elements, navigation, translations) is supported, plus project-specific endpoints for custom logic.

Does Laioutr work with TYPO3 multi-site?

Yes. TYPO3 sites are treated as standalone frontends in Laioutr. Layouts, content, languages and domains can be configured separately per site, in line with the TYPO3 multi-site concept.

Can editorial workflows and permissions from TYPO3 still be used?

Yes. Editorial workflows, permissions and approvals remain in TYPO3. Laioutr renders the approved content, and governance stays entirely in TYPO3.

TYPO3 already has an API with EXT:headless, so why Laioutr?

Precisely because TYPO3 exposes content as an API, the frontend question remains open: TYPO3 delivers the data, but not the finished, visually operable frontend. Laioutr builds on this content API and makes the frontend operable for marketing, editorial and development teams together, without separate frontend development.

How long does implementation with Laioutr take?

A pilot is usually live within 14 days, and migration takes less than 14 days at the median. Founder-led migration is standard, not an extra charge. With multi-site or complex requirements, the timeframe depends on the scope.

What does Laioutr cost compared to a custom build?

Laioutr works with transparent SaaS plans based on traffic and features. The total cost of ownership is typically below that of a custom build, because Studio, components and editor are part of the platform and no separate frontend team is needed. Cloud/Edge Hosting is available as an add-on and is not included in the license.

Can the backend be switched later without rebuilding the frontend?

Yes. Laioutr is backend-agnostic. If another system is added alongside TYPO3 later, such as a commerce backend, it is connected via an API instead of rebuilding the frontend.

Is the solution BFSG- and GDPR-compliant?

Yes. Laioutr is GDPR-compliant by default, EU hosting is available, further regions on request (US, APAC), and regional data residency is possible. In addition, there is an EU standard contract and German-language support. WCAG and the BFSG (German Accessibility Strengthening Act, binding since 2025) are covered by default: compliance is built in, not bolted on.

What happens to existing TYPO3 extensions?

Backend extensions (editorial, permissions, import, workflows) remain unchanged. Frontend-oriented features are typically replaced by Laioutr components or pre-integrated apps. The extension stack is reviewed in the migration audit.

Is Laioutr itself also a CMS?

Yes. Laioutr is also an integrated headless CMS: content collections, Studio and frontend in one platform. With TYPO3 in place, Laioutr acts as the visual page builder and frontend, while TYPO3 remains the leading CMS. Content that should not be maintained in TYPO3, for example for campaigns, can be managed directly in Laioutr.

## Latest insights from the Laioutr blog

[View all insights](https://www.laioutr.com/en/blogs/insights)

[![Hero typo3 v12 end of free support shops 2026 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmv855u28dm0y06mioz1kcik1)<h3>TYPO3 v12 Without Free Updates: What It Means for Shops Now</h3>Since April 30, 2026, TYPO3 v12 LTS no longer receives free security and maintenance updates. Teams …](https://www.laioutr.com/en/blog/typo3-v12-end-of-free-support-shops-2026)

[![Hero typo3 sap one storefront data layer en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmv855nbxdlit06mlxlxeo6nv)<h3>TYPO3 and SAP Behind One Storefront: The Data Layer Explained</h3>When TYPO3 supplies content and shop structure while SAP manages prices, stock and orders, the store…](https://www.laioutr.com/en/blog/typo3-sap-one-storefront-data-layer)

[![Hero typo3 multi domain country sites one frontend project en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmv855gwxdpvb06mqehmt8jak)<h3>Many Country Domains on TYPO3: From n Frontends to One Project</h3>Merchants with many country domains and language variants on TYPO3 often maintain more frontends tha…](https://www.laioutr.com/en/blog/typo3-multi-domain-country-sites-one-frontend-project)

[![Hero typo3 elts or upgrade three paths 2026 2027 en](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmv8559z9dpli06mq1hn2yojb)<h3>TYPO3 ELTS or Rebuild: Three Paths for TYPO3 Shops in 2026/27</h3>Since free support for TYPO3 v12 ended on April 30, 2026, shops on v12 have three realistic paths: b…](https://www.laioutr.com/en/blog/typo3-elts-or-upgrade-three-paths-2026-2027)

[![Hero typo3 modern frontend](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmr4mm7qrr81m07mmrrkrfzzg)<h3>Frontend options for TYPO3: from CMS to live storefront</h3>TYPO3 is a enterprise, PHP-based CMS you can run headless: it delivers content through its headless …](https://www.laioutr.com/en/blog/typo3-modern-frontend)

[![Typo3 vs laioutr](https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/resize=width:1920,fit:max/auto_image/cmor98pbd0z5c07lca92kbvot)<h3>TYPO3 Alternative Laioutr: A Modern DXP Instead of Extension Migrations</h3>Laioutr is the faster-to-launch, predictably priced, and AI-native alternative to TYPO3, built for m…](https://www.laioutr.com/en/blog/typo3-alternative-laioutr)

READ MORE

## More on page builders and headless CMS

### Visual page builder

How Laioutr works as a visual page builder with any CMS and commerce backend.

[More on the visual page builder](https://www.laioutr.com/en/composable-visual-page-builder)

### Headless CMS

Laioutr as an integrated headless CMS: content collections, Studio and frontend in one platform.

[More on the headless CMS](https://www.laioutr.com/en/headless-cms)

### Laioutr and existing CMS

How Laioutr works together with an existing content management system.

[More on CMS systems](https://www.laioutr.com/en/system/content-management-system-cms)

### Page builder for Contao

Visual editor and frontend for Contao, built on Laioutr.

[More on the page builder for Contao](https://www.laioutr.com/en/page-builder-contao)

### Page builder for Sulu

Visual editor and frontend for Sulu, built on Laioutr.

[More on the page builder for Sulu](https://www.laioutr.com/en/page-builder-sulu-io)

QUESTIONS LEFT?

## Rethinking the TYPO3 frontend with the Laioutr page builder

30 minutes with the Laioutr team: see Laioutr live on the existing TYPO3 setup and get answers on integration, performance and pricing.

[Request a demo](https://www.laioutr.com/en/contact)

## Structured Data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://www.laioutr.com/#identity",
      "name": "Laioutr",
      "legalName": "Laioutr GmbH",
      "url": "https://www.laioutr.com/",
      "logo": {
        "@type": "ImageObject",
        "url": "https://www.laioutr.com/laioutr-logo.png",
        "width": 400,
        "height": 400
      },
      "email": "info@laioutr.com",
      "telephone": "+49 30 75435715",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "Münchweilersteig 5",
        "postalCode": "12559",
        "addressLocality": "Berlin",
        "addressCountry": "DE"
      },
      "vatID": "DE450905846",
      "sameAs": [
        "https://www.linkedin.com/company/laioutr",
        "https://www.youtube.com/@Laioutr",
        "https://x.com/laioutr"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://www.laioutr.com/en/#website",
      "url": "https://www.laioutr.com/en/",
      "name": "Laioutr",
      "inLanguage": "en",
      "publisher": {
        "@id": "https://www.laioutr.com/#identity"
      }
    },
    {
      "@type": [
        "WebPage",
        "FAQPage"
      ],
      "@id": "https://www.laioutr.com/en/page-builder-typo3#webpage",
      "url": "https://www.laioutr.com/en/page-builder-typo3",
      "name": "Page Builder for TYPO3: Build Pages Visually | Laioutr",
      "description": "Page builder for TYPO3: Laioutr adds a visual editor and fast frontend to TYPO3 content. No Fluid templating, accessible and GDPR-compliant.",
      "inLanguage": "en",
      "isPartOf": {
        "@id": "https://www.laioutr.com/en/#website"
      },
      "breadcrumb": {
        "@id": "https://www.laioutr.com/en/page-builder-typo3#breadcrumb"
      },
      "primaryImageOfPage": {
        "@type": "ImageObject",
        "url": "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmr24iubs8qii07mnhoipk9m4"
      },
      "mainEntity": [
        {
          "@type": "Question",
          "name": "Does Laioutr work with TYPO3 (multi-site and multilingual)?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. Laioutr reads TYPO3 content via the headless/content API and supports multi-site, multiple domains and multilingual setups, provided the corresponding API endpoints are available."
          }
        },
        {
          "@type": "Question",
          "name": "How does Laioutr differ from a custom build with Next.js or Nuxt?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "A custom build typically takes six to twelve months of engineering plus ongoing maintenance by an in-house frontend team. Laioutr delivers Studio and 70+ components ready to use, with Cloud/Edge Hosting available as an add-on. Time-to-launch drops from months to weeks, and the total cost of ownership is typically well below."
          }
        },
        {
          "@type": "Question",
          "name": "How does Laioutr differ from Fluid and TypoScript?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Fluid and TypoScript are the classic developer route: every layout change goes through development. Laioutr delivers a visual builder, ready-made components, Themes and Blueprints, so marketing and editorial teams can build pages themselves, without a ticket for every change."
          }
        },
        {
          "@type": "Question",
          "name": "How does Laioutr connect to TYPO3?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Laioutr connects via the TYPO3 headless/content API (JSON). Standard content (pages, content elements, navigation, translations) is supported, plus project-specific endpoints for custom logic."
          }
        },
        {
          "@type": "Question",
          "name": "Does Laioutr work with TYPO3 multi-site?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. TYPO3 sites are treated as standalone frontends in Laioutr. Layouts, content, languages and domains can be configured separately per site, in line with the TYPO3 multi-site concept."
          }
        },
        {
          "@type": "Question",
          "name": "Can editorial workflows and permissions from TYPO3 still be used?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. Editorial workflows, permissions and approvals remain in TYPO3. Laioutr renders the approved content, and governance stays entirely in TYPO3."
          }
        },
        {
          "@type": "Question",
          "name": "TYPO3 already has an API with EXT:headless, so why Laioutr?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Precisely because TYPO3 exposes content as an API, the frontend question remains open: TYPO3 delivers the data, but not the finished, visually operable frontend. Laioutr builds on this content API and makes the frontend operable for marketing, editorial and development teams together, without separate frontend development."
          }
        },
        {
          "@type": "Question",
          "name": "How long does implementation with Laioutr take?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "A pilot is usually live within 14 days, and migration takes less than 14 days at the median. Founder-led migration is standard, not an extra charge. With multi-site or complex requirements, the timeframe depends on the scope."
          }
        },
        {
          "@type": "Question",
          "name": "What does Laioutr cost compared to a custom build?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Laioutr works with transparent SaaS plans based on traffic and features. The total cost of ownership is typically below that of a custom build, because Studio, components and editor are part of the platform and no separate frontend team is needed. Cloud/Edge Hosting is available as an add-on and is not included in the license."
          }
        },
        {
          "@type": "Question",
          "name": "Can the backend be switched later without rebuilding the frontend?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. Laioutr is backend-agnostic. If another system is added alongside TYPO3 later, such as a commerce backend, it is connected via an API instead of rebuilding the frontend."
          }
        },
        {
          "@type": "Question",
          "name": "Is the solution BFSG- and GDPR-compliant?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. Laioutr is GDPR-compliant by default, EU hosting is available, further regions on request (US, APAC), and regional data residency is possible. In addition, there is an EU standard contract and German-language support. WCAG and the BFSG (German Accessibility Strengthening Act, binding since 2025) are covered by default: compliance is built in, not bolted on."
          }
        },
        {
          "@type": "Question",
          "name": "What happens to existing TYPO3 extensions?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Backend extensions (editorial, permissions, import, workflows) remain unchanged. Frontend-oriented features are typically replaced by Laioutr components or pre-integrated apps. The extension stack is reviewed in the migration audit."
          }
        },
        {
          "@type": "Question",
          "name": "Is Laioutr itself also a CMS?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "Yes. Laioutr is also an integrated headless CMS: content collections, Studio and frontend in one platform. With TYPO3 in place, Laioutr acts as the visual page builder and frontend, while TYPO3 remains the leading CMS. Content that should not be maintained in TYPO3, for example for campaigns, can be managed directly in Laioutr."
          }
        }
      ]
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://www.laioutr.com/en/page-builder-typo3#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Laioutr",
          "item": "https://www.laioutr.com/en/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Page Builder for TYPO3: Build Pages Visually"
        }
      ]
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#webpage",
      "description": "Page builder for TYPO3: Laioutr adds a visual editor and fast frontend to TYPO3 content. No Fluid templating, accessible and GDPR-compliant.",
      "name": "Page Builder for TYPO3: Build Pages Visually | Laioutr",
      "url": "https://www.laioutr.com/en/page-builder-typo3",
      "@type": [
        "WebPage",
        "FAQPage"
      ],
      "mainEntity": [
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/1"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/2"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/3"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/4"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/5"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/6"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/7"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/8"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/9"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/10"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/11"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/12"
        },
        {
          "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/13"
        }
      ]
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/1",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Does Laioutr work with TYPO3 (multi-site and multilingual)?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. Laioutr reads TYPO3 content via the headless/content API and supports multi-site, multiple domains and multilingual setups, provided the corresponding API endpoints are available.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/2",
      "@type": "Question",
      "inLanguage": "en",
      "name": "How does Laioutr differ from a custom build with Next.js or Nuxt?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>A custom build typically takes six to twelve months of engineering plus ongoing maintenance by an in-house frontend team. Laioutr delivers Studio and 70+ components ready to use, with Cloud/Edge Hosting available as an add-on. Time-to-launch drops from months to weeks, and the total cost of ownership is typically well below.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/3",
      "@type": "Question",
      "inLanguage": "en",
      "name": "How does Laioutr differ from Fluid and TypoScript?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Fluid and TypoScript are the classic developer route: every layout change goes through development. Laioutr delivers a visual builder, ready-made components, Themes and Blueprints, so marketing and editorial teams can build pages themselves, without a ticket for every change.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/4",
      "@type": "Question",
      "inLanguage": "en",
      "name": "How does Laioutr connect to TYPO3?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Laioutr connects via the TYPO3 headless/content API (JSON). Standard content (pages, content elements, navigation, translations) is supported, plus project-specific endpoints for custom logic.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/5",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Does Laioutr work with TYPO3 multi-site?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. TYPO3 sites are treated as standalone frontends in Laioutr. Layouts, content, languages and domains can be configured separately per site, in line with the TYPO3 multi-site concept.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/6",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Can editorial workflows and permissions from TYPO3 still be used?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. Editorial workflows, permissions and approvals remain in TYPO3. Laioutr renders the approved content, and governance stays entirely in TYPO3.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/7",
      "@type": "Question",
      "inLanguage": "en",
      "name": "TYPO3 already has an API with EXT:headless, so why Laioutr?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Precisely because TYPO3 exposes content as an API, the frontend question remains open: TYPO3 delivers the data, but not the finished, visually operable frontend. Laioutr builds on this content API and makes the frontend operable for marketing, editorial and development teams together, without separate frontend development.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/8",
      "@type": "Question",
      "inLanguage": "en",
      "name": "How long does implementation with Laioutr take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>A pilot is usually live within 14 days, and migration takes less than 14 days at the median. Founder-led migration is standard, not an extra charge. With multi-site or complex requirements, the timeframe depends on the scope.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/9",
      "@type": "Question",
      "inLanguage": "en",
      "name": "What does Laioutr cost compared to a custom build?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Laioutr works with transparent SaaS plans based on traffic and features. The total cost of ownership is typically below that of a custom build, because Studio, components and editor are part of the platform and no separate frontend team is needed. Cloud/Edge Hosting is available as an add-on and is not included in the license.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/10",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Can the backend be switched later without rebuilding the frontend?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. Laioutr is backend-agnostic. If another system is added alongside TYPO3 later, such as a commerce backend, it is connected via an API instead of rebuilding the frontend.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/11",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Is the solution BFSG- and GDPR-compliant?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. Laioutr is GDPR-compliant by default, EU hosting is available, further regions on request (US, APAC), and regional data residency is possible. In addition, there is an EU standard contract and German-language support. WCAG and the BFSG (German Accessibility Strengthening Act, binding since 2025) are covered by default: compliance is built in, not bolted on.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/12",
      "@type": "Question",
      "inLanguage": "en",
      "name": "What happens to existing TYPO3 extensions?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Backend extensions (editorial, permissions, import, workflows) remain unchanged. Frontend-oriented features are typically replaced by Laioutr components or pre-integrated apps. The extension stack is reviewed in the migration audit.</p>"
      }
    },
    {
      "@id": "https://www.laioutr.com/en/page-builder-typo3#/schema/question/13",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Is Laioutr itself also a CMS?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Yes. Laioutr is also an integrated headless CMS: content collections, Studio and frontend in one platform. With TYPO3 in place, Laioutr acts as the visual page builder and frontend, while TYPO3 remains the leading CMS. Content that should not be maintained in TYPO3, for example for campaigns, can be managed directly in Laioutr.</p>"
      }
    }
  ]
}
```
