The developers of TYPO3 Flow focused on a series of paradigms and design patterns, some of which are considered as innovative within the PHP community.

These conventions assist the developers to effectively create clean, structured code and to prevent errors [3] Some important aspects are: When designing TYPO3 Flow the developers paid attention that their custom code has minimal dependencies on the TYPO3 Flow API.

This allows users to import and use modules that were originally written for other systems (such as Symfony) to be used in TYPO3 Flow with very little modifications.

On a side note, the Java WCMS community has also been paying attention to the development of TYPO3 Neos and TYPO3 Flow, for its modern architecture and transparent code basis[3][10] On 2 June 2009 the first Build was released as FLOW3 1.0.0 Alpha 1[11] In the following period about 14 alpha versions were released, until FLOW3 was ready for the beta phase in August 2011.

The TYPO3 Flow core team currently consists of eleven developers actively working on the framework.

Most of the new features of TYPO3 Flow have been backported for use with older TYPO3 versions (4.3 and higher) to provide a smooth transition to or from TYPO3 CMS.

Therefore, Domain-Driven Design and MVC concepts can be used within TYPO3 CMS and subsequently ported to systems running TYPO3 Neos.

The ability to develop custom ViewHelpers makes Fluid a flexible and extendible templating system.