1. Continuous Delivery

    For almost two years now we use Hudson - the Continuous Integration server - for automizing tests of the FLOW3 and TYPO3 Phoenix projects. Since then this tool has been an invaluable help for spotting bugs and integration issues right after each commit. Inspired by Martin Fowler's CI article we always sought to automize the testing and release process but it needed another book to really enthuse me for the topic.

    Read more

  2. Debugging FLOW3 Applications

    Throughout the years my team and I have gathered quite some experience with debugging complex PHP applications like one FLOW3 is. Since FLOW3 controls the lifecycle, dependencies, proxy classes and scopes of almost all objects used in an application or the framework itself, the central parts contain a lot of references to other objects which in turn might refer back to central places like the Object Manager.

    Read more

  3. Managing a big project

    Over the last years TYPO3 Phoenix – and in the meantime also its sub projects FLOW3 and Fluid – have become huge and complex projects. Most of us surely underestimated the effort which needs to go in such a venture. On the other hand it doesn't come by surprise that creating a CMS from scratch which aims to excel the current TYPO3 in function, user experience, technology and code quality isn't a walk in the park.

    Read more

  4. The purpose of this blog

    Developing your own blog is probably not the cleverest thing a busy developer can do. And yet it was very important for the TYPO3 5.0 and FLOW3 project to create this "blog example". My blog serves as a test bed and steady reminder for what we want to achieve with the project Phoenix: A full featured next generation CMS.

    Read more

  5. Hello World!

    After literally years of development, I am really happy to have my very own first FLOW3 based application online: this blog! But although a Hello World post would be the perfect place for telling the story behind this site, the title refers to something completely different. It's the reason why I won't be at the T3BOARD this year, so ...

    Read more