mistakes • TYPO3 v9 to v10 has the smoothest upgrade paths since TYPO3 v6.2 • Hundreds extensions are compatible already • New PHP tools like rector help shape the path for the future • My recent works • Updating from a deprecation-free v8 to v9: 100% • Updating from a deprecation-free v9 to v10: 30%
- developer-driven product development • Where are the benefits from an Upgrade? • What is the need that people have using TYPO3 (or not even knowing TYPO3)? • Are we refactoring for the sake of refactoring?
• Should news, flux, crawler (you name it) be included in Core? • Who is going to maintain TYPO3 Core? • Disclaimer: "Having it in the Core" is a very easy answer, somebody™ is going to have to maintain the code for a loooong time. 3 years for free from people working on this in their spare time is a hard-to-take thing. Consider developers sponsoring bugfixes for TYPO3 like Mehrwert, Uni Oldenburg and so many more are doing. • We rely on people feeding their families and giving us TYPO3 for free!
We now rely on third-party software and their support times • PHP, Databases: This gets more complicated these days • Symfony, Doctrine etc. in conjunction with PHP lifetimes • On top: • jQuery • Twitter Bootstrap • CKEditor4
groups • A lot of stakeholders • Who is taking decisions based on what facts? • Who should benefit from new changes? • Governments? Large Enterprises? Universities? Newspaper websites? Multi- national corporation websites? Integrations with shops? • Is there a vision where everybody moves in the same direction?
does "Enterprise" mean anyway? • Look at how TYPO3 is used across the CMS landscape • 90% are running on shared hosters with small to medium-size installations • Are there "Enterprise" editors? • Why do we make it so hard for everybody who is "non-Enterprise" then?
(“LHF”) 2. UX-driven improvements 3. Market research and definition of the strategy and goals Clear positioning of the CMS regarding our main target groups 4. Increase adoption rate through faster "time-to-launch" 5. Make updates a “no-brainer” 6. Innovation through extensibility in a conservative CMS market
bugs • Make everybody happy! • Work through feature requests on forge.typo3.org • Build stories around uncommon features • Workspaces? Watch out for them! It's gonna be a USP for TYPO3 again! • Security: Content Security Policy (CSP) for TYPO3 Backend is long overdue
a dashboard if a new installation does not hold hands for creating a site? • How good are modules if everything is done through the list view (on page ID "0") • How good is "frontend users" logic if they are hidden in a module? • File Storages, File Mounts, File References.... does anyone new get that? • Organize the TYPO3 Backend modules for new people • Make the TYPO3 Backend accessible for everyone!
TYPO3 ship a default output for a website? • Why can't we build best practices for Frontend output in TYPO3 Core? • Why don't we build themes? • Note: Even marketers in Enterprises want a “quick new landing page” • Who is using TYPO3? And how? • We need more marketing targeted on the next generation of users • Relevant TYPO3 Teams need to work together!
with other web apps and t3o services • Extensions / Apps / Web Hooks • Build features everybody falls in love with • “Unsplash” Extension: FAL driver for Files / Assets • Markdown Support for TYPO3 Content Elements • Build innovation in the PHP CMS world • Security: Integrate 2FA / Multi-Factor-Authentication by default • Make the TER a first-class-citizen again
December 2020 • LTS planned for early October 2021 • Continue the easy upgrade path • Include the long-hanging fruits ("LHF") • Caution: System requirements will change! • and of course... breaking changes!
Define the target groups & Evaluate market position and future possibilities • T3A Board, Mathias Schreiber / TYPO3 GmbH, Marketing Team + myself • What about a UX Product Team? • Evaluate other CMS for usability • Make TYPO3 more usable • Accessibility Team • Use a better language in docs & the CMS • Core development is then "building the results in a sustainable way"