Study guide · CMS basics and roles

Your first day as an editor: CMS, TYPO3 and who does what

As of November 17, 2026 · TYPO3 14.3 LTS · about 21 min read

Before you create your first page in TYPO3, it pays to look at the big picture. This page explains what a content management system is, what makes TYPO3 special and how frontend and backend fit together. You learn who is responsible for what in a project and whom to ask when something is missing. Finally, it covers the browser, your most important tool.

Lena's first day

Our example is the website of the Weidenau City Library. It has pages such as Home, Events, Media, Opening Hours and Contact. Every page exists in German and in English.

Lena is new in the library's public relations team. Until now she wrote texts in a word processor and sent them by email. From today on, she maintains the website herself. Tom is the administrator. He built the website together with an agency and he grants the permissions.

On her first morning, Lena has lots of questions. Do I need to know HTML? What happens when the website gets a new design? Where do I log in? And whom do I ask when something does not work? Tom answers them one by one.

What a CMS is

A content management system, CMS for short, is software that lets several people create, organize and edit content together. It is mostly about websites. The editorial team works through forms in the browser. They do not have to write any HTML.

So a CMS is more than a program that delivers ready-made HTML files. It is not just a database for user accounts either, and it is not a service that crawls other websites.

Typical features of a CMS are:

  • User and permission management, so that each person only sees and changes what belongs to their job.
  • Media management for images, documents and videos.
  • A page structure, which in TYPO3 is the page tree.
  • Often also multiple languages and approval workflows.

The benefits for the library are obvious. Lena changes the opening hours without knowing HTML. Several people work on the same website with different permissions. The website still needs a web server, though. And a CMS does not push a page to the top of search engines by itself. Only well-kept content and good metadata do that.

People still write the texts. A CMS does not write content on its own, and AI helpers do not replace editorial review either.

A CMS is built for teamwork. Several editors can work on different pages at the same time. Permissions define who may edit which areas. Not every change needs approval from a programmer.

If a second person should check a text before it is published, TYPO3 offers workspaces. There you work in a preview environment. Changes go through stages such as Editing and Ready to publish, and only then go live. The administrator sets up workspaces. You learn more in the course “Übersetzungen und Workspaces”.

Content and design kept apart

The most important principle of a CMS is the separation of content and design. The editorial team maintains texts, images and data. The look comes from centrally maintained templates. In TYPO3 these templates usually live in a site package, built by the agency or the integrator.

When a visitor requests a page, the CMS assembles it. It takes the stored content and combines it with the template for the layout. So the finished page is not a single HTML file that someone uploaded.

How a page is built Content Texts, images, events kept by editors Template Layout, colours, fonts built by the integrator Finished page in the visitor's browser New design: swap the template, content stays
The CMS combines stored content with a central template.

This leads to the biggest benefit for editors. A new design applies to all pages without anyone re-entering a single text.

The separation helps in daily work, too. Lena does not pick a design when she saves. She does not write a stylesheet for individual pages. That keeps the look consistent everywhere.

TYPO3 in a nutshell

TYPO3 is an open source enterprise CMS. It ships with many features out of the box and can be extended with extensions. You can run it on your own servers or with a hosting provider. So it is not a site builder from a single vendor and not a blogging service.

TYPO3 is released under the GNU General Public License, GPL for short. The source code is freely available. Everyone may read, copy, distribute and change it. There is no license fee, not even for commercial websites, and no matter how many editors you have. You pay at most for services such as hosting, development or support.

A worldwide community develops TYPO3. It is supported by the TYPO3 Association and TYPO3 GmbH. TYPO3 GmbH also offers the official certifications. The backend interface is available in many languages through language packs, not only in German.

In TYPO3, packages that add features are called extensions. Much of what TYPO3 can do out of the box is itself provided as system extensions. An extension can bring a plugin. That is a content element that shows the extension's feature on a page, for example an events calendar.

So an extension and a plugin are not the same. The extension is the package, and the plugin is the building block Lena inserts on a page. Lena may not install extensions herself. The integrator or administrator does that.

You should know three addresses:

  • docs.typo3.org holds the official documentation. It is freely accessible. For editors there is the tutorial “TYPO3 Editors Guide” covering pages, content, media and languages.
  • extensions.typo3.org is the extension repository.
  • get.typo3.org offers downloads and system requirements.

Changelogs in the source code are aimed at developers. For Lena's question about how to translate pages, the Editors Guide is the right place.

Some terms come up all the time. The backend is the administration interface, and the frontend is the website. The page tree shows all pages as a structure. A page holds content elements, such as text with an image. A module is an area in the backend, for example Media for files. Add record, extension, plugin and workspace to the list. Words like mailbox or workbook, on the other hand, come from email and spreadsheet programs.

What runs under the hood

Lena does not have to install TYPO3. But she should roughly know what it runs on. TYPO3 is a PHP application with a database on a web server. The technical team takes care of the setup.

According to get.typo3.org, TYPO3 14 needs:

  • PHP in versions 8.2 to 8.5.
  • As a database, MariaDB from 10.4.3, MySQL from 8.0.17, PostgreSQL from version 10 or SQLite from 3.8.3. Document databases like MongoDB or desktop databases like Microsoft Access are not supported.
  • As a web server, Apache httpd, Nginx, Microsoft IIS or Caddy Server. Plain FTP storage is not enough, because TYPO3 has to run PHP.
  • For the backend, the current versions of Chrome, Edge, Firefox and Safari. Old browsers like Internet Explorer are not supported.

Frontend and backend

The frontend is the public website with layout and content. Visitors see it when they open the library's site in their browser. The backend is the administration interface. That is where Lena maintains pages, content and files. What she saves in the backend, the frontend displays.

By default, you reach the backend by adding the path /typo3 to the domain. For the library, that would be weidenau-library.org followed by typo3. This path is only the default. The administrator can change it. If it does not work, the correct address is in the project documentation, or you ask the administrator. The path is the same for editors and administrators.

Lena corrects the opening hours in the backend. As soon as she has saved and the page is reloaded, visitors see the change. No server restart and no export are needed. TYPO3 automatically clears the cache of the changed page when you save. If the browser still shows the old text, it is usually the browser cache holding on to the old version. You will see below how to get around it.

The library has a members area where readers can see their loans. Anyone who logs in there is a website user, also called a frontend user. Website users log in on the website, not in the backend. They have no access to the backend, see no page tree and do not edit content elements.

Lena and Tom, on the other hand, are backend users. They work in the administration interface. Website users and backend users are separate records with separate groups. That is why a protected members area belongs to the frontend, even though you have to log in.

One special case is the page type Backend User Section. The frontend only shows such a page if someone is logged into the backend at the same time. A folder, by contrast, never appears in the frontend. A menu separator only structures menus.

Logging in, working, logging out

The backend is a web application. It needs a current browser with JavaScript and cookies. If JavaScript is switched off, even the login fails.

If Lena cannot log in, she first checks two things:

  • Is JavaScript enabled in the browser?
  • Are her username and password correct, and is the account valid?

Besides that, the backend might be in maintenance mode. Or logging in may be blocked for a while after too many failed attempts. By default, TYPO3 allows five failed attempts within 15 minutes from the same IP address.

Once you are logged in, the session lasts for up to eight hours without activity. The default value is 28800 seconds. Only then does TYPO3 log you out automatically. Still, at the end of the day you log out through the user menu in the top bar, so that nobody can misuse your device.

Four roles in TYPO3

In a CMS project, people work in different roles. TYPO3 has established four core roles, and each has an official certification:

  • The editor maintains pages, content elements, media and translations in the backend. The certification is called TCCE, TYPO3 CMS Certified Editor.
  • The integrator implements templates and backend layouts, configures extensions and sets permissions for backend users. The certification is called TCCI.
  • The developer knows the architecture of TYPO3 and programs custom extensions in PHP. The certification is called TCCD.
  • The consultant advises clients, clarifies requirements and accompanies projects, for example as project manager or product owner. The certification is called TCCC.
Four roles, four certifications Editor Pages, content, media, translations TCCE Integrator Builds templates, grants permissions TCCI Developer Programs extensions in PHP TCCD Consultant Advises clients, leads projects TCCC Missing a permission, module or element type? Ask the administrator or integrator
Four roles, four certifications. One person can hold several roles.

One person can hold several roles at the same time. Tom, for example, is administrator and integrator in one.

In the backend there are no built-in roles. No user has to be assigned to exactly one role, and nobody picks a role in the user settings. Instead, the administrator creates backend user groups, for example Editorial team. He gives the group the permissions it needs. Users receive the permissions of their groups. That is how a role is set up technically.

Which modules Lena sees depends on her permissions. She cannot unlock permissions for herself. So the rules are:

  • If a module, a field or a permission is missing, Lena asks the administrator who grants the permissions. At the library, that is Tom.
  • If she needs a new type of content element, she turns to the integrator. Integrators or developers define new element types, often in the site package. Which elements Lena sees in the wizard also depends on her permissions.
  • If the website should get a new language, an administrator first has to set it up in the site configuration. That happens in the Setup module under Sites and requires administrator permissions. Only then can the editorial team translate pages into that language.
  1. After an update, an error message appears when saving a content element.
  2. Lena notes the time, the exact message and the URL from the address bar.
  3. She sends these details to the integrator or the programmer.
  4. She does not delete the element and does not keep saving again and again. Fixing it is not part of her role.

