TYPO3 CMS 7 backend
|Original author(s)||Kasper Skårhøj|
8.7.8 / 2017-04-04
|Available in||51 languages|
|Type||Content management framework, Content management system|
|License||GNU General Public License|
TYPO3 is a free and open source web content management system written in PHP. It is released under the GNU General Public License. It can run on several web servers, such as Apache or IIS, on top of many operating systems, among them Linux, Microsoft Windows, FreeBSD, macOS and OS/2.
TYPO3 is, along with Drupal, Joomla! and WordPress, among the most popular content management systems worldwide, however it is more widespread in Europe than in other regions. The biggest market share can be found in German-speaking countries.
TYPO3 is credited to be highly flexible, as here you can code and content are operated separately. It can be extended by new functions without writing any program code. Also, the software is available in more than 50 languages and has a built-in localization system, therefore supports publishing content in multiple languages. Due to its features like editorial workplace and workflow, advanced frontend editing, scalability and maturity, TYPO3 is used to build and manage websites of different types and size ranges, from small sites for individuals or nonprofit organizations to multilingual enterprise solutions for large corporations. According to the ability to support a corporate environment, it classifies itself as an enterprise level content management system.
TYPO3 was initially authored by the Dane Kasper Skårhøj in 1997. It is now developed by over 300 contributors under the lead of Benjamin Mack (Core team leader) and Mathias Schreiber (Product Owner).
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 by February 2017.
Delivered with a base set of interfaces, functions and modules, TYPO3's functionality spectrum is implemented by 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.
Since version 4.5, TYPO3 is published with a demo website called "Introduction Package". It enables first-time users to get an working example website quickly and to experiment with built-in features. The package can be enabled from the install tool.
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 CMSes, 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 additional 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 backends' page tree. Standard pages serve as "containers" for one or multiple content elements. There are several additional special page types:
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.
Designing and developing with TYPO3 is commonly based on the following elements, among others:
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 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.
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.
Examples for popular extensions:
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, MVC-based development framework. To ensure backwards compatibility, both libraries can be used in the same TYPO3 installation. Extbase itself is a backport of some features of FLOW3, a general web application framework.
As it classifies as an enterprise CMS, many global companies and organisations base their web or intranet sites on TYPO3. The majority is based in german-speaking countries, such as the state of Saxony-Anhalt, the german Green Party, the University of Lucerne (Switzerland), the University of Vienna (Austria) and the Technical University of Berlin. International organisations running one or more TYPO3 sites are: Airbus, Konica-Minolta, Leica Microsystems, Air France, Greenpeace and Meda (Sweden).
|Legend:||Old version||Older version, still supported||Current stable version||Latest preview version||Future release|
|Branch||Version ||Release date||Major changes|
|Old version, no longer supported: 3.0||2001||
|Old version, no longer supported: 3.2||May 2002||
|Old version, no longer supported: 3.3||3 June 2002|
|Old version, no longer supported: 3.5||18 February 2003||
|Old version, no longer supported: 3.6||30 April 2004|
|Old version, no longer supported: 3.7||24 September 2004||
|Old version, no longer supported: 3.8||23 May 2005|
|Old version, no longer supported: 3.8.1||14 November 2005||
|4.x||Old version, no longer supported: 4.0||7 April 2006|
|Old version, no longer supported: 4.1||6 March 2007|
|Old version, no longer supported: 4.2||24 May 2008||
|Old version, no longer supported: 4.3||30 November 2009|
|Old version, no longer supported: 4.4||22 June 2010|
|Old version, no longer supported: 4.5 LTS||26 January 2011||
|Old version, no longer supported: 4.6||25 October 2011|
|Old version, no longer supported: 4.7||24 April 2012|
|6.x||Old version, no longer supported: 6.0||27 November 2012|
|Old version, no longer supported: 6.1||30 April 2013|
|Old version, no longer supported: 6.2 LTS||25 March 2014||
|7.x||Old version, no longer supported: 7.0||02. December 2014||
|Old version, no longer supported: 7.4||04. August 2015||
|Old version, no longer supported: 7.5||29. September 2015||
|Older version, yet still supported: 7.6 LTS||10. November 2015||
|8.x||Old version, no longer supported: 8.0||March 2016||
|Old version, no longer supported: 8.1||3. May 2016||
|Old version, no longer supported: 8.2||05. July 2016||
|Old version, no longer supported: 8.3||30. August 2016||
|Old version, no longer supported: 8.4||18. October 2016||
|Old version, no longer supported: 8.5||20. December 2016||
|Old version, no longer supported: 8.6||14. February 2017||
|Current stable version: 8.7 LTS||04. April 2017||
|9.x||Current stable version: 9.0||12. December 2017||
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, it along with various other packages then served as the basis for the start of development of project Phoenix.
In September 2012, the TYPO3 developers decided on the name for the new product, "TYPO3 Neos". With TYPO3 Neos 1.0 alpha1, a public test version was released in late 2012. 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. 
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
Manage research, learning and skills at defaultLogic. Create an account using LinkedIn or facebook to manage and organize your Digital Marketing and Technology knowledge. defaultLogic works like a shopping cart for information -- helping you to save, discuss and share.