TYPO3 Phoenix and FLOW3 - August 2012

TYPO3 Phoenix

Christian finished content type definitions for Phoenix, so we have a definite basic set of content types. Those differ slightly from what we used so far, which resulted in a migration tool for content inside the TYPO3CR that is working fine and was about ready for a merge at the end of August. Together with the content types all you need to start with a website is a template, and to speed things up even more Phoenix will deliver a wireframe template to allow for a quick start when it comes to content editing. Christian finalized the concept we had for this and started to implement that. Marc and Sebastian further improved the content management module for Phoenix, which also fostered improvements to TypoScript, including the possibility to use it standalone in any FLOW3 package for configuration purposes and template rendering (using the new TypoScriptView). Mattias Nilsson and Rens started to integrate <link http: createjs.org>create.js into Phoenix, as the base for using the results of the IKS project. Aske brought the workspace management module for Phoenix to a state that allows to approve and discard content changes easily and fixed some workspace publishing issues with nested content along the way. Sebastian, Bastian and Marc started to work on what you know as TCEforms from the good old days - only this time it's based on the content management module as well as TypoScript, to be flexible and as easy as possible at the same time. Support for images in XML export/import for Phoenix was started and the basic princple has been verified as working fine. Now this needs to be expanded to support arbitrary  attached objects. A lof of reviews and other fixes were done by the team as well.

FLOW3

Cookie support in the HTTP implementation was finished by Robert, documentation was massively updated in light of the 1.1 release and some remaining issues were resolved. Then we tweaked the FLOW3 website some more and released FLOW3 1.1 through our release pipeline, Jenkins worked flawlessly as usual. :) Julle further focused on package management and composer integration, and first results allow to install a clean FLOW3 setup just using composer. More work needs to be done, but it looks promising. Rens started with a major addition to the capabilities of the security framework by removing Role as an entity - Roles will solely be defined in policy configuration - and adding persistable groups (this was partly sponsored by <link http: beech.it>Beech Applications, thanks!).

The End

Presenting FLOW3 at <link http: campus-party.eu>Campus Party Europe was a success and the event itself turned out to be as interesting as expected. If you missed it, watching the videos from the event is really recommended. After that exciting event, Robert needed something to relax, so he  finally moved all tickets we had in our Jira instance (back) to redmine. Speaking about consolidating services, the FLOW3 website has been moved to the TYPO3 project infrastructure and is ready to be served from there. Yay! And as it was time for budgets again, we looked at this years budget use so far and handed in a number of budget applications for 2013. That's it for August. Now on with September, starting with a code sprint in Copenhagen. Thanks to Aske and Julle for organizing it!