TYPO3 is similar to other content management systems such as Drupal, Joomla!, and WordPress. It is used more widely in Europe than in other regions, with a larger market share in German-speaking countries, the Netherlands, and France.[2][3]
TYPO3 allows for the separate maintenance of code and content. It can be extended with new functions without writing any program code. TYPO3 supports publishing content in multiple languages due to its built-in localization system.
History and usage
TYPO3 was initially authored by the Dane Kasper Skårhøj in 1997.[4] It is now developed by over 300 contributors under the lead of Benjamin Mack.[5]
Calculations from the TYPO3 Association show that it is currently used in more than 500,000 installations. The number of installations detected by the public website "CMS Crawler" was around 384,000 in February 2017.[3][6]
Features
TYPO3 provides a base set of interfaces, functions and modules. Most functionality exceeding the base set can be implemented via the use of extensions. More than 5000 extensions are currently available for TYPO3 for download under the GNU General Public License from a repository called the TYPO3 Extension Repository, or TER.[7]
Compatibility
TYPO3 is able to run on most HTTP servers such as Apache, Nginx or IIS on top of Linux, Microsoft Windows, FreeBSD, macOS, and OS/2. It uses PHP 7.2 or newer[8] and any relational database supported by the TYPO3 DBAL including MySQL/MariaDB, PostgreSQL, and SQLite.[9] Some 3rd-party extensions – not using the database API – support MySQL as the only database engine. The system can be run on any web server with at least 256 MB RAM and a CPU appropriate for that RAM.
The backend can be displayed in any modern browser with JavaScript. There is no browser restriction for displaying user-oriented content generated by TYPO3. A developer setting up a website with TYPO3 would need to work intensively with the Domain-specific language Typoscript.[10]
System architecture
Conceptually, TYPO3 consists of two parts: the frontend, visible to visitors, and the administrative backend. The frontend displays the web content. The backend is responsible for administration and managing content. The core functions of TYPO3 include user privileges and user roles, timed display control of content (show/hide content elements), a search function for static and dynamic content, search-engine friendly URLs, an automatic sitemap, multi-language capability for frontend and backend, and more.
Like most modern CMS's, TYPO3 follows the policy of separation of content and layout: The website content is stored in a relational database, while the page templates are stored on the file system. Therefore, both can be managed and updated separately.
TYPO3 defines various basic types of content data. Standard content elements are described as text, text with media, images, (plain) HTML, video etc. Various added types of content elements can be handled using extensions.
The fundamental content unit is a "page". Pages represent a URL in the frontend and are organized hierarchically in the backend's page tree. Standard pages serve as "containers" for one or multiple content elements. There are several added special page types, including:
shortcuts (they show content from another page)
mount points (that insert a part of the page tree at the mount point)
external URLs
system folders (to handle complex data such as registered users)
Internally, TYPO3 is managed by various PHP arrays. They contain all the information necessary to generate HTML code from the content stored in the database. This is achieved by a unique configuration language called Typoscript.
Design elements
Designing and developing with TYPO3 is commonly based on the following elements, among others:
Page tree
Representation of all pages of a site, their structure and properties.
Constants
System-wide configuration parameters
Template
Since TYPO3 6, the system runs on the templating engine Fluid. Fluid combines HTML markup with conditions and control structures. It can be extended by custom view helpers written in PHP.
Until version 4.3, an HTML skeleton was used, with markers (e.g., ###MARKER###) and range markers, called subparts (e.g., <!--###CONTENT###Start--> … <!--###CONTENT###End-->); that were replaced by various content elements or served as a sub template. This template system can still be found in older extensions or installations.
Typoscript
Typoscript is a purely declarative configuration language. In Typoscript, configuration values are defined, which are parsed into a system-wide PHP array. Typoscript is object-based and organized in a tree-like structure.
Extensions
Added plug-ins to enable more functions. See Extensions.
PHP
TYPO3 CMS is written in PHP. Thus, most features can be modified or extended by experienced users. For example, the XCLASS mechanism allows classes and methods to be overwritten and extended.
Extensions
Extensions are the cornerstone in the internal architecture of TYPO3. A feature that was introduced with version 3.5 in 2003 is the Extension Manager, a control center managing all TYPO3 extensions. The division between the TYPO3 core and the extensions is an important concept which determined the development of TYPO3 in the past years. Extensions[11] are designed in a way so they can supplement the core seamlessly. This means that a TYPO3 system will appear as a unit while actually being composed of the core application and a set of extensions providing various features.[12]
Diagram of the basic TYPO3 system architecture
They can be downloaded from the online repository (TER) directly from the backend, and are installed and updated with a few clicks. Every extension is identified by a unique extension key (for example, tt news). Also, developers can share new or modified extensions by uploading them to the repository.[7]
Generally, extensions are written in PHP. The full command set of PHP 5.3 can be used (regarded the system requirements of the specific TYPO3 version), but TYPO3 also provides several library classes for better efficiency: Best known and most used is the Pibase library class. With introduction of TYPO3 4.3 in 2009, Pibase has been replaced (or extended) by the Extbase library, which is a modern, model–view–controller (MVC) based development framework. To ensure backward compatibility, both libraries can be used in the same TYPO3 installation. Extbase is a backport of some features of FLOW3, renamed Neos Flow, a general web application framework.[13]
As artificial intelligence (AI) continues to shape various industries, it is making a significant impact on content management systems (CMS) like TYPO3. AI integration within TYPO3 offers users the potential to streamline content creation, optimize website performance, and manage data more efficiently. AI can assist in automating routine tasks, such as generating content drafts, enhancing SEO practices, and translating content into multiple languages. Additionally, AI-driven tools like T3AI help improve decision-making by analyzing user behavior and recommending relevant adjustments to enhance site performance and user experience.[18]
Second release with Long Term Support (LTS), until April 2017[35]
File Abstraction Layer (FAL) re-worked
Install Tool re-written and Distribution Management added
Responsive image rendering and mobile device preview
New documentation module added
Enhanced security features
Latest version: 6.2.47
7.x
Old version, no longer maintained: 7.0
2 December 2014
general code cleanup, speed improvements through outsourcing of an old compatibility layer, refresh of the visual appearance of the backend.[59]
Old version, no longer maintained: 7.4
4 August 2015
Backend Overhaul Vol 2
Old version, no longer maintained: 7.5
29 September 2015
general code base improvements, Backend Overhaul Vol 3
Old version, no longer maintained: 7.6 LTS
10 November 2015
Third release with Long Term Support (LTS), support until November 2018[35]
8.x
Old version, no longer maintained: 8.0
22 March 2016
general code cleanup, speed improvements through outsourcing of the old compatibility layer, refresh of the visual appearance of the backend. Usage of performance improvements through PHP7 requirement.[59]
Old version, no longer maintained: 8.1
3 May 2016
Most notable: Doctrine integration, UX rework of workspace module, general cleanup.[60]
Long Term Support Release (LTS), bug fixes for 18 months, security support for 36 months, until March 2020.[65]
9.x
Old version, no longer maintained: 9.0
12 December 2017
First of five sprint releases to 9.x LTS. Refactored Install Tool into System Maintenance Area. New Page Tree user interface. New page translations.[65]
A completely rewritten version (code-named "Phoenix") was originally planned as TYPO3 version 5.0. While working on this new release and analyzing the 10-year history and complexity of TYPO3 v4, the TYPO3 community decided to branch out version 5 as a completely separate product, one that wouldn't replace version 4 in the near future and as such needed to have its own name. Published as FLOW3, now renamed Neos Flow, it along with various other packages then served as the basis for the start of development of project Phoenix.[79]
In September 2012, the TYPO3 developers decided on the name for the new product, "TYPO3 Neos".[80] With TYPO3 Neos 1.0 alpha1, a public test version was released in late 2012.[81][82] In May 2015 the TYPO3 Association and the Neos team decided to go separate ways, with TYPO3 CMS remaining the only CMS product endorsed by the Association and the Neos team publishing Neos as a stand-alone CMS without any connection to the TYPO3 world.[83]
In January 2017, Neos 3.0 has been published, along with a new version of Flow framework and a name change of its configuration language from TypoScript2 to Fusion.[84]
Drupal is a free and open-source web content management system (CMS) written in PHP and distributed under the GNU General Public License. Drupal provides an open-source back-end framework for at least 14% of the top 10,000 websites worldwide and 1.2% of the top 10 million websites—ranging from personal blogs to corporate, political, and government sites. Drupal can also be used for knowledge management and for business collaboration.
Midgard is an open source persistent storage framework. It provides an object-oriented and replicated environment for building data-intensive applications.
Tiki Wiki CMS Groupware or simply Tiki, originally known as TikiWiki, is a free and open source Wiki-based content management system and online office suite written primarily in PHP and distributed under the GNU Lesser General Public License (LGPL-2.1-only) license. In addition to enabling websites and portals on the internet and on intranets and extranets, Tiki contains a number of collaboration features allowing it to operate as a Geospatial Content Management System (GeoCMS) and Groupware web application.
eZ Publish is an open-source enterprise PHP content management system that was developed by the Norwegian company Ibexa. eZ Publish is now maintained by 7x. eZ Publish is freely available under the GNU GPL version 2 license, as well as under proprietary licenses that include commercial support. In 2015, eZ Systems introduced eZ Platform to replace eZ Publish with a more modern and future-proof solution. In 2024, 7x released eZ Publish 6.0 (stable) to replace eZ Publish 5.4 with a more modern and future-proof solution compatible with PHP 7.x and 8.x software. In 2024/02 7x followed up its first release (6.0) with a powerful second release 6.0.1 containing key installation bugfixes and a brand new database backend for flat file database called SQLite that is mature and stable ready to use to simplify your website or web application. In 2024/03 7x continues to develop and release monthly updates to eZ Publish with the release of version 6.0.2 which provides default design improvements and many more extensions enabled for use by default.
A web content management system is a software content management system (CMS) specifically for web content. It provides website authoring, collaboration, and administration tools that help users with little knowledge of web programming languages or markup languages create and manage website content. A WCMS provides the foundation for collaboration, providing users the ability to manage documents and output for multiple author editing and participation. Most systems use a content repository or a database to store page content, metadata, and other information assets the system needs.
Django is a free and open-source, Python-based web framework that runs on a web server. It follows the model–template–views (MTV) architectural pattern. It is maintained by the Django Software Foundation (DSF), an independent organization established in the US as a 501(c)(3) non-profit.
Joomla, also styled Joomla! and sometimes abbreviated as J!, is a free and open-source content management system (CMS) for publishing web content on websites. Web content applications include discussion forums, photo galleries, e-Commerce and user communities, and numerous other web-based applications. Joomla is developed by a community of volunteers supported with the legal, organisational and financial resources of Open Source Matters, Inc.
Content Repository API for Java (JCR) is a specification for a Java platform application programming interface (API) to access content repositories in a uniform manner. The content repositories are used in content management systems to keep the content data and also the metadata used in content management systems (CMS) such as versioning metadata. The specification was developed under the Java Community Process as JSR-170, and as JSR-283. The main Java package is javax.jcr.
Symfony is a free and open-source PHP web application framework and a set of reusable PHP component libraries. It was published as free software on October 18, 2005, and released under the MIT License.
Silverstripe CMS is a free and open source content management system (CMS) and framework for creating and maintaining websites and web applications. It provides an out of the box web-based administration panel that enables users to make modifications to parts of the website, which includes a WYSIWYG website editor. The core of the software is Silverstripe Framework, a PHP Web application framework.
Serendipity is a blog and web-based content management system written in PHP and available under a BSD license. It supports PostgreSQL, MySQL, SQLite database backends, the Smarty template engine, and a plugin architecture for user contributed modifications.
Nuxeo is a software company making an open source content management system.
Flow is a free and open source web application framework written in PHP. The first final version was released on October 20, 2011. It was primarily designed as a basis for the content management system Neos, but can also be used independently. It is generally suitable for PHP development of mid- or large-scaled web applications.
Umbraco is an open-source content management system (CMS) platform for publishing content on the World Wide Web and intranets. It is written in C# and deployed on Microsoft based infrastructure. Since version 4.5, the whole system has been available under an MIT License.
Pimcore is an open-source enterprise PHP software platform for product information management (PIM), master data management (MDM), customer data management (CDP), digital asset management (DAM), content management (CMS), and digital commerce.
ownCloud, a Kiteworks Company, is a free and open-source software project for content collaboration and sharing and syncing of files in distributed and federated enterprise scenarios. It allows companies and remote end-users to organize their documents on servers, computers, and mobile devices and work with them collaboratively while keeping a centrally organized and synchronized state.
ProcessWire is a free and open source content management system (CMS), content management framework (CMF) and web application framework (WAF) written in the PHP programming language. It is distributed under the Mozilla Public License 2.0. ProcessWire is built around an API with usage and naming conventions similar to the JavaScript framework jQuery. The stated goal behind the API is to provide the level of accessibility and control to pages in a website that jQuery provides to the DOM. Content is managed either via the API or the web-based admin control panel. ProcessWire is largely used for development of web sites, web applications, services, content feeds and related applications.
Ibexa DXP is an open-source enterprise PHP content management system (CMS) and Digital eXperience Platform (DXP) developed by the company Ibexa, which has headquarters in Oslo, Norway. The OSS edition of Ibexa DXP is freely available under the GNU GPL version 2 license, while the Headless, Experience and Commerce editions are available under proprietary licenses that include commercial support as well as access to additional features. The commercial versions of the software extend the capabilities of the open-source core with features such as personalization, e-Commerce and additional editorial and development capabilities.
Grav is a free software, self-hosted content management system (CMS) written in the PHP programming language and based on the Symfony web application framework. It uses a flat file database for both backend and frontend.
This page is based on this Wikipedia article Text is available under the CC BY-SA 4.0 license; additional terms may apply. Images, videos and audio are available under their respective licenses.
