Typo3

TYPO3

TYPO3 is a Web Content management system (CMS) written in the programming language PHP. It can run on a variety of web servers, such as Apache, Nginx, or Internet Information Services (IIS), and on many operating systems, including Linux, Microsoft Windows, FreeBSD, macOS, and OS/2. It is free and open-source software released under the GNU General Public License version 2.

Quick Facts Original author(s), Developer(s) ...

TYPO3 is similar to other popular content management systems such as, Drupal, Joomla! and WordPress. It is used more widely in Europe than in other regions, with larger market share in German-speaking countries, the Netherlands and France.[2][3]

TYPO3 is credited to be highly flexible, as code and content are run separately.[citation needed] It can be extended by new functions without writing any program code. TYPO3 supports publishing content in multiple languages due to its built-in localization system. Due to its features like editorial workplace and workflow, advanced frontend editing, scalability and maturity, TYPO3 makers classify it as an enterprise level content management system.[4][5]

History and usage

TYPO3 was initially authored by the Dane Kasper Skårhøj in 1997.[6] It is now developed by over 300 contributors under the lead of Benjamin Mack (Core team leader).[7]

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][8]

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.[9]

TYPO3 can run on most HTTP servers such as Apache, Nginx or IIS on top of Linux, Microsoft Windows or macOS. It uses PHP 7.2 or newer[10] and any relational database supported by the TYPO3 DBAL including MySQL/MariaDB, PostgreSQL, and SQLite.[11] 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.

Building basic proficiency in TYPO3 needs between a few weeks up to some months. For an author or editor who administers and operates a TYPO3 based website, this requirement can range from a few minutes to a few hours. A developer setting up a website with TYPO3 would need to work intensively with the meta-language Typoscript.[12]

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 backends' 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 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.[13]

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.[9]

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.[14]

Notable projects

As it classifies as an enterprise CMS, many global companies and organizations base their web or intranet sites on TYPO3. The majority are 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 organizations running one or more TYPO3 sites are: Airbus, Konica-Minolta, Leica Microsystems, Air France, Greenpeace, and Meda (Sweden).[15][16][17]

Releases

Version history

More information Legend: ...
More information Branch, Version ...

Neos

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.[77]

In September 2012, the TYPO3 developers decided on the name for the new product, "TYPO3 Neos".[78] With TYPO3 Neos 1.0 alpha1, a public test version was released in late 2012.[79][80] 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.[81]

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.[82]

See also


