All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

TYPO3 Neos Components

From TYPO3Wiki
Jump to: navigation, search
This page belongs to the TYPO3 Neos-Development (category Neos development team)


This page is used for further brainstorming and planning for the TYPO3 5.0 components. Please add your ideas and comments where they fit and join the discussion in the TYPO3 5.0 Development newsgroup.

Categorization of components

Generally, every part of TYPO3 5.0 is implemented as a component. The only exception will likey be the component manager. In the overal architecture components do their work on different levels and can be categorized as follow:

  • Core components ("the core") The core components form the essential part TYPO3 - without them the whole system wouldn't work or wouldn't make sense to be used. Core components are transparent to the user.
  • Library components ("libraries") While core components are required, most of the libraries are optional, depending on how TYPO3 is used. They add important functionality the system and usually don't produce frontend output.
  • Plugin components ("plugins") This type of components is the most visible for users of TYPO3 and visitors of the website. Traditionally this functionality has been implemented as frontend plugins

Core components

  • Testing Framework
  • Configuration (TypoScript)
  • Content Repository (TCR)
    • "Rights", "Sessions", "Versioning", "Workspaces" and DBAL are parts of their own but highly depend or even form the content repository
  • L10N / I18N

Libary components

  • Transformation (template engine API, ...)
  • Asset Management
  • Workflow / BPM
  • Synchronisation
  • Help System
  • Media Manipulation
  • Content Analysis

Plugin components

  • Task Manager
  • Shop System
  • Calendar
  • Blog
  • Image gallery
  • News System
  • ...

External project references

  • ZEND Framework:
  • eZ Components Framework from eZ Systems, providing: Authentification (soon), Cache, ConsoleTools, Database-abstraction, RSS-Feed, Graph, ImageAnalysis, ImageConversion, Mail, PersistentObject, SignalSlot, Template, Translation
  • Phing: Build system written in PHP inspired by ANT, good base for general automatic tasks (class generation,...)
  • Propel: Object relational mapper for PHP5, model is stored as XML, generates the model classes with build system phing
  • Creole: Service Layer for Propel, can do reverse engineering too