Glossary
TYPO3 Glossary
TYPO3 comes with a vocabulary of its own, and most of these words turn up in quotes and project meetings before anyone has explained them. Here they are in plain terms, each with the situation you actually run into it in.
The definition of which content areas a page has and how they are presented to editors in the backend.
The German law obliging certain consumer products and services to be accessible. In force since 28 June 2025.
The intermediate storage of rendered content, so TYPO3 does not recalculate everything on every request.
The tool that manages and installs TYPO3, its extensions and their dependencies.
An approach for defining custom content elements compactly, instead of spreading the configuration across several files.
The framework used to build custom TYPO3 extensions with data models of their own.
A package that adds features to TYPO3, from the sitepackage to a search engine integration.
The file handling of TYPO3: every file is a record with metadata, not just a path in a directory.
Extra settings fields per record, stored as XML in a single database column.
The template language of TYPO3. It decides how data is turned into HTML.
Long Term Support: the period in which a TYPO3 version receives security fixes as a matter of course.
An extension for clicking custom content elements together in the backend. No longer developed for TYPO3 v14.
The rules by which TYPO3 builds addresses and resolves them back to content.
The task scheduling of TYPO3, for everything that should happen regularly and without anyone doing it.
The configuration that assigns a page tree its domain, its languages and its URL rules.
A named configuration package a site can include. Since TYPO3 v13 the intended way to reuse configuration.
The project's own extension, holding the templates, TypoScript and configuration of a TYPO3 site in one place.
A standalone search engine that indexes TYPO3 content and does considerably more than the built-in search.
The configuration that decides how database fields appear and are validated in the TYPO3 backend.
The configuration of the TYPO3 backend, split into areas of the site (page TSconfig) and users (user TSconfig).
The configuration language that decides what the TYPO3 frontend outputs and how it behaves.
A working area where changes are made and reviewed before they appear on the live site.
Term cleared up. What now?
If the question turns into a project: we build, migrate and look after TYPO3 installations.