Future of TYPO3 CMS

• Mathias Schreiber • TYPO3 CMS Product Owner • TYPO3 CMS Contact • Dog Person

Who are you?

Future of TYPO3 CMS

• Act • Release • Learn • Repeat

Future

Future of TYPO3 CMS

• What did we have? • What did we do? • What did go wrong?

Retrospective

Future of TYPO3 CMS

• Regular Decays • Flow announced • Neos announced

• next-to static Feedback

Velocity and Impact

Future of TYPO3 CMS

• FAL • Backend Polishing • Small fixes (a LOT) • Maintenance

CMS 6.2

Future of TYPO3 CMS

• Gather strength • Find Focus • Define Goals • Re-Build the Team • Gain Confidence

The big sleep

Future of TYPO3 CMS

• Take what we have • Build what we need • Close contact to the market

Embrace & Innovate

Future of TYPO3 CMS

• Define common goals • Consensus over

dictatorship • Unblock teams • Connect Businesses and

Development

Management

Future of TYPO3 CMS

• Old code • Built in 1999 • in PHP4 • still valid today

Re-pay technical debt

Future of TYPO3 CMS

We are feature complete

Future of TYPO3 CMS

• Seriously :)

• Easy content entry • Supply help • Streamline editing

Editors

Future of TYPO3 CMS

• Simplify Workflows • One solution over 20 • Automated tools • Easier staging

Integrators

Future of TYPO3 CMS

• Ease deployment • Harden the system • Improve scalability

DevOps

Future of TYPO3 CMS

• Legacy Code • Rushed features • Wrong impressions

Fix it, for f***s sake!

Future of TYPO3 CMS

Q & A

Future of TYPO3 CMS

Thank you for your time