**Proposals for T3CON12DE Talks From Phoenix/FLOW3 Team** (scroll down for talk list) **================================** **MARKETING FACTS** **================================** * We definitely have 14 Talks happening about Phoenix, and 2 tutorials. Maybe there will be 3-6 more talks. * Main Topic: The Launch Of Phoenix Highlight Talks/Topics: * TYPO3 Phoenix o "Master Talk" = keynote, introducing TYPO3 Phoenix * Integrating Phoenix into the Enterprise o Why should a decisionmaker choose Phoenix, and why does it matter especially in enterprise environments? o Andreas Förthner * Talk + Tutorial "Building a Phoenix Website" o everything you need to use Phoenix for projects, educating the integrators to work with Phoenix o Christian Müller + Berit * Lots of Technology Talks, highlighting and showcasing the recent developments and the functionality o FLOW3 highlights (version 1.1) (Robert) o Half-day tutorial about FLOW3 key techniques o Package management in FLOW3 and Phoenix + by Julle (Christian Jul Jensen) + maybe also with Jordi Boggiano, chief developer of the Composer Package Manager. o EmberJS + EmberJS is the JS framework used for Phoenix. + this talk is by Tom Dale, lead developer of Ember o "Travis-CI - social continuous integration" + Talk about the CI platform by Lukas Kahwe Smith, release manager of PHP 5.3 o Other topics: + Deployment, Semantic Technologies, Profiling and Debugging, Forms **================================** **TALK LIST** **================================** Who is available for speaking: * Robert * Christian * Julle * Berit * Sebastian * Christopher * Marc * Aske * Karsten * Bastian * Adrian Foeder * Andi? * Rens * Markus (not direct a talk alone, but would help anyone who needs help) ------------------------------------------------------- **Profiling and debugging FLOW3 and Phoenix (**Marc Neuhaus,** **Sebastian**)** STATE: SUBMITTED ------------------------------------------------------- **Introduction to the ContentManagement package** (Marc Neuhaus / Sebastian) (Management View) State: SUBMITTED ------------------------------------------------------- **Searching the Semantic Web: Exploration of Linked Data **(Sebastian, Florian Heinze) State: SUBMITTED ------------------------------------------------------- **FLOW3 Form Project** (Bastian) State: SUBMITTED ------------------------------------------------------- **Vendor Branching and other Stunts with Git** (Karsten) State: SUBMITTED ------------------------------------------------------- **Internationalization with FLOW3** (Karsten) State: SUBMITTED ------------------------------------------------------- **Testing FLOW3 and Phoenix** (Karsten, Rens) State: SUBMITTED ------------------------------------------------------- **A Technical Overview of TYPO3 Phoenix** (Christopher, maybe Sebastian) State: SUBMITTED ------------------------------------------------------- **Integrating Phoenix into the Enterprise** (Andi) State: SUBMITTED ------------------------------------------------------- **Automate FLOW3 and TYPO3 Deployment with Surf** (Christopher, Tobias) State: SUBMITTED ------------------------------------------------------- **Getting into FLOW3 1.1 – Tutorial **(Robert) State: SUBMITTED ------------------------------------------------------- **FLOW3 1.1 **(Robert) State: SUBMITTED ------------------------------------------------------- **A New CMS **(Robert) State: SUBMITTED ------------------------------------------------------- **FLOW3 goes Composer **(Julle) State: BOARDING MUST-HAVE talks: **Phoenix master talk by "TYPO3 Phoenix team" (demo …)** * Possible Talk Title: "Lift off!" * possibly directly after the keynote, celebration and presentation of Phoenix release candidate **Title:** * A New CMS **Short abstract** * The keynote address about a new Content Management System. **Long abstract** * When the core team met in 2006 for creating a vision and roadmap for TYPO3 project, we only had a vague idea of the possible impact a "version 5.0 - usability for developers" could have. * * A lot of research went into the new framework and ultimately into the new Content Management System. TYPO3 had so many great features and mechanisms, that it took quite an effort to think outside the box and come up with something even better. * * See for yourself, what the ever growing team behind the project with the code name "Phoenix" has created for you. ------------------------------------------------------- **A Technical Overview of TYPO3 Phoenix (Christopher, maybe Sebastian)** **State:** SUBMITTED * Notes: * Here, we will give a techically-oriented overview of TYPO3 Phoenix, showing all its technology parts and how they connect together. * Each of the main technologies will be briefly presented: FLOW3, the Content Repository, TypoScript, Eel, FlowQuery, Fluid, the Form API, Package Management, Plugins, the Phoenix UI and more. * * Moreover, this talk serves as an overview for all the other Phoenix-related talks. At the end, we will highlight the upcoming tasks, and ask for community help and participation in order to implement them. **Title:** * **An Technical Overview of TYPO3 Phoenix** * Phoenix behind the Scenes **Short abstract** * An overview of the technical architecture of Phoenix featuring FLOW3 and several modular packages that provide key components of the CMS. **Long abstract** * TYPO3 Phoenix features a brand new architecture based on the FLOW3 framework and modular packages for the content management system. * This talk will give you a technical overview of the framework and individual components, how they connect and how to re-use them in custom applications. * Each of the main technologies will be briefly presented: FLOW3, the Content Repository, TypoScript, Eel, FlowQuery, Fluid, the Form API, Package Management, Plugins, the Phoenix UI and more. * Moreover, this talk serves as a good overview for all other Phoenix-related talks. * ------------------------------------------------------- **FLOW3 1.1** (Robert) **Title:** * FLOW3 1.1 **Short abstract** * Helicopter talk about the key features of FLOW3 1.1. **Long abstract** * The FLOW3 framework got a lot of attention when version 1.0 was released after years of development. Its main approach is to deliver a whole-in-one concept for modern programming techniques and guiding developers to write excellent code. In the meantime, version 1.1 has been released, introducing a handful of important features early users of the framework had on their wish list. * * This session takes you on a tour through the key features of FLOW3 1.1 with the help of some concrete examples. (TODO: WRITE ABSTRACT) ------------------------------------------------------- **Getting into FLOW3 1.1 tutorial** (Robert) **Title:** * Getting Into FLOW3 1.1 **Short abstract** * Half-day tutorial introducing the core features of FLOW3 1.1 by means of a concrete example. **Long abstract** * FLOW3 is a web application platform which uses Domain-Driven Design as its major underlying concept. This approach makes FLOW3 easy to learn and at the same time clean and flexible for complex projects. It features namespaces, has an emphasis on clean, object-oriented code and provides a seamless Doctrine 2 integration. * * FLOW3 incorporates Dependency Injection in a way which lets you truly enjoy creating a stable and easy-to-test application architecture (no configuration necessary). Being the only Aspect-Oriented Programming capable PHP framework, FLOW3 allows you to cleanly separate cross-cutting concerns like security from your main application logic. With its 1.1 release, several new features have been introduced, including a comprehensive internationalization support and a standards compliant HTTP foundation. * * This tutorial takes you through an imaginary project from scratch. During the journey we’ll visit all important areas of the framework. ------------------------------------------------------- **Package Management in FLOW3 / Phoenix** (Julle) (+ we should ask Jordi if he's got some time, right?) (TODO: WRITE ABSTRACT) **Title:** * [title] **Short abstract** * one sentence **Long abstract** * 4-6 paragraphs ------------------------------------------------------- **Building a TYPO3 Phoenix Website (Christian, Berit)** STATE: NOT SUBMITTED **Title:** * **Building a TYPO3 Phoenix Website** **Short abstract** * In this talk, we'll show how to develop your own Phoenix website, ranging from first setup up to advanced TypoScript customizations. **Long abstract** * In this talk, we'll show how to develop your own Phoenix website: * After the basic installation, we'll show how packages bundle all website-related assets such as TypoScript, templates, and basic content. * * We'll use the site kickstarter to create a skeleton package and customize it. After basic adjustments, we'll create our own template. * * Later in the process, we will create custom content elements, highlighting the powerful flexible content elements directly baked into the Phoenix core. * We'll end this talk with giving an outlook to adjusting the website output using TypoScript. ------------------------------------------------------- **Phoenix Integrator Tutorial (Christian, Berit)** **Title:** * **Phoenix Integrator Tutorial** **Short abstract** * TODO zielgruppe integrator * In this tutorial, you will learn the completely re-designed TypoScript of TYPO3 Phoenix. **Long abstract** * TODO re-write * If TYPO3 was a human, then TypoScript would be probably his DNA. It's the heart of TYPO3, enabling extremely flexible and customizable frontend output. * For Phoenix, we've completely re-designed this language, making it more consistent, powerful, and hopefully also easier to understand. * * In this tutorial, you will learn the basics of the new TypoScript and their related technologies such as Eel and FlowQuery by example. Together with showing the similarities and differences with the classic TypoScript from TYPO3 v4/6, we will customize and extend an existing webpage. * * In the end, an outlook on planned improvements such as better developer tooling or better technology integration is given, making it easier for new people to join the development effort. ------------------------------------------------------- **Integrating Phoenix into the Enterprise (Andi)** * **Status:** SUBMITTED **abstract wird geschrieben von: Sebastian** **wird eingereicht von: Christopher** * Notes: * * Title: * Why should a decisionmaker choose Phoenix? This talk answers this question, especially focussing on enterprise integration. * * Abstract: * There exist loads of CMS systems on the market, and with Phoenix, we got one more. * * In this talk, we'll explain the benefits of choosing Phoenix in an enterprise environment, especially demonstrating the integration into a heterogenous application landscape. * * Because Phoenix websites and applications are based upon numerous powerful and extensible frameworks, we'll demonstrate how to orchestrate the numerous pieces together. * * We'll show real-world use cases, and how to solve them with the framework. This includes the use of custom plugins and authentication backends, but also importers, message queues and SOAP endpoints. * Furthermore, we'll show how the phoenix UI can be extended * * At the end of this talk, you will have a good overview about the possibilities and extensibility features of Phoenix, and which points to use in enterprise environments. * **Title:** * **Integrating Phoenix into the Enterprise** **Short abstract** * This talk looks at the integration capabilities of Phoenix and why it's a great fit for enterprise CMS projects from a decision makers perspective. **Long abstract** * TYPO3 Phoenix is not just another CMS, it's a whole ecosystem based on a powerful framework and solid components. * * In this talk, we'll explain the benefits of choosing Phoenix for an enterprise environment, especially demonstrating the integration into a heterogenous application landscape and connecting it to existing systems. * * We'll show real-world use cases, and how to solve them with the new CMS. From the use of custom plugins and authentication backends to data handling with imports, message queues and webservices with SOAP or REST. Not only the backend but also the UI is extensible for custom requirements and can be used to build any application on top of Phoenix. * * At the end of this talk you will have a good overview about the possibilities and extensibility features of Phoenix and how it connects to existing enterprise systems. * ------------------------------------------------------- **Semantic Enrichment of Content using VIE, Stanbol and the IKS** Stack (Rens) (TODO: WRITE ABSTRACT) **Title:** * [title] **Short abstract** * one sentence **Long abstract** * 4-6 paragraphs ------------------------------------------------------- **Automate FLOW3 and TYPO3 Deployment with Surf** (Christopher, Tobias) **Status:** SUBMITTED * * Notes: * - Why a Deployment Process matters * - deploy FLOW3 applications and Phoenix websites * - deploy v6 (maybe Tobias can join here) * - extend Surf * - integrate Surf into CI **Title:** * Automate FLOW3 and TYPO3 Deployment with Surf **Short abstract** * Surf can automate and ease the deployment process of FLOW3 and TYPO3 projects. See real world examples and learn how to extend the flexible system. **Long abstract** * Automated deployment is a crucial part of continuous delivery and most agile strategies. * The Surf tool is already used for most FLOW3 related projects and provides a great benefit for these kind of projects. Built as a FLOW3 application it's flexible and extensible and can be bundled or used stand-alone. Besides being great for any FLOW3 based project (including Phoenix) it's possible to deploy almost anything. * Starting with TYPO3 6.0 an automated deployment process will be much easier to implement and Surf comes pre-configured with a deployment target for this branch of TYPO3. * In this talk we will also feature the unique features of Surf like clustered deployment, smoke testing, extensibility with custom tasks and integration into a continuous integration infrastructure. ------------------------------------------------------- **EmberJS Introduction **(Tom Dale) **Title:** * [title] **Short abstract** * one sentence **Long abstract** * 4-6 paragraphs ------------------------------------------------------- **Search Integration** (ElasticSearch, Adrian Foeder)? ~~Adrian: Christian already offered to co-moderate and co-prepare that slot which I'm very fine with ;) For the moment the TYPO3.ElasticSearch package offers basic functionality to index entities. Due to the fact I'm personally lacking very good ES knowledge at all it's hard for me to think what additionally will make sense; but if the guys who already used ES can give some input that'd be great (Sebastian?, Bastian?). Maybe the ElasticSearch example package could be a good work-on basis. TODO: soutask adriansout \& write abstract **Title:** * [title] * * * **Short abstract** * one sentence **Long abstract** * 4-6 paragraphs ------------------------------------------------------- **Building Extensible FLOW3 Applications: AOP, Signals/Slots, TypoScript and beyond** (WHO DOES THIS) Karsten? - using TypoScript in the view layer (TODO: WRITE ABSTRACT) **Title:** * [title] **Short abstract** * one sentence **Long abstract** * 4-6 paragraphs ------------------------------------------------------- **Testing FLOW3 and Phoenix ** - Unit tests - Functional tests - Javascript Tests? (Rens) **Title:** * Testing FLOW3 and Phoenix **Short abstract** * Test-Driven Development is a centerpiece of FLOW3 and Phoenix development - see how and why we do it! **Long abstract** * With the complexity of frameworks like FLOW3 and applications like TYPO3 Phoenix development will grind to a halt sooner rather than later without sufficient test coverage. This talk will show how we do unit and functional testing of PHP and JavaScript code. And because writing tests without running them does not help, we'll talk about Continuous Integration as well. ------------------------------------------------------- **Real world projects using Phoenix/FLOW3?** +2 -- maybe Adrian Foeder, or Bastian? ~~Adrian: For the moment I can't promise that we, in October, are in a situation where we already can present our project to the publicity. If somewhat possible, maybe we can make our part here "optional", i.e. group this session to few project holders that each do present their work on a 20 min base instead of one person presenting 1 hour Marc: I'm working on a little Internal project making use of FLOW3 and Foo.ContentManagement. I could possibly present that depending on how far along it will be. (TODO: WRITE ABSTRACT) **Title:** * [title] **Short abstract** * one sentence **Long abstract** * 4-6 paragraphs ------------------------------------------------------- **Customizing Phoenix (Aske?)** (TODO: WRITE ABSTRACT) **Title:** * [title] **Short abstract** * one sentence **Long abstract** * 4-6 paragraphs ------------------------------------------------------- **Aloha something?** TODO ask Haymo \& write abstract **Title:** * [title] **Short abstract** * one sentence **Long abstract** * 4-6 paragraphs ------------------------------------------------------- **Phoenix Content Synchronization / Import/Export** (maybe robert?) (TODO: WRITE ABSTRACT) **Title:** * [title] **Short abstract** * one sentence **Long abstract** * 4-6 paragraphs ------------------------------------------------------- **Title** * Vendor Branching and other Stunts with Git **Short abstract** * FLOW3 is developed using Git, this leads to some best practices when developing with and for FLOW3. **Long abstract** * FLOW3 is developed using the distributed version control system Git. This provides countless possibilities when it comes to tracking changes in both the framework codebase, developed by the FLOW3 team, and your own application packages. The talk will show how to use "vendor branching" the way we think it should be done and will showcase a few other cool stunts you can pull off with Git. ------------------------------------------------------- **Title** * Internationalization with FLOW3 **Short abstract** * An overview of internationalization and localization for FLOW3 applications. **Long abstract** * I18n and L10n are important parts of most (web) applications. FLOW3 offers various methods to develop applications that can be translated and localized as needed. The talk will show the available API, explain the XLIFF format used for message catalogs and present best practices for putting all those parts to use. * -------------------------------------------------------------------------------------------------------------------------------------------------- **Asset Management using TYPO3.Asset** (Marc Neuhaus,sout Adrian Foedersout?) ( maybe merge this with the Profiling and debugging into a talk about Tools to improve the FLOW3 development process? ) -> maybe remove it, or have a generic FLOW3 Packages talk? A common problem growing applications face is the question how to Handle CSS/Less/SASS and JavaScript Assets. By usage of Assetic we've created a package called TYPO3.Asset to simplify this process. In this talk we'll walk you through some examples on how to use this Package and give you a look behind the curtain of TYPO3.Asset **Title:** * Asset Management using TYPO3.Asset **Short abstract** * TYPO3.Asset offers simple tools to include and convert CSS, LESS, SASS and JS assets into your FLOW3 applictaions **Long abstract** *