Getting around safely in the browser

The browser is the central program for viewing websites and for using web applications like TYPO3. A few basics save a lot of trouble.

You type the address of a website, the URL, into the address bar. The browser then loads the page directly. The search field of a website, by contrast, only searches that site's own content.

A URL consists of several parts. Take this address of the library:

https://weidenau-library.org/events?page=2#c12
Example address. Scheme https, host weidenau-library.org, path events, query page equals 2 and fragment c12.
The parts of a URL https:// Scheme secure connection weidenau-library.org Host name of the site /events Path requested page ?page=2 Query parameter: page 2 #c12 Fragment jump to the element
The five parts of a URL.

The fragment after the hash sign points to an anchor in the document. It does not filter anything, does not choose a language and does not set a page ID. If you link directly to a content element in TYPO3, you get such a link with an anchor. The browser then jumps straight to that element.

The s in https stands for secure. Data between the browser and the website is transferred encrypted. The browser usually shows this with a padlock icon next to the address. With plain http, data travels across the network as plain text. Many browsers then warn you about typing into form fields.

Forms are the way you work with a web application. When you click Submit, the browser sends the data you entered to the web server. The server processes it. At its core, the TYPO3 backend is made of such forms too. Your input only reaches the server when you save.

Lena has saved the opening hours, but the browser still shows the old ones. This is usually down to the browser cache. Two steps help first:

  • On Windows and Linux, Ctrl plus F5 reloads the page and bypasses the browser cache. F5 alone just reloads. On macOS, use Cmd plus Option plus R. Cmd plus R alone also just reloads.
  • A private window, also called an incognito window, starts without browser cache and without cookies. You see the page like a new visitor.

A private window does not clear the TYPO3 page cache on the server, though. It does not show hidden content and does not publish anything. If neither step helps, the TYPO3 page cache may be the cause.

Watch out for similar keys. Alt plus F4 closes the window on Windows. Ctrl plus D creates a bookmark, and Ctrl plus P prints. On macOS, Cmd plus Q quits the program.

Key points

  • A CMS builds pages from stored content and central templates. A new design does not change the content.
  • TYPO3 is an open source enterprise CMS under the GPL, with no license fee, even for commercial use. Extensions add features.
  • TYPO3 14 needs PHP 8.2 to 8.5, a database such as MariaDB, MySQL, PostgreSQL or SQLite, and a current browser with JavaScript.
  • The frontend is the website, and the backend is the administration interface under the default path typo3. Website users and backend users are separate.
  • The backend session ends after eight hours without activity. The browser's back button discards unsaved changes.
  • Four roles with certification: editor, integrator, developer and consultant. In the backend, roles are built with groups.
  • If a permission, a module or a language is missing, the administrator helps. The integrator builds new element types.
  • Passwords only with https. If you see an old version, reload without cache or use a private window.

Terms

CMS
Software that lets several people create, organize and edit content together.
Template
Centrally maintained layout that presents the content of all pages consistently.
GPL
Free license that allows reading, copying, distributing and changing the code.
Extension
Package that adds features to TYPO3.
Plugin
Content element of an extension that shows its feature on a page.
Frontend
The public website that visitors see.
Backend
The administration interface where editors maintain pages and content.
Website user
Person who logs in on the website and has no access to the backend.
Backend user group
Group with permissions that TYPO3 uses to represent roles.
Fragment
Part of a URL after the hash sign that jumps to an anchor on the page.
Browser cache
Storage in the browser that can show old versions of a page.

As of: November 17, 2026 (TYPO3 14.3 LTS)

Sources:

  • Learning objectives TYPO3 CMS Certified Editor 14 LTS, areas About a CMS, About TYPO3, Frontend and backend, Roles in TYPO3 and Basic usage of a browser
  • TYPO3 Editors Guide 14.3 and TYPO3 Getting Started 14.3, chapter Concepts (docs.typo3.org)
  • get.typo3.org, system requirements TYPO3 14, and typo3.com, certifications
  • Source code TYPO3 14.3 (typo3/cms-core, typo3/cms-backend, typo3/cms-install), checked for session length, page types, module names and database versions

This study guide was written with AI and checked against the sources.

Certifications & exams

Which exam comes next?

You can already practise for 51 exams, and 16 are up for a vote. See all certifications with their official information, cast your vote or suggest your exam.

See all certifications