Skip to main content
t3headless
KNOWLEDGE BASE & ARCHITECTURE FAQ

Frequently Asked Questions.

Clear, authoritative answers on visual no-code element modeling, automated Next.js code generation, API velocity, TYPO3 v13 and v14 support, and Swiss SLA governance.

🔍
Showing all 17 questions
01 Do I need to write Next.js code when I create a new element in TYPO3?
+
No. That is the core advantage of T3Headless. You create Custom Elements or Container Elements visually inside TYPO3 (using the 3-tab Info, Fields, Template wizard), place them on any page, and T3Headless automatically generates the Next.js component on the frontend. You never have to open Next.js to write rendering code from scratch.
02 How do Custom Elements and Container Elements work without coding knowledge?
+
In Web > T3headless > Elements, you click "+ Create New Element" or "New Container Element", drag and drop fields (String, Text, File, Link, Repeating groups, or Columns), and save. T3Headless generates the template and click-to-copy field markers automatically.
03 How does the Next.js frontend stay in sync with TYPO3 changes?
+
After creating or updating elements or theme options in TYPO3, run "yarn themebuild" (or "npm run themebuild") in your t3headless-frontend directory to sync and regenerate all components and styles automatically.
04 Which TYPO3 versions are supported by EXT:t3headless?
+
EXT:t3headless supports TYPO3 v13 LTS and TYPO3 v14. Install via Composer ("composer require t3element/t3headless") for TYPO3 v13 and v14 (Composer is mandatory for TYPO3 v14+).
05 What is a headless TYPO3 architecture?
+
In a headless TYPO3 architecture, the backend CMS is decoupled from the frontend presentation layer. Instead of rendering HTML server-side via legacy Fluid templates, TYPO3 delivers structured content as pure JSON REST APIs directly to modern JavaScript frontends like Next.js or React.
06 What happens when I add a new field to an existing element later?
+
T3Headless protects your existing template from being overwritten. When you edit an element and add a new field, a new click-to-copy Field Marker appears above the template editor so you can place it exactly where you want.
07 Can editors manage global Logo, Favicon, Fonts, and Header layouts from TYPO3?
+
Yes. Under Theme Options > Header in TYPO3, editors can upload Logos (with custom dimensions), Favicons, Theme Fonts, CSS/JS files, or assign a dedicated TYPO3 Header Page that renders across the entire Next.js site.
08 Where can I get the official T3Headless TYPO3 extension?
+
Our official extension EXT:t3headless is published on the TYPO3 Extension Repository (TER) and pairs seamlessly with T3Element for zero-Fluid content element creation and component mapping.
09 Do editors lose the TYPO3 Page Tree in headless mode?
+
Not at all. Editors continue working with the familiar TYPO3 hierarchical page tree, drag-and-drop content elements, workspaces, and granular permissions. Our routing API mirrors the page tree automatically.
10 Is T3Headless suitable for large-scale enterprise websites?
+
Absolutely. Decoupling the CMS allows independent scaling of read-heavy frontend traffic on global CDNs while keeping the TYPO3 backend secure behind corporate firewalls or private VPC networks.
11 How is SEO handled in a decoupled TYPO3 setup?
+
All SEO fields managed in TYPO3 (meta title, description, canonical tags, OpenGraph images, robots instructions, and localized hreflang links) are included in every page JSON payload for server-side rendering and edge caching.
12 Can we migrate an existing Fluid-based TYPO3 site to T3Headless?
+
Yes. You can migrate incrementally (hybrid headless) or perform a clean frontend modernization while keeping your existing database pages, FAL media assets, and redirects intact.
13 How does real-time preview work for editors?
+
When an editor clicks "View" in the TYPO3 backend, T3Headless generates a secure preview token and opens the external frontend in draft mode, rendering unpublished changes immediately.
14 Do you provide starter kits, boilerplates, or live demos?
+
Yes. We provide starter blueprints, JSON schema references in our Documentation Hub, and personalized 1:1 walkthroughs of T3Headless and T3Element.
15 Can we integrate third-party APIs (CRM, ERP, Search, E-Commerce) alongside TYPO3?
+
Yes. A headless frontend makes composable architecture effortless. Combine TYPO3 content JSON with Algolia, Shopify, Shopware, HubSpot, or custom microservices in one unified UI.
16 What ongoing support is available after launch?
+
Our 360 Program provides continuous TYPO3 core and extension maintenance, proactive security patching, performance tuning, and dedicated Swiss engineering support.
17 Where is the T3Headless engineering team based?
+
Our headquarters and core engineering team are based in Glattpark (Opfikon), Zurich, Switzerland, operating in strict compliance with Swiss and European data protection standards.
SWISS ARCHITECTURE EXPERTISE

Have a specific question about your TYPO3 architecture?

Consult directly with our senior TYPO3 and headless engineers in Glattpark (Opfikon), Switzerland. We help you scope feasibility, migration path, and SLAs.