TYPO3 for publishers: workspaces and enterprise-grade structure

What is TYPO3?

TYPO3 is a PHP content management system. The repository README calls it an open source PHP based web content management system released under the GNU GPL, with copyright from 1999 by Kasper Skårhøj. Its documentation, TYPO3 Explained, describes a CMS and framework with a modular extension system built around Extbase, Fluid templating and PSR-14 events.

It is a framework as much as a product. That helps with complex sites and hurts with simple ones.

See the licence guide for what GPL means for a site owner.

Who is TYPO3 best for?

It suits larger publishers, media groups and organisations that run many sections or languages, need staged editing and want a long support window. get.typo3.org shows free support for 14 LTS through 30 June 2029, which helps a team that plans in multi-year cycles.

It does not suit a solo writer or a newsletter with a small archive. The effort to build and maintain it is higher than the benefit. Compare WordPress for speed and Drupal for a comparable structured-content approach.

Editorial workflow

The Workspaces extension is the headline. Its documentation says it introduces workflows with custom stages and versioning for a more granular editing and publishing process. The documentation lists draft changes, review through custom stages and control over who may publish. The documentation also references scheduler tasks for publication timing.

The documentation describes configurable options that decide who can perform which actions at each stage. We have not opened the detail of those permission settings and did not install the system, so we cannot tell you how heavy the setup is. Expect it to be a configuration task for an administrator, not a checkbox.

The rich text editor is CKEditor, integrated into the backend by the rte_ckeditor extension.

SEO, structured data and feeds

The SEO system extension offers special fields for search engine optimisation, HTML meta tag display and sitemaps, and its documentation highlights XML sitemaps. The Redirects extension lets you create manual redirects, list existing ones and create redirects automatically when a page slug changes, which protects links when editors retitle a story.

The documentation we opened does not describe structured data output such as JSON-LD or RSS feed generation, so we make no claim about them. If those matter, confirm them against your version or an extension. See the features checklist.

Media, multilingual and performance

TYPO3 documentation separates two kinds of translation: labels and messages, stored in XLIFF files, and content. The default language is en_US and core ships with English labels only. The 14.0 changelog lists multi-language selection in the page and list modules. We did not open the pages on site languages or translation modes, so we do not describe how linked translations work.

The 14.0 changelog also lists removal of frontend asset concatenation and compression. If you relied on that behaviour, plan to handle it at the server, build or CDN layer. We did not verify core image handling or caching options in the pages we opened.

Hosting and requirements

For TYPO3 14.3.8 the version page lists PHP from 8.2.0 up to 8.5.99. Databases supported are MariaDB 10.4.3 or later, MySQL 8.0.17 or later, PostgreSQL 10.0 or later and SQLite 3.8.3 or later. Web servers listed are Apache httpd, Nginx, Microsoft IIS and Caddy Server.

Support windows are explicit. 14 LTS has free support through 30 June 2029 and 13 LTS through 31 December 2027. For versions 12, 11 and 10, get.typo3.org says Extended Long Term Support is available for additional years of vendor-backed security updates. That is useful to know before you plan an upgrade, because the 14.0 changelog lists over 100 breaking changes.

Extending TYPO3

Extensions are the standard route. The documentation describes a modular extension system, with Extbase for MVC-style extension code, Fluid for templates and PSR-14 events for hooking into core behaviour. System extensions such as Workspaces, SEO, Redirects and rte_ckeditor show how much of the functionality is shipped as separately documented parts.

We did not verify a count of third-party extensions, so we give none. We did not open API documentation for headless use. See the headless guide for the general trade-offs.

What TYPO3 costs

The licence is free. Build cost is the main line: A framework-style system like this normally needs developers who know Fluid and extension development, which we cannot price from a primary source. Add hosting, and possibly paid extended support for older versions. We have not verified public prices, so we give no figures. See the cost guide.

Where TYPO3 falls short

• The learning curve and build effort are high for small publications.
• Major versions carry many breaking changes: over 100 listed for 14.0.
• Core ships English labels only, so language packs and content translation need configuration.
• We could not confirm structured data or feed output from the documentation we opened.
• Free support ends on stated dates, after which you pay for extended support or upgrade.

Questions to ask before choosing TYPO3

Start with the support calendar. If you launch on 14 LTS, free support runs to 30 June 2029, so decide now who will pay for the upgrade or extended support after that. Ask the agency how many breaking changes your custom code will face between major versions, given the 14.0 changelog lists over 100.

Then test the editorial path with real people. Give two editors and one approver a Workspaces trial, record how long it takes to move a story from draft to live, and note where they got stuck. Finally, confirm in writing how structured data, feeds and image delivery will be handled, because we could not confirm them from the documentation we opened.

The verdict for publishers

TYPO3 is a good fit for a publisher that wants staged editing, a long support horizon and a framework a development team can shape. Workspaces, SEO and Redirects are documented system extensions, and the release calendar is clear.

For small and medium publications it is more system than needed. WordPress or Concrete CMS are lighter-weight places to start. This profile is based on vendor documentation, not an install of our own; see how we test.