TYPO3Development

Writing a book is a huge project. I never believed those people saying “Just double the time of your first estimate”. Now, after the book is finally available I would say they are wrong. You have to increase it threefold.

The book about Extbase and Fluid was written in close collaboration with Sebastian Kurfürst (core developer of Fluid) and Inken Kiupel (reader). We hope that it encourages the developers of TYPO3 extensions to get in touch with the fascinating concepts of FLOW3. And we hope that the book eases the migration to TYPO3 v5 (that’s what Extbase is all about).

We are aware of the fact that many of the English speaking TYPO3 developers are eagerly waiting for more Books about Extbase and Fluid published in English. Sebastian Kurfürst and I are currently investigating the best way to to get the book translated into English to be published on typo3.org.

If you have any questions regarding the book, or found some typos (at least 3), feel free to use the comments facility (if it is positive ;-) ) or write me an e-mail. I am really looking forward to hear from you.

You might want to support our work by ordering the book through this link.

The upcoming Version 5 of TYPO3 is rewritten from scratch. It is based on a new framework called FLOW3. With TYPO3 v5 the [API|Application Programming Interface] will change completely. There are also a couple of new programming paradigms and patterns. Personally, I am very enthusiastic about the “new way”.

The past couple of months I had numerous discussions about the new version and how to migrate from TYPO3 v4 to v5. And I had to realize that there are several reservations and concerns about all the new things to learn. All of them have to be taken into account to keep the community healthy.
read more »

Domain Driven Design is—by experience—a strong concept and a good foundation to build TYPO3 extensions upon.

Domain-driven design (DDD) is an approach to the design of software, based on the two premises that complex domain designs should be based on a model, and that, for most software projects, the primary focus should be on the domain and domain logic [...].

The domain represents structure, knowledge and data. A content management system (CMS) like TYPO3 has to handle the data of the domain with respect to the domain knowledge. It aggregates the data, and visualizes it as a content of an output format.

A question emerges: How should the data stored in a domain be mapped on the content of the output? read more »

Today’s development process of a TYPO3 extension comprises (usually) the following steps:

1. collect clients’ or personal needs
2. design the relational model (database design)
3. scaffold the extension using the kickstarter
4. add a lot of database queries template handling to the file _pi1, _pi2, _pi3 etc.
5. design the templates

This ends up in an extension design which is hard to maintain – especially for larger projects. A more modern approach uses the Model View Controller Pattern. read more »