Study guide · TYPO3, CMS and Ecosystem
Explaining TYPO3: CMS, roles and who stands behind TYPO3
As a consultant you do not need to program TYPO3. But you do need to explain it correctly: what a CMS does, what makes TYPO3 special, who does what in a project and who stands behind TYPO3. This page walks you through a first meeting with a client. Afterwards you can answer the typical basic questions with confidence, from the license to the trademark.
The first meeting
Our example is Lake Valley Holidays, a regional tourism association. Its website comes in German, English and French. On top of that there is a second website for the guest card, the "Lake Valley Card". The old system is outdated, and an agency is pitching TYPO3 14 LTS.
The agency's consultant is called Lena. In the first meeting she sits with the association's management and marketing team. They ask questions that almost every client asks:
- What does the license cost?
- Will we have to enter all our texts again at the next relaunch?
- Who stands behind TYPO3, and will it still be around in ten years?
- May the agency use "TYPO3" in its advertising?
Lena answers them one by one. This page follows the same order.
What a CMS does
A content management system, or CMS for short, is software that lets several people create, organize and edit content together. Mostly this is about websites. The editorial team works in the browser through forms and needs no HTML skills. A program that stores HTML files on your own computer is not a CMS. A database server without a user interface or a graphics program also covers only a small part.
The core idea is the separation of content and design. Texts, images and metadata are stored in a structured way as records in a database. Templates and CSS decide how they look. In TYPO3 these are Fluid templates and the site package. If a text changes, the design stays. If the design changes, the texts stay.
Typical features of a CMS are:
- Permission management for users and groups, so that everyone only sees and changes what belongs to their job.
- Versioning, that is a history that lets you trace changes and undo them.
- The separation of content and layout through templates.
- On top of that there are often approval workflows, multiple languages, a recycle bin and reuse of content.
What a CMS does not do: it does not write content by itself, and the server hardware is a job for hosting.
What makes TYPO3 special
TYPO3 is an open source enterprise CMS. It comes with many features out of the box and can be extended with extensions. TYPO3 is written in PHP, not in Java, Python or Ruby.
The license is the GNU General Public License, or GPL for short. Everyone may read, copy, share and change the source code. There is no license fee, not even through the TYPO3 GmbH. That answers the client's first question. Costs arise for implementation, hosting, maintenance and, if you want it, commercial support.
"Enterprise" here means large, multilingual websites, many editors, a fine-grained permission concept and several websites in one installation. That fits Lake Valley with three languages and two websites.
Every client should know two terms:
- The backend is the protected administration interface. This is where editors maintain pages, content and records.
- The frontend is the website that visitors see.
Other terms come up all the time in a project. The page tree organizes all pages of a website. A content element is a building block on a page, such as text with an image. A site is a website with its own domain and its own languages. A site package contains templates and configuration for the look. The Install Tool is for system configuration and is not meant for editors.
The official documentation lives at docs.typo3.org, with a version for each release, for example 14.3. Do not confuse it with other addresses: extensions.typo3.org is the extension repository, or TER for short. packagist.org is the directory for Composer packages. forge.typo3.org is the bug tracker.
What the server needs
Lake Valley's IT wants to know whether the existing server is good enough. TYPO3 basically needs three things: a web server, PHP and a supported database system. It does not need a Java environment. Also, TYPO3 does not deliver static HTML files. It builds the pages with PHP.
- Web server: Apache, NGINX or Microsoft IIS, the latter only on Windows. For Apache, TYPO3 ships a file called .htaccess with rules. For NGINX and IIS you put these rules into the server configuration.
- PHP: TYPO3 14 runs on PHP 8.2 to 8.5. TYPO3 12 still ran on PHP 8.1 to 8.4.
- Database: MySQL from 8.0.17, MariaDB from 10.4.3, PostgreSQL from 10 or SQLite from 3.8.3. For MySQL and MariaDB the InnoDB storage engine must be available.
- PHP extensions: Among others, intl, mbstring and sodium are required.
- Composer: If you install TYPO3 with Composer, you need Composer version 2.1 or later.
- Image processing: For cropping, scaling and thumbnails TYPO3 recommends GraphicsMagick 1.3 or later or ImageMagick 6 or later. The PHP extension gd is used as well. None of them is required for the installation itself.
For the php.ini file, the system requirements recommend a memory_limit of 256M, a max_execution_time of 240 and max_input_vars of 1500. 256M is also the lower limit. Below that, the Install Tool reports an error, and for larger installations it even suggests 512M. Values that are too small cause aborts, for example during image processing or in the Install Tool. TYPO3 runs on Linux, macOS and Windows.
The four roles in a project
In a CMS, everyone who works with it has one or more roles. TYPO3 has four core roles, and each of them has an official certification.
- The editor creates and maintains pages and content elements in the backend. The certification is called TYPO3 CMS Certified Editor, or TCCE for short.
- The integrator builds the site with the tools TYPO3 already offers. Integrators set up templates and the site configuration, write TypoScript and TSconfig and configure users, groups and access rights. The certification is called TCCI.
- The developer programs custom extensions, for example with Extbase. The certification is called TCCD.
- The consultant gives advice. The certification is called TCCC and is aimed at consultants, project managers and product owners. It tests knowledge about the possibilities, limits, operation and environment of TYPO3, not programming.
What belongs to Lena's tasks as a consultant? She gathers and evaluates requirements with the client. She judges whether a requirement can be solved with core features or with an extension. And she advises on hosting, maintenance and the life cycle of the TYPO3 version. She does not build the menu in TypoScript. That is the integrator's job. She does not program an extension either. That is the developer's job. Lena has to know the possibilities, but she does not implement them technically herself.
An important learning goal is: know whom to ask. For topics outside your own role, you turn to the role in charge.
The certifications are offered by the TYPO3 GmbH. They confirm the knowledge of individual people. Agencies cannot issue their own official TYPO3 certificates, and neither can the Security Team or universities.
Who stands behind TYPO3: the Association
Lake Valley's management asks whether TYPO3 will still exist in ten years. To answer, Lena explains who stands behind the project. There are three levels: the Association, the GmbH and the community.
The TYPO3 Association is a non-profit organization. It was founded in 2004 and is based in Switzerland. It is the legal body behind the TYPO3 project. Its tasks are:
- It holds the TYPO3 trademark and manages the licensing under the GPL.
- It funds core development and community projects, with around 650,000 euros a year.
- It provides infrastructure and guidance for the community and supports events.
The Association is mainly funded through membership fees, donations and events. There are no license fees for GPL software. There is no advertising in the backend either, and taxes from the European Union are not a source of funding.
The Association is a membership organization with around 1,100 members. At the annual members' meeting, the General Assembly, they elect the board. The board makes strategic decisions. The day-to-day work is done by teams and committees.
Becoming a member
Both individuals and organizations can become members of the Association. Membership supports the project. But it is not a requirement for using TYPO3 commercially, because the GPL allows that to everyone. Everyone gets the source code too, not just members.
The regular membership levels are Community, Bronze, Silver, Gold and Platinum. Community is the entry level for individuals, and Platinum is meant for companies that offer almost only TYPO3 services or save a lot through TYPO3. Levels such as Diamond or Enterprise Plus do not exist.
In addition there are sector memberships for universities, called Academic, for non-profit organizations, called NGO, for public administrations, called Public Sector, and for Industry and E-Commerce. Each comes in Bronze, Silver and Gold variants. A minimum number of certified employees or an own data center is not required.
What do members get?
- Every member has one vote at the General Assembly, regardless of the level. Higher levels bring more benefits, but not more votes.
- Members get discounts, for example on events and certifications. The certifications are not free, though.
- Current members may show the membership badge of their level, as long as their fees are paid.
- For Extended Long Term Support there are tiered discounts: Silver 25 percent, Gold 30 percent, Platinum 45 percent.
Lake Valley itself could become a member too, for example in the public sector category. That way Lake Valley helps secure the future of the system it relies on.
The TYPO3 GmbH and the partner program
The TYPO3 GmbH was founded by the Association in 2016. It is a wholly owned subsidiary of the Association and its commercial arm. So it is neither the parent company nor a competitor of the Association. Its services are:
- Extended Long Term Support, or ELTS for short, for older TYPO3 versions.
- Certification programs for TYPO3 professionals.
- Service level agreements, or SLAs for short, independent project reviews and mediation.
- The partner program, presales support and marketing for the CMS.
- According to the learning objectives catalog, the big events TYPO3 Developer Days and TYPO3 Conference, or T3CON for short. The Association is involved as well.
The GmbH does not sell usage licenses. It does not approve extensions in the TER either.
The TYPO3 Partner Program is one of the GmbH's services. It has three partner types:
- Consultant Partners are freelancers, TYPO3 consultants and development agencies without their own end-client focus. A freelancer who only advises agencies fits here.
- Solution Partners are classic TYPO3 agencies and service providers with end clients.
- Technology Partners are TYPO3 hosting providers and integration partners that connect technology with TYPO3.
There is no "Premium Hosting Partner" or "Community Partner". Universities go through the Academic membership of the Association.
Partners get additional discounts of up to 45 percent on services of the GmbH. They become visible as experts on typo3.com and receive referred leads. They take part in regular roundtables, for example on security, product strategy and development. And they get access to the fourth ELTS year. ELTS extends support for a version by up to three years for every client. The fourth year is reserved for partners, and even Platinum members do not get it. Partners have no say in which patches go into the core. That is decided by the open review process. There is no early access to the source code either, because it is public anyway.
The community: taking part and finding help
The TYPO3 community includes everyone who uses or develops TYPO3: editors, integrators, developers and agencies. Everyone is invited to take part. You do not need a membership, a certification or a job at the GmbH. You can contribute with code, documentation, translations, testing, marketing or by organizing events.
The community itself organizes TYPO3Camps and the regular meetings of local user groups. The work is shared among teams, for example the Documentation Team, the Marketing Team and the Strategic Initiatives. The Documentation Team maintains the official documentation at docs.typo3.org and the tools used to render it. Anyone can submit improvements through the "Edit on GitHub" link. The Documentation Team does not translate the backend, and it does not review extensions.
How people treat each other is set out in the TYPO3 Code of Conduct. It describes respectful behavior at events, in Slack and elsewhere.
Every concern has its right place:
- Questions and exchange: The TYPO3 Slack at typo3.slack.com has channels for questions, teams and topics. People often help each other quickly there. There is also Discord.
- Stack Overflow is the place for concrete questions and answers about using and developing TYPO3, under the tag "typo3". This builds a searchable knowledge base.
- Bugs and feature requests for the core and the system extensions go into the bug tracker Forge at forge.typo3.org.
- Security issues are never reported in public, not even in Forge. They go confidentially to the TYPO3 Security Team at security@typo3.org.
- News: You can subscribe to the read-only mailing list TYPO3 Announce. It announces releases and security bulletins, with only a few emails a month. The details are in the security advisories on typo3.org under security. On top of that there are news.typo3.com and social media.
The core is not an extension in the TER. So you will not find new core versions there.
The TYPO3 trademark
The word "TYPO3" is a registered trademark of the TYPO3 Association. It belongs neither to the GmbH, nor to TYPO3's inventor Kasper Skårhøj, nor to every user. The GPL only covers the source code, not the name. How the name may be used is defined in the Trademark Usage Policy.
Allowed is descriptive use, without permission and for everyone. Sentences like "We offer TYPO3 development services" or "The website is built with TYPO3" are factual and allowed. You may also mention a TYPO3 certification you have actually earned, for example in your CV, as long as it is valid. You just must not give the impression of an official partnership.
Not allowed is the wordmark as part of a name. This applies to everyone, including members:
- Company names such as "TYPO3 Solutions Ltd.".
- Product names such as "TYPO3 Builder".
- Domain names such as typo3hosting.com.
- Social media names such as "TYPO3Experts".
Paid advertising with the wordmark, for example on Google Ads, Facebook Ads or LinkedIn, is only allowed for Gold and Platinum members. Non-members and members below Gold may not do it. Certified employees do not change this. If you plan a use that the policy does not allow, you can register as a trademark user and apply for permission. The Association then decides case by case.
Two more things are forbidden for everyone. Nobody may, without explicit permission, give the impression of being an official partner or of being endorsed or certified by the Association. And nobody may use the trademark in a disparaging or defamatory way.
Key points
- A CMS separates content and design. That is why content survives a relaunch, and only changed structures need a migration.
- TYPO3 is an open source enterprise CMS written in PHP under the GPL, without license fees. The documentation is at docs.typo3.org.
- TYPO3 14 needs a web server, PHP 8.2 to 8.5 and MySQL, MariaDB, PostgreSQL or SQLite. Oracle and Microsoft SQL Server are not supported.
- There are four core roles with certifications: editor, integrator, developer and consultant. The certifications are offered by the TYPO3 GmbH.
- The Association is the non-profit body in Switzerland, founded in 2004. It holds the trademark and funds core and community.
- Every member has one vote at the General Assembly, regardless of the level.
- The GmbH is the wholly owned subsidiary of the Association. It offers ELTS, certifications, SLAs and the partner program and does not compete with agencies.
- Questions go to Slack or Stack Overflow, bugs go to Forge, and security issues go confidentially to the Security Team.
- "TYPO3" is off limits in company, product, domain and social media names. Only Gold and Platinum members may run paid ads with it.
Terms
- CMS
- Software that lets several people create and maintain content together, separate from the design.
- Backend
- The protected administration interface of TYPO3 where editors work.
- Frontend
- The website that visitors see.
- GPL
- GNU General Public License, the free license of TYPO3.
- ELTS
- Extended Long Term Support, a paid extension of support for a version through the TYPO3 GmbH.
- TYPO3 Association
- Non-profit association, the body behind the project and owner of the trademark.
- TYPO3 GmbH
- Wholly owned subsidiary of the Association for commercial services.
- General Assembly
- Annual members' meeting of the Association, which elects the board.
- Forge
- Bug tracker for bugs and feature requests in the core.
- TYPO3 Announce
- Read-only mailing list for releases and security bulletins.
- Trademark Usage Policy
- Guideline on how the name TYPO3 may be used.