Neos 3.0 and the road ahead

A presentation of the current most important projects and the status of Neos 3.0 at the Neos Meetup Rhein/Main.

Transcript

2. Neos 3.0 & The Road Ahead
3. Bastian Heist • SAP ERP Consultant @ Merck, 2008-2015 • Freelance Web Developer since 2009 • Full-Stack-Developer @ Sandstorm Media since 2015 • Neos since 2015 @beheist @bastianheist
5. Agenda • Neos 3.0 - Features & Changes • CQRS / ES for the Neos CR • The Neos React UI
6. Neos 3.0 Features & Changes
7. New features in 3.0 ¯\_(ϑ)_/¯ 3.0 is focused on preparing the foundation!
8. Namespace: TYPO3 -> Neos • ~50 packages in Neos\ and Flowpack\ • … >100 more in vendor namespaces
 by Core Team Members such as Ttree, Psmb,
 Yeebase, Sandstorm, Networkteam, Flownative, Sitegeist, … • A LOT of refactoring.
9. TypoScript2 -> Fusion • To distinguish the language from TypoScript,
 it was renamed to Fusion. • File endings are now .fusion (.ts2 will continue
 to work until Neos 4.0) • More refactoring.
10. Fluid becomes standalone engine • TYPO3.Fluid is now split in typo3fluid and 
 Neos.FluidAdaptor • More refactoring…
11. PHP 7.1 compatibility • Issues with PHP 7.1 especially in rendering • Soft reserved keywords: „Object“ and „Resource“ • Even more refactoring…
12. PSR-7 compliance • PSR-7 describes a set of default interfaces
 that represent HTTP requests and responses • Some refactoring is needed to implement them. • Will probably come with Flow 4.1.
13. Rethinking 
 The Neos CR CQRS and Event Sourcing
14. What is CQRS / ES?
15. CQRS and ES primer • CQRS splits the Read and Write
 sides of an application’s model.
16. Classical Layered Architecture Controller Model View Read Write
17. CQRS Command Handler Read Write Command Domain Logic / Aggregates Event Query Models Query Models Query Models Projection
18. Benefits of CQRS Well-suited for read/write 
 disparate systems
19. Benefits of CQRS Great fit for event-driven,
 unidirectional dataflow UI
 (React/Redux, anyone?)
20. Benefits of CQRS Lets you implement collaborative editing more easily 
 (avoids locking issues)
21. Benefits of CQRS Very detailed audit log by-design
 (which we currently don’t have)
22. https://github.com/neos/ Neos.EventSourcing Want to contribute?
23. The React Rewrite Neos — React
24. Basics? React+Redux
25. y = f(x) DOM = react(state) React+Redux
26. state?
27. State is immutable React+Redux
28. Component Action Reducer State
29. Actions React+Redux
30. Reducer newState = f(oldState, action) React+Redux
31. Why rewrite?
32. Why rewrite?
33. Issues… Why rewrite?
34. Responsiveness Why rewrite?
35. Overflowing Styles Why rewrite?
36. Planned Features Why rewrite?
37. Extensibility Why rewrite?
38. JS Ecosystem Converging to Flux Pattern Why rewrite?
39. 16655 lines of Ember 1.x code The Rewrite
40. State Structure
41. State Structure
42. State Structure
43. State Structure
44. State Structure
45. Let’s have a look! composer require 
 neos/neos-ui:dev-master 
 neos/neos-ui-compiled:dev-master
46. Let’s have a look! /neos -> old /neos! -> new
47. Status & next steps Alpha shipped with Neos 3.0 Full switch with Neos 4.0
48. https://github.com/neos/neos-ui Want to contribute?
49. www.neos.io Thank you!
50. March 31 & April 1
 Hamburg
51. www.neos.io Thank you!