T3-NEWS

TYPO3 v14

the next Are beginns

What immediately impresses:

  Fresh backend and better orientation. Modules have been renamed in a meaningful way (for example, Web → Content, Files → Media) and the new breadcrumb improves clarity – noticeably speeding up everyday work.

Fluid 5 and modern templates. Cleaner templates, new ViewHelpers, and a more robust foundation for high‑performance projects.

Multilingual made manageable. The new guided translation workflow walks teams through translations step by step – ideal for international websites.

Future‑proof foundation. Over 2,000 improvements, a streamlined core, and modern standards – PHP 8.2+ is the recommended baseline.

Roadmap, that builds trust

 TYPO3 v14 follows a transparent cycle:

 

  • 14.0 (Breaking Changes) – 25.11.2025 
  • 14.1 (Feature Integration) – 20.01.2026 
  • 14.2 (Feature Freeze) – 31.03.2026 
  • 14.3 (LTS) – 21.04.2026. This means that the range of functions is frozen in good time and LTS offers the usual stability for productive use.

The last News in Typo3 v14

TYPO3 14: Camino, Content Restrictions, Site Sets & Fluid 5 — What Matters Most

TYPO3 v14 introduces the new default theme Camino, built-in content element restrictions per column, Site Sets for cleaner, reusable configuration, and Fluid 5 with stricter typing and changes to CDATA/namespace behavior. Result: faster starts, cleaner integrations, and fewer upgrade pitfalls.

Camino: The new default theme for rapid starts

With Camino, TYPO3 now ships an optional, encapsulated default theme that lets fresh installs display a working frontend in minutes—without third‑party dependencies and without fluid_styled_content. Camino provides multiple color schemes, configurable backend layouts (start page, content page, content + sidebar), and a globally inherited footer. You enable it per site via “Sets for this Site.”

Quickstart & setup: The official quickstart walks you from installation through Camino configuration, including Composer commands and backend screenshots.


Note: Camino is completely optional and won’t interfere with existing setups; for Composer projects the package is typo3/theme-camino.

Content element restrictions: now core, no extension required

From TYPO3 v14.1 onwards, you can define per backend layout column (colPos) which content element types are allowed or disallowed—for example, “sidebar only CTA,” “no headers in the footer.” Implemented via two new PageTS keys in backend layout definitions: allowedContentTypes (allowlist) and disallowedContentTypes (denylist). The new content wizard, edit forms, and move/copy operations all honor these rules. (Database‑based backend layouts can’t configure these values yet; support is planned.)

 

Plugin heads‑up: As of TYPO3 13.4, list_type plugins are deprecated and removed in v14. Migrate plugins to CType for proper restrictions and a clean UX (official guide + upgrade wizard).

Site Sets: modular, reusable configuration

Site Sets bundle TypoScript (setup/constants), PageTS, and site settings into clear, reusable packages. They’re activated per site as dependencies and replace many older include/record patterns—excellent for multi‑site setups and agency standards.

Structure & definition: In Configuration/Sets/<YourSet>/ you define config.yaml (name/label/dependencies) plus settings.yaml, page.tsconfig, constants.typoscript, and setup.typoscript. Activation in the backend: Sites → [Site] → General → Sets for this Site. The core docs and community guides provide solid intros and migration tips.

Fluid 5: stricter types, new CDATA rules & namespace changes

Shipped with TYPO3 v14, Fluid 5 introduces a few changes that integrators and template authors should address:

1.) Stricter ViewHelper typing – Argument validation is tighter; tag‑based ViewHelpers now omit attributes whose value is null (instead of rendering attr=""). Audit attributes like alt, placeholder, class, etc. 

2) No automatic namespace inheritance – ViewHelper namespaces are not inherited from templates to layouts/partials; declare them explicitly. 

3) New CDATA semantics – Inside <![CDATA[ ... ]]>, {} is ignored; use {{{variable}}} for variables/ViewHelpers. For commenting out template code, prefer <f:comment>.

What this means for projects

  • New builds benefit from Camino (fast, dependency‑free start) and Site Sets (standardized config).

     

  • Existing sites should review Fluid templates (namespaces/CDATA/types) and migrate list_type → CType where needed; column restrictions can significantly improve editorial quality

Further reading

  • Feature: Default Theme “Camino” (Changelog) — core docs.
  • TYPO3 News: Introducing Camino — overview & screenshots.
  • Quickstart v14 + Camino — step‑by‑step guide.
  • Content element restrictions per column (Changelog) — PageTS keys & event.
  • Site Sets (Core docs) — definition, dependencies, API.
  • Fluid 5 (Changelog 5.x & “Strict Types” breaking change) — technical details.
  • Migration list_type → CType — official migration guide

Upgrade Pfad mit Ansage

The path from v13 to v14 is clearly documented. 

Key point: scheduler tasks are migrated to a new format (make sure to run the upgrade wizard). 

For production systems, it is recommended to start from the feature freeze phase (14.2) or go straight to 14.3 LTS once extensions have been widely updated.

What immediately inspires enthusiasm 

  • Fresh backend & better orientation. Modules have been renamed appropriately (e.g., Web → Content, Files → Media), and the new breadcrumb trail provides clarity—this noticeably speeds up daily work.
  • Fluid 5 & moderne Templates. Cleaner templates, new ViewHelpers, and a more robust foundation for high-performance projects.
  • Multilingualism under control. The new guided translation workflow Guides teams step by step through translations – ideal for international appearances.
  • Future-proof foundation. Over 2,000 improvements, a tidier core, and modern standards – PHP 8.2+ is the recommended basis.

                your Benefits on 2026
            
[Translate to US:] TYPO3 Background
With TYPO3 v14, you’re future‑proofing your platform for the coming years: faster editorial workflows,
 a modern developer experience, and reliability thanks to a clear product roadmap. typo3‑solutions handles setup,
 migration, and fine‑tuning so your team can focus on content and growth.

                Why choose typo3‑solutions?
            

                typo3‑solutions begleitet dich vom ersten Konzept bis zum Go‑Live – 
            
  • Quick start & clean architecture. We deliver v14 with a modern backend, Fluid 5, and clear content structures—including setup for multilingualism and translation workflows.
  • Performance without ballast. We enable server-side compression and concurrency instead of outdated concatenation—for measurably better load times and stable deployments.
  • Secure Migration & Roadmap‑Timing. Upgrade wizards (e.g., scheduler), extension compatibility, tests on 14.2/14.3—all orchestrated so you can go live without risk.
  • Content‑Teams relieve. We integrate v14‑Features as Guided Translation and moderne Templates, Optional AI-powered tools for text suggestions and SEO tips. 
  • Transparent planning. With the v14 release plan, you have budget and milestone security—we work together to define project phases and deadlines.

                integrations really matter – which kinds of integrations count here?
            
TYPO3 is cleaning up legacy features in a consistent way:
its own HTTP compression and asset concatenation are being removed,
because modern web servers (like Apache or nginx) handle these tasks more efficiently, and HTTP/2/3 multiplexing already scales parallel requests.
This reduces complexity and potential sources of errors in everyday use.

                Your Benefit in 2026
            
 With TYPO3 v14, you can prepare your platform for the years ahead:
Faster editing, modern developer experience, and predictability thanks to a clear roadmap.
Typo3‑Solutions takes care of setup, migration, and fine-tuning—so your team can focus on content and growth.