Glossary: P

Module for managing page content.

Page TSconfig in TYPO3 is a configuration layer applied on a page level to control backend behavior. It allows integrators to customize the editorial interface and workflows directly within the page tree.

Use Cases for Page TSconfig

Page TSconfig is typically used to tailor backend behavior, such as:

• Restricting available content elements on specific pages
• Defining default values for fields like metadata or categories
• Configuring backend layouts and modules
• Shaping editorial workflows for different page sections

How Page TSconfig Works

• Configuration is stored in page.tsconfig files or directly in page properties.
• TYPO3 evaluates Page TSconfig for each page, with inheritance down the page tree.
• Settings apply automatically to all child pages unless overridden.

Advantages

• Flexible customization of the editorial backend
• Clear rules for editors without modifying extensions
• Consistent workflows across entire page trees
• Can be combined with User TSconfig for fine-grained control

Typical Use Case

A website section should only allow “News” content elements. Page TSconfig restricts the available elements so editors can only insert and manage news items in that section.

Module where page content can be managed.

The pagetree is a hierarchical representation of the pages of your website.

PHP is a general-purpose programming language originally designed for web development.

A Plugin in TYPO3 is a specific type of extension that outputs content in the frontend. It is inserted as a “Content Element of type Plugin” within the page module.

What Is a Plugin?

Technically, a plugin is a frontend-focused extension built with Extbase and Fluid that renders dynamic content. Common examples include:

• News or event listings
• Forms or interactive elements (e.g. polls, quizzes)
• Product filters or search results

Backend Integration

Editors add plugins via content elements of the “Plugin” type. Depending on configuration, they can choose between list or detail views.

Distinction from Extension

• Every plugin is part of an extension—but not every extension contains a plugin.
• An extension may also provide backend-only features or system services.

Typical Use Case

Plugins are used when you need to render interactive or dynamic frontend content, such as news feeds, user forms, or real-time data widgets.

An ordered list of user stories containing all the functionalities, requirements, improvements and bug fixes needed for the product being developed.

The product owner is responsible for maximising the value of the product and managing the product backlog. He or she communicates the requirements and priorities to the developers and decides on the release of results.

A clear and inspiring description of the long-term goals and purposes of the product. It serves as a guide for the whole team and helps to focus on the key business achievements.