TYPO3 Development
This is the developer's corner of the TYPO3 project. If you would like to help developing TYPO3 or contribute to our big repository of extensions, the following information will give you an idea of how to get started.
The development of the TYPO3 core and its system extensions (ie. extension which are released together with the core) is planned by the R&D Committee (see below) and published in our roadmap.
Getting started
If you would like to develop with and for TYPO3, you'll start by discovering TYPO3 from a user's and site developers point of view. Make sure you have read and tried the different tutorials in the Documentation section. If that made you hungry for more, you should try developing your first extension.
Development teams
Developing extensions is the best way getting to know the internals of TYPO3. If you already passed that line and would like to contribute to the TYPO3 core, we're glad to welcome you in one of our development teams listed below or on the many projects now active for the upcoming TYPO3 version 4.6.
- The Core Team develops and maintains the TYPO3 4.X core. Only members of this team have write access to the SVN repository.
- The 5.0 Team shapes the future of TYPO3 by transferring and extending the current concepts to a future-proof platform.
- In the Bug Fixing section, you will find information about the way the core team fixes issues in the TYPO3 bug tracker.
Mailing lists
The main list about developing TYPO3 (not developing sites with TYPO3!) is typo3-dev. Post to this list to discuss development related ideas, questions and suggestions.
For other mailing lists please have a look at the different team pages.
Documentation
- The most important documents for core developers are the "Project Coding Guidelines", "TYPO3 Core APIs", and "Inside TYPO3". You find them in the documentation section.
- After each release we create an overview of the core API with Doxgen.
- Interesting information about special development topics can also be found in our articles.
Comments, suggestions? Please write to Robert Lemke