References

  1. "List of Releases for TYPO3 v12". Retrieved 25 April 2023.
  2. "TYPO3". cmscrawler.com.
  3. "TYPO3 - The Enterprise CMS". Archived from the original on 2013-04-16. Retrieved 2012-04-10.
  4. Hinderink e.a., Werner Altmann; René Fritz; Daniel (2005). TYPO3: enterprise content management (1. ed.). Birmingham [u.a.]: Packt Publ. ISBN 1-904811-41-8.{{cite book}}: CS1 maint: multiple names: authors list (link)
  5. "The History of TYPO3". Archived from the original on 2012-04-06. Retrieved 2012-04-11.
  6. "TYPO3 in numbers". TYPO3 - The Enterprise Open Source CMS. Archived from the original on 2012-04-04.
  7. "Extension Repository". TYPO3 - The Enterprise Open Source CMS. Archived from the original on 2004-04-29.
  8. Böhm, Julian (25 June 2020). "What Versions of TYPO3 Run on Which Versions of PHP?". TYPO3 Blog.
  9. "Download TYPO3 - get.typo3.org". get.typo3.org. Retrieved 2020-12-02.
  10. "What are extensions?". TYPO3 - The Enterprise Open Source CMS.
  11. "TYPO3 case studies". typo3.org. Retrieved 9 February 2017.
  12. "Recently added sites". TYPO3 Reference Blog. Retrieved 9 February 2017.
  13. "Case studies". typo3.com.
  14. http://typo3.org/download/ Information on support cycles of TYPO3 versions
  15. "Installation manual for TYPO3 3.0" (PDF). Archived from the original (PDF) on 2014-04-07. Retrieved 2012-07-31.
  16. "Installation manual for TYPO3 3.0 w/ Screenshots of version 3.2" (PDF). Archived from the original (PDF) on 2014-04-07. Retrieved 2012-07-31.
  17. "TYPO3". sourceforge.net.
  18. "Source code of all newer versions with release dates". Archived from the original on 2014-07-09. Retrieved 2013-11-22.
  19. Bager, Jo (3 May 2004). "Typo3 3.6.0 fertig gestellt". heise online.
  20. "release notes for TYPO3 3.8.1". Archived from the original on 2012-07-24. Retrieved 2012-07-31.
  21. "TYPO3 4.0". typo3.org.
  22. "TYPO3 4.1". typo3.org.
  23. "TYPO3 4.2". typo3.org.
  24. "release notes for TYPO3 4.3". Archived from the original on 2012-04-06. Retrieved 2012-07-31.
  25. "release notes for TYPO3 4.4". Archived from the original on 2012-04-06. Retrieved 2012-07-31.
  26. t3n Redaktion. "TYPO3 4.4: TYPO3 wird einsteigerfreundlicher, schöner, schneller – Hier die wichtigsten Neuerungen". t3n Magazin (in German). Archived from the original on 2016-08-18. Retrieved 2012-07-31.{{cite web}}: CS1 maint: numeric names: authors list (link)
  27. "TYPO3 Roadmap". Archived from the original on 2012-10-25.
  28. "Download". TYPO3 - The Enterprise Open Source CMS.
  29. Ernesto Baschny (2 October 2010). "TYPO3 4.5 LTS Status Report T3CON10". slideshare.net.
  30. Ernesto Baschny (3 July 2010). "TYPO3 4.5 Kick-Off Presentation #t3dd10". slideshare.net.
  31. TYPO3 4.6 release date rec. 6. October 2012
  32. "Login". TYPO3 - The Enterprise Open Source CMS.
  33. "Welcome to nginx". Archived from the original on 2012-07-20. Retrieved 2012-07-31.
  34. "Development Report: File Abstraction Layer". TYPO3 - The Enterprise Open Source CMS. 28 February 2012.
  35. "TYPO3 6.0 - Back to the Future". TYPO3 - The Enterprise Open Source CMS. 14 May 2012.
  36. "New release plan for 6.2 LTS". 21 November 2013. Retrieved 8 December 2013.
  37. "8.2 Changes". docs.typo3.org. 2016. Archived from the original on February 11, 2017. Retrieved 1 June 2023.
  38. "Releasing TYPO3 v8.4". 18 October 2016.
  39. "TYPO3 v8.5 released". 20 December 2016.
  40. Dambekalns, Karsten (10 October 2012). "TYPO3 Neos and Flow - September 2012". TYPO3 Association. Retrieved 12 October 2012.
  41. "TYPO3 Neos Alpha Releases". TYPO3 Association. Retrieved 9 May 2013.
  42. "Change Log Neos 1.0.0 alpha2". TYPO3 Association. Retrieved 9 May 2013.
  43. "Neos 3.0 and Flow 4.0 Released". neos.io. 30 January 2017. Retrieved 9 February 2017.

Further reading

  • Michael Peacock – Building Websites with TYPO3 (Paperback) – ISBN 1-84719-111-8
  • Michael Schams, Patrick Lobacher - TYPO3 Extbase: Modern Extension Development for TYPO3 CMS with Extbase & Fluid (Paberback) - ISBN 1-53053-417-8
  • Rene Fritz, Daniel Hinderink, Werner Altmann – TYPO3: Enterprise Content Management (Paperback) – ISBN 1-904811-41-8

Share this article:

This article uses material from the Wikipedia article Typo3, and is written by contributors. Text is available under a CC BY-SA 4.0 International License; additional terms may apply. Images, videos and audio are available under their respective licenses.