Spelling and TYPO3 Terminology

This section establishes common keywords and the terminology that TYPO3 uses. For a guide on how to spell certain trademark and product names, see Spelling, terms and glossary.

Spelling and TYPO3 Terminology

  • A

    • Admin Panel

      The Admin Panel is an administrative tool that can be enabled in the frontend to show debugging information, performed SQL queries and more for authenticated backend users.

    • Admin Tools

      Admin tools are a group of backend modules. These include maintaining the installation, adjusting settings, executing upgrade wizards, checking environment information and setting up extensions.

    • Allow Fields

      Allow fields refer to fields of content elements displayed in the TYPO3 backend with regard to their permissions. Editors can only edit fields in the backend which are included in the list of "Allow fields" in their permission setup.

    • Assets

      Assets are media resources such as images, videos and documents that are uploaded and managed in the TYPO3 system. Also, extensions can include assets which can be referred to in the frontend, like specific icons or JavaScript libraries.

  • B

    • Backend / Frontend

      The Backend and Frontend are the two main areas of TYPO3 CMS. The backend is the administrative interface for editors and administrators. The frontend is the publicly accessible part of the website.

    • Backend Bookmarks

      Backend bookmarks are shortcuts that users can set for frequently used backend pages for quicker access.

    • Backend Layout

      The backend layout defines the structure and design of the backend user interface for maintaining content elements and the layout of their input fields. A backend layout can be set on the page-level, and this attribute can actually be also evaluated in the frontend, to affect the arrangement of elements on a page.

    • Backend Module

      Backend modules are extendable components in the TYPO3 backend that provide various functionalities and tools such as user management and file management. The left hand panel in the backend display all the modules.

  • C

    • Callout

      A callout is a highlighted element designed to draw attention to important information or actions.

    • Cache (Cache Backend, Frontend Cache)

      Caches are used to improve website performance by storing frequently accessed data. TYPO3 has multiple caches for various performance relevant areas in both for the frontend and backend.

    • Cache Tags

      With cache tags one or more cache entries can be grouped together such that all cache entries related to a cache tag can be invalidated with just one call.

    • Certification (TCCC, TCCD, TCCI, TCCE)

      Certifications in the TYPO3 ecosystem, such as TCCC (Consultant), TCCD (Developer), TCCI (Integrator), and TCCE (Editor) confirm the proficiency of developers and integrators in various aspects of TYPO3 CMS. TYPO3 has an official certification strategy.

    • CIG/SIG (Special Interest Group)

      Special Interest Groups (SIGs) are groups of experts and enthusiasts who focus on specific topics within the TYPO3 ecosystem and work on improving those areas.

    • Clipboard

      The clipboard in the TYPO3 backend is a tool for copying, cutting, and pasting content elements and records.

    • colPos

      colPos is a column in the TYPO3 database that defines the position and layout of content elements on a page within a template.

    • Constants/Setup

      Constants and Setup are configuration options in TYPO3 TypoScript that set basic settings and variables for the website. "Constants" can be seen as variables that reference content defined in the backend GUI. The "Setup" uses these "Constants" to put the variables where they are needed, to define behaviour of the frontend (and sometimes also backend).

    • Content Blocks

      Content blocks are predefined layouts and content elements that can be used to create page content in the TYPO3 backend. Currently Content Blocks refers to an extension which will be included in TYPO3 v13. Content Blocks are configuration sets which define backend input and frontend output.

    • Content Elements

      Content elements in TYPO3 are blocks of content that can be displayed in the frontend. Each content element has many (and also custom) attributes, and can even consist of nested hierarchies of further content elements.

    • Core

      The TYPO3 Core is the central framework of the CMS that provides basic functions and features.

    • Core Development

      Core Development refers to development and maintenance of the central TYPO3 framework by the Core Team.

    • Core Merger

      A Core Merger is a person or team member responsible for merging code changes and updates into the TYPO3 core. TYPO3 Core Mergers are elected in a formal process.

    • Core Team

      The Core Team consists of the main developers (Core Mergers) and contributors responsible for developing and maintaining the TYPO3 core.

    • Crop variants

      Crop Variants are different cropping options for images that can be defined and used within the TYPO3 system, for example an image can have a crop variant for "mobile" and "desktop", or different aspect ratios.

    • Crowdin

      Crowdin is a translation tool used for localizing and translating TYPO3 content into different languages.

    • CType

      CType refers to Content Type and is a database column field in a very important database table called "tt_content", where all the content elements are stored. This column defines the name of the specific content element, and influences how it is displayed in the backend and frontend.

  • D

    • Dashboard / Widgets

      The dashboard is a customizable start page in the TYPO3 backend that provides quick access and contains various widgets for displaying important information. access.

    • Data Processor

      A data processor is a component that processes and manipulates data before it is displayed in the TYPO3 frontend. Data processors are implemented in PHP code. They can be executed via TypoScript configuration and manipulate data that is passed to Fluid templates. It is therefore a way of manipulating data before it is passed to the presentation layer (Fluid templates).

    • Data Provider

      A data provider is a data source that can be used by other components in the TYPO3 system. Data providers are commonly used for passing on data in the backend (for example by defining which icons are available, item keys and values).

    • DataHandler

      The DataHandler is a central component of TYPO3 and it is responsible for processing and storing data changes. It is a large PHP class that is used in the backend to receive data from the FormEngine (content elements and records), and is also part of an API that can be used by extensions to operate on records.

    • DB Analyzer / DB Compare

      DB Analyzer and DB Compare are tools in TYPO3 that analyze and compare database structures to identify changes that are needed at the database level for for upgrades and extension integration. Other systems often call this "database migration".

    • DB Mounts / Mount Points

      Mount points allow TYPO3 editors to mount a page (and its subpages) from a different area in the backend page tree.

    • DBAL

      The Database Abstraction Layer (DBAL) is collection of API Interfaces and Classes in TYPO3 that allows abstract access to various database systems. SQL queries can be executed without needing to be adapted to specific database systems such as MariaDB, MySQL, PostgreSQL and SQLite.

  • E

    • Enhancer

      An enhancer is a component that adds additional functionality or improvements to existing TYPO3 features, most commonly used for "Routing Enhancers" operating on speaking URL fragments.

    • Exclude Fields

      Exclude fields are fields that are configured as "excluded" in the TCA so that they are hidden in the TYPO3 backend for specific users or user groups. This is done via the permission setup.

    • Extbase

      Extbase is a framework for developing extensions in the TYPO3 system. It uses the Model-View-Controller (MVC) principle. It allows models and data fields (stored as records) to be easily defined and to be easily managed by editors in the backend. Models can also be shown in the frontend using custom logic, adhering to standards, conventions and API definitions. Extbase plugins include Extbase controllers where custom logic can be added using PHP.

    • Extension

      An extension is an add-on to the TYPO3 system that adds additional functionality and features. An extension can consist of multiple parts, for example backend modules, frontend plugins, scheduler tasks, console commands, API definitions and frontend styling.

    • Extension Builder

      The Extension Builder is a backend module in TYPO3 that facilitates the creation of extbase extensions. The Extension Builder is a community extension and maintained on its own.

    • Extension Manager

      The Extension Manager is an interface in the TYPO3 backend used for installing, updating, and managing extensions. It is very important in legacy installations, but in Composer-based installations it is only used for configuring extensions (composer then manages the (de-)installation of extensions).

    • Extension Scanner

      The Extension Scanner analyzes installed extensions for compatibility issues with current and future TYPO3 versions. It can report fixes that are needed to upgrade extensions.

  • F

    • FAL

      The File Abstraction Layer (FAL) is a system in TYPO3 that centralizes management and access to files and media resources. This is the technical interface (API) to the integrated media asset database.

    • fe_groups / be_groups

      Frontend groups fe_groups and backend groups be_groups are user groups in TYPO3 that define permissions and roles. Frontend groups restrict frontend content and possible actions to specific users in those groups. Backend groups allow the definition of permissions for content and which actions can be performed in the backend.

    • felogin

      EXT:felogin is a TYPO3 system extension for managing and authenticating frontend users.

    • fe_users / be_users

      Frontend users fe_users and backend users be_users are the two main types of user in the TYPO3 system.

    • file reference

      A file reference is a reference to a file in the TYPO3 system. A file reference (as opposed to a file copy) is a pointer to the original file, so that when the original file changes, all references will too.

    • file resource

      A file resource is a physical file that is stored and managed within the TYPO3 system. A file reference always points to a file resource.

    • file storage

      File storage in TYPO3 manages the organization and storage of files and media resources. Other systems may refer to this as "asset storage".

    • fileadmin

      The fileadmin area is a special folder in the TYPO3 backend for files and media resources. This has been the default name of the file storage since TYPO3 versions, but can be customized.

    • Filelist

      The EXT:filelist is a module in the TYPO3 backend used for displaying and managing files and media resources. It displays the content of all configured file storage. When referencing files from content elements, a popup window will display the filelist in the backend.

    • Flash Message

      Flash Messages are notifications in the TYPO3 backend that inform users about important events or changes. The Extbase framework has an API to display flash messages in the frontend.

    • FlexForm

      FlexForms are a way of adding additional content element settings in the Backend and which can be accessed in the frontend. A flexForm data source (in XML format) defines sheets, sections and fields, which are displayed alongside a record in the backend record editing interface (based on TCA naming). The values entered in a FlexForm data source are saved as XML data (as a "blob", so will need serialization and deserialization when being accessed), which allows for customizable additional data storage as well as the relational database tables (like tt_content).

    • Fluid

      Fluid is a template engine in TYPO3 used for creating dynamic and customizable frontend layouts. It looks like HTML and has embedded tags that can be customized. It also has standard variable replacement as well as a large range of algorithmic and logical operations.

    • Forge / Forger / Gerrit

      Forge is the central platform for issues and where the Core Team manage the TYPO3 project and its features and bugs. Forger and Gerrit are tools for code review and management.

    • Form Framework / Form Extension

      The EXT:form framework in TYPO3 is used to create and manage complex forms with many fields and validations. Backend modules allow these forms to be configured through a powerful GUI.

    • Form Variants

      Form Variants are different versions or variations of a form built in the form framework, that can be defined and used within the TYPO3 system.

    • FormEngine

      The FormEngine is a vital component in TYPO3 responsible for displaying all record and content editing parts in the backend.

    • fsc / csc

      fsc (Fluid Styled Content) and csc (CSS Styled Content) are system extensions that can be used to render content elements in the frontend.

  • G

    • GeneralUtility

      GeneralUtility is a central PHP class in TYPO3 that provides a variety of general functions and methods.

    • GifBuilder

      GifBuilder is an API set in TYPO3 for creating and editing images. It is called "Gif"-Builder but it can deal with all image formats and is used to embed overlays and other manipulations (color, geometry) into media files.

  • I

    • Indexed Search

      Indexed Search is a system extension in TYPO3 for implementing search on a website.

    • Infobox

      An infobox is a highlighted area on a page that contains important information.

    • Install Tool

      The Install Tool is a tool in the TYPO3 backend used for installing and configuring/upgrading the system.

    • Integrator / Developer

      Integrator and Developer are roles within the TYPO3 ecosystem. Integrators are responsible for setting up and configuring the system, and developers create new extensions and features.

    • Introduction Package

      The Introduction Package is a sample package in TYPO3 that contains a pre-configured website with content and configuration.

    • IRRE

      IRRE (Inline Relational Record Editing) is a feature in TYPO3 where related (child) records can be edited directly in the backend (via a form). It is displayed in a nested accordion structure (also supports tabs).

    • ItemProcessor

      An ItemProcessor is a component that processes and manipulates individual data elements used within the FormEngine.

  • L

    • Legacy Installation

      TYPO3 can be operated in one of two modes: "Composer Installation" (using the Composer ecosystem and tooling to setup TYPO3, also referred to as "Composer mode") or "Legacy Installation", in which TYPO3 distribution files are maintained as a simple set of files and folders on a server.

    • Link Browser

      The Link Browser is a tool in the TYPO3 backend for creating and managing links and references. It can be accessed when inserting links into content elements and opens as a popup, allowing pages, records, media files, or URLS to be selected for all fields configured as a "link type", or in plain content edited through the RTE.

    • LinkHandler

      The LinkHandler is a component in TYPO3 that provides advanced link and reference functionality. Each type of Link (for example: files, pages, records, mails, telephone, ...) is implemented via the LinkHandler API.

    • Linkvalidator

      Linkvalidator is a tool in TYPO3 that checks links and references on a website for validity and identifies broken or invalid links. It operates on content elements and their data fields.

    • List View

      The Web -> List view is a view in the TYPO3 backend used for displaying and managing records in a list format.

  • M

    • Maintenance Mode

      Maintenance Mode in TYPO3 is used to temporarily take a website offline for updates or maintenance. Only maintainers (administrators) can then access the backend and frontend.

    • Maintenance Tool

      The Maintenance Tool is a tool in the TYPO3 backend used for performing maintenance tasks and system optimizations. It is part of the "Admin Tools" backend module.

    • makeInstance

      GeneralUtility::makeInstance() is a method in the TYPO3 PHP API used for creating instances of classes and objects. It can use "Dependency Injection" for service classes.

    • Modal

      A modal is a dialog or pop-up window in TYPO3 that prompts users to enter or confirm information.

    • Module

      A module is a component that extends the TYPO3 backend by providing various functionality and tools. Modules are usually "Backend Modules", and appear in the left-hand side navigation.

    • Multisite

      Multisite refers to the capability of TYPO3 to manage multiple distinct websites in a single installation.

  • O

    • Overrides

      Overrides, specifically "TCA Overrides", allow TYPO3 extensions to change core configuration of records and content elements.

  • P

    • Package

      A Package is a bundle of files and resources used for installing and configuring extensions or functionalities in TYPO3. Usually, TYPO3 extensions are available as "Composer Packages", hence the term "package".

    • Page Frame / Tree Frame / Module Frame / Navigation Frame

      Page frame, Tree frame, and Module frame are sections in the TYPO3 backend where content and modules are displayed and can be navigated.

    • Page Tree

      The Page Tree is a hierarchical representation of the page structure in the TYPO3 backend. It is displayed in the middle section of the TYPO3 Backend where content is edited.

    • Page View

      The Page View is a view in the TYPO3 backend where page content is edited and managed.

    • Page builder / Sitepackage Builder

      A Sitepackage Builder, or Pagebuilders, are tools in TYPO3 for creating and designing page layouts and content. They are often used to create "Sitepackage extensions", which define the TYPO3 frontend appearance and the definitions of content elements. Since these sitepackages can often be repetitive and contain boilerplate code, builders can help to auto-generate these sitepackages.

    • PageRenderer

      The PageRenderer is a PHP API component in TYPO3 responsible for rendering and displaying page content in the frontend.

    • Palette (TCA)

      A Palette in the TCA (Table Configuration Array) is a grouping of fields that are displayed and edited together.

    • Partial

      A Partial is a re-usable component of Fluid templates, that can be parametrized.

    • Permissions / ACL

      Permissions and Access Control Lists (ACL) are mechanisms in TYPO3 for managing access rights and restrictions for users and groups.

    • piBase

      piBase was a base class for developing frontend plugins in TYPO3. The name "piBase" is based on the old class class.tslib_pibase.php ("pi" for "PlugIn"), which has now been moved into a AbstractPlugin API class and provides base functionality that can be extended. Nowadays, it has been superseded by Extbase and completely customized PHP-code plugins.

    • pid / uid

      Each page and content element as a unique identifier (uid) assigned to it. The pid stands for "parent id" and references this uid for child records.

    • Plugin

      A plugin is an extension in TYPO3 that adds additional functionality and features to a website. The term "Frontend plugin" usually defines a content element that renders dynamic frontend functionality by utilizing Extbase, Fluid or raw PHP code.

    • Processed file

      A processed file is a file that has been handled and optimized by TYPO3, such as being cropped or compressed. It is a persisted artifact that can be regenerated if missing.

  • R

    • Realurl

      Realurl was a commonly used TYPO3 community extension that created and managed user-friendly URLs. Now, the TYPO3 Core offers exhaustive URL rewriting capabilities with Site Matchers, Route Enhancers/Decorators and slugs.

    • Records

      A record is the smallest unit of a database entry. A record can be a content element but also any configuration record, data storage record, user data record and much more. Records are defined via the TCA and can be edited in the backend GUI depending on their configuration.

    • recycler

      The Recycler is a backend module for managing and restoring deleted records.

    • Redirects

      Redirects are links that direct users from one URL to another, often used to correct outdated or invalid links.

    • RenderType

      RenderType is a TCA setting in TYPO3 that defines the rendering mode of fields and content elements when displayed in the FormEngine.

    • Repository

      This term is usually referred to in Extbase-context, and defines a PHP API class in Domain Driven Design (DDD) that manages access to entities/models defined through configuration and database records.

    • reports

      Reports are analyses and insights in the TYPO3 backend that provide information about system performance and usage of extensions.

    • reST / reStructuredText

      reST (reStructuredText) is a markup format used for creating and formatting documentation ssuch as the official TYPO3 documentation and public extensions.

    • Route Enhancer

      A Route Enhancer is a component in TYPO3 used for improving and customizing URL routing logic. It is part of the YAML Site configuration.

    • Route Decorator / Enhancing Decorator

      Route Decorators and Enhancing Decorators are part of Route enhancement and can be seen as configuration and API implementations where URL routing can be accessed and rewritten.

    • RTE (also: WYSIWYG, CKEditor, htmlarea, t3editor)

      A Rich Text Editor (RTE) is a tool in TYPO3 that enables WYSIWYG editing (What You See Is What You Get), part of the CKEditor Open Source project. An older component was "rte_htmlarea". The t3editor is a specific RTE that handles syntax-highlighting for code languages.

    • runTests.sh (?)

      runTests.sh is utility Script provided internally by the TYPO3 Core, which allows several test types to be run (functional tests, unit tests, acceptance tests) and where Core developers can manage instances for building assets.

  • S

    • scheduler

      The scheduler is a backend module that manages and executes regular, scheduled tasks, such as regular purging of temporary data.

    • Scheduler Tasks

      Scheduler tasks in TYPO3 are automated jobs that can be scheduled to run at specific times or intervals.

    • showfields (TCA)

      showfields settings in the TCA (Table Configuration Array) that define which fields are displayed in the FormEngine backend GUI.

    • SignalSlot / Hook / Event Dispatcher + Listeners

      SignalSlot was a design pattern in TYPO3 for implementing event-driven programming and allowing components to communicate with each other. This was superseded by the PSR-14 compatible Event-API (using a Dispatcher and Event Listeners).

    • Site Configuration

      A Site Configuration includes settings and options that affect the behavior and display of a TYPO3 website, mapped to a specific domain (with variants). The Site Configuration also includes site settings, which is a simple key/value storage of variables that can affect the frontend (or backend sections).

    • Site Language / Page Language

      Site language and page language define the languages in which a TYPO3 website and its content are displayed. It is part of the site configuration.

    • Site Management

      Site management includes tools and functions for managing and maintaining a TYPO3 website, including the site configuration of each site.

    • Site Matcher

      A site matcher is a component in TYPO3 used for mapping and processing URL patterns and requests in conjunction with a specific part of the page tree (root page/site).

    • Site Package

      A site package is a pre-configured package in TYPO3 that usually contains configuration, Content Element definitions, functionality (like PSR-14 event listeners, middleware), templates and sample content.

    • Site Sets

      Site Sets are predefined collections of settings and configurations used for setting up and managing TYPO3 websites, mainly used to assign TypoScript configuration to a site.

    • Sites

      Sites are the various websites / projects managed and operated within the TYPO3 system. Site is the short form for "Website".

    • Slug

      A slug is a user-friendly part of a URL, often generated from the page title or content elements. A URL can consist of multiple slug parts.

    • Static File Cache

      Static file cache is an extension that is used to store pre-rendered pages as static files to improve performance, such as a static page generator.

    • Styleguide

      The styleguide extension is a collection of sample TCA-based content elements to showcase the functionality of TYPO3. It also features an example page tree for both these backend elements, as well as a frontend example site. The module also showcases all GUI elements (like dialogs, alerts, colors, accordions, grids, ...) that TYPO3 uses in the backend.

    • SVG Tree

      The SVG tree is a visual representation of the page and content structure of a TYPO3 website in SVG format. This is the technical visual version of the page tree.

    • sys_log / sys_history

      The sys_log and sys_history are database tables in TYPO3 for recording and tracking system events and changes.

    • sysext

      Sysexts are SYStem EXTensions in TYPO3 that provide core functions and features. This is the name of a central TYPO3 Core Sourcecode directory, and in older TYPO3 versions there was a clearer separation between system and local extensions.

  • T

    • T3DD

      T3DD stands for TYPO3 Developer Days, an annual conference for TYPO3 developers and enthusiasts.

    • TCA

      The Table Configuration Array (TCA) is a central configuration structure in TYPO3 for defining and configuring database tables and fields.

    • TCEforms

      TCEforms are forms in TYPO3 used for editing database entries and content elements in the backend.

    • Templates (=Fluid)

      Templates in TYPO3, often created with Fluid, define the structure and layout of the frontend.

    • TER

      The TYPO3 Extension Repository (TER) is a central directory for distributing TYPO3 extensions.

    • Testing Framework

      The Testing Framework in TYPO3 provides tools and methods for conducting automated tests used for developing the TYPO3 Core or custom projects and extensions.

    • TSconfig

      TSconfig uses the TypoScript configuration language in TYPO3 and is used for defining backend settings and configuration options. This is separated into "User TSconfig" and "Page TSconfig"

  • U

    • uid

      uid stands for Unique Identifier and is a unique identifier for records and objects in the TYPO3 system. It complements the pid (parent identifier).

    • upgrade wizard

      The upgrade wizard is a module in the TYPO3 backend used for performing system and database upgrades.

  • V

    • Vendor

      The term "Vendor" is most commonly used as a semantic grouping identifier for PHP namespaces in extensions. Composer collects all packages in a directory, that is also usually called "vendor" and contains subdirectories with the PHP namespace identifiers. A vendor can then provide multiple distinct extensions, each separated by an extension name identifier. The PHP Composer class-Loading functionality depends on these two basic identifiers.

    • ViewHelper

      ViewHelpers are logical helper functions, utilized in Fluid templates and partials. ViewHelpers are implemented as PHP code and can perform any kind of functionality, however they should only be used for managing context of frontend output and should not contain too much domain logic.

  • W

    • Workspace(s)

      Workspaces are areas in TYPO3 used for managing and editing content in a "versioned" way. They allow to prepare content to be published, and verified in workflow steps before.

    • Web Component

      The TYPO3 Cores backend makes considerable use of JavaScript-based, standards-compliant web components. These offer dynamic functionality using a standards-driven approach, compatible with most browsers and offering graceful degradation.

  • X

    • XCLASS

      XCLASS is a mechanism in TYPO3 that allows developers to extend or override existing classes and functions. The TYPO3 Core can then replace one instance of a class with another custom class.