The Event-Sourced Content Repository for Neos

We are currently busy reworking the central data store of Neos: The content repository (CR), is currently getting a from-scratch rewrite. We'll quickly showcase the evolution of the current-generation CR, and explain which of our design decisions worked out and where we currently see the biggest problems.

After that, we'll explain why we're settling on an event-sourced architecture, then showing the current status of the rewrite. We'll be demonstrating how integrators will work with the new CR and how you can program with its APIs. Finally, we'll give an outlook on how we'll make upgrades to the new CR possible.