TYPO3 Association
businessWeb Page: http://typo3.org/development/gsoc2011/ideas/
Mailing List: http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
TYPO3 is an enterprise-class Open Source Content Management System built with PHP and has a 10 year development history. Because of its Danish origins the majority of TYPO3’s developer community is situated in Europe and especially in Germany, but TYPO3 is also enjoying a growing popularity in Asia, Africa, and the Americas recently.
There are about 500,000 installations world wide including high profile websites of large companies such as Lufthansa, Volkswagen, T-Online, DHL, 3M, General Electric, and Stanford University and many government sites to name a few.
There are about 500,000 installations world wide including high profile websites of large companies such as Lufthansa, Volkswagen, T-Online, DHL, 3M, General Electric, and Stanford University and many government sites to name a few.
TYPO3 as a CMS is currently undergoing a rewrite from scratch for its upcoming version five in parallel to the further development on TYPO3 v4. As a basis for TYPO3 v5 a new framework (FLOW3) with features like AOP and DI is being built. Based on FLOW3 and also as another base component for TYPO3 v5 a content repository (influenced by JSR-283) is being built in a way that it can be reused by other open source projects.
Highlights of TYPO3’s feature set are its complete separation of content and design, a fine-grained permission system, a WYSIWYG rich text editor, an integrated versioning and workflow system, frontend / in-site editing, integrated search engine, dynamic navigation menu generation, dynamic graphics generation, standards compliant output and single source publishing, multi-language support, advanced caching system with reverse proxy support, and user registration.
In addition an open API enables very versatile options for developing extensions and additional functionality.
The main goal of the TYPO3 Association is to support core development of the TYPO3 Open Source Content Management System on a steadier basis and improve the transparency and efficiency of various aspects of the TYPO3 project.
In addition an open API enables very versatile options for developing extensions and additional functionality.
The main goal of the TYPO3 Association is to support core development of the TYPO3 Open Source Content Management System on a steadier basis and improve the transparency and efficiency of various aspects of the TYPO3 project.
Projects
- FLOW3: data model browsing Create a data model browsing package for FLOW3. The browser allows to view the data of a FLOW3 installation, do CRUD-operations, search and filter it, regardless of it's underlying database.
- Integration of semantic ontologies This project aims at integrating ontologies as a source for data structures. This includes automatic creation of database tables and form descriptions as well as possibilites to share these data structures between installations. The main goal is to ease creation of new data types by reusing existing ontologies, and reducing the number of redundant data types that exist among different extensions (de-coupling of data structures and plugins)
- Static File Caching Code changes will reduce database load by caching pages as static files. The server will load the cache file rather than even looking at the script so as to dramatically increase performance on high traffic sites.
- TYPO3 Transition Tool TYPO3 is right in a big rebuilding phase and will make a huge technical step from version 4 to version 5. Basis of the new version will be the FLOW3 Framework which is just maturing into its beta phase. One of the new concepts is the implementation of a Content Repository (CR) which transparently persists data in form of Nodes in a hierarchical Node-Tree. For making the transition as smooth as possible, there is a need of functionalities to transform TYPO3v4 contents into CR-compatible data.
- User Administration Module The current user administration is done through the list module, and it is very limited because that module handles only the back-end users and groups. My project will come with some improvements on the design, the back-end users and groups administration and also add some missing features such as front-end users and groups administration